GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T23:47:30Z,
for the dataset file:///shared/imagine.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
French
Feed Start Date:
2025-09-16
Feed End Date:
2026-08-31

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. transfers.txt
  10. trips.txt

Counts


  • Agencies: 1
  • Blocks: 341
  • Routes: 81
  • Shapes: 237
  • Stops: 1661
  • Trips: 980

Specification Compliance report

27 notices reported (2 errors, 25 warnings, 0 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 2

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
631 "100922-151" "100922-merged_6fccc63366c9594b1570" 131 "100922-101" "100922-9455:12-12-31" "000069" "20251020"
614 "100922-117" "100922-merged_5976478ca30ef7fc43c5" 149 "100922-93" "100922-9455:12-12-31" "000068" "20250916"
mixed_case_recommended_field WARNING 18

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "imagerie" 41
"stops.txt" "stop_name" "parc relais" 64
"stops.txt" "stop_name" "parc relais" 65
"stops.txt" "stop_name" "parc relais" 66
"stops.txt" "stop_name" "terres st jean" 67
"stops.txt" "stop_name" "terres st jean" 68
"stops.txt" "stop_name" "terres st jean" 69
"stops.txt" "stop_name" "les chenes" 159
"stops.txt" "stop_name" "les chenes" 160
"stops.txt" "stop_name" "maurice ravel" 405
"stops.txt" "stop_name" "maurice ravel" 406
"stops.txt" "stop_name" "bmi" 413
"stops.txt" "stop_name" "bmi" 414
"stops.txt" "stop_name" "bmi" 415
"stops.txt" "stop_name" "patinoire" 446
"stops.txt" "stop_name" "patinoire" 447
"stops.txt" "stop_name" "wilson" 454
"stops.txt" "stop_name" "poissompré" 457
stop_too_far_from_shape WARNING 7

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
742 "100922-CALC_15054352" "100922-332" 16038 "100922-UZEFORG1" "Uzemain Les forges" [48.08422,6.305999999999999] 101.52301108922335
287 "100922-CALC_15054351" "100922-333" 5468 "100922-UZEFORG2" "Uzemain Les forges" [48.08422,6.305999999999999] 101.52301108922335
232 "100922-CALC_15054243" "100922-730" 4958 "100922-ZINCROI2" "Zincourt Croisement" [48.31088,6.43947] 105.91602259620271
234 "100922-CALC_15054241" "100922-732" 4969 "100922-ZINCROI2" "Zincourt Croisement" [48.31088,6.43947] 105.91602259620271
240 "100922-CALC_15054250" "100922-301" 5004 "100922-NOMLUNE2" "Nomexy Cote de la lune" [48.311600000000006,6.3751] 148.48348011366087
701 "100922-CALC_15054253" "100922-298" 15678 "100922-NOMLUNE1" "Nomexy Cote de la lune" [48.311600000000006,6.3751] 148.48348011366087
241 "100922-CALC_15054251" "100922-302" 5010 "100922-NOMLUNE2" "Nomexy Cote de la lune" [48.311600000000006,6.3751] 148.48348011366087