Call-prep brief · checked 2026-08-02
Réseau urbain Hop Bus
Grade F · 42.6 / 100
Unchanged since 2026-08-01.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
Top three things to fix
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Review the rule documentation for 'location_with_unexpected_stop_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Location with unexpected stop time (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Duplicate key (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Foreign key violation (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Location with unexpected stop time (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'location_with_unexpected_stop_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Key facts
- Feed URL
- https://www.data.gouv.fr/api/1/datasets/r/d10fb9b2-1a5a-498c-ba55-e89cf0136ef1
- Last checked
- 2026-08-02
- Service window
- 182 days of service data remain. Last service date 2027-01-31.
- Location
- Hauts-de-France, France
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.