GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T16:01:22Z,
for the dataset file:///shared/gtfs-open-014228d0527290.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-08
Feed End Date:
2026-09-07

Files included


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

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 36
  • Shapes: 108
  • Stops: 444
  • Trips: 298

Specification Compliance report

14 notices reported (0 errors, 14 warnings, 0 infos)

Notice Code Severity Total
fast_travel_between_consecutive_stops WARNING 11

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
120 "102884-119" "102884-161" 716.8474092121867 0.19912428033671853 2019 25 "102884-1986" "Paron Collège" "10:50:00" 2020 26 "102884-1990" "Complexe R. Treille" "10:50:01"
213 "102884-212" "102884-161" 716.8474092121867 0.19912428033671853 4018 25 "102884-1986" "Paron Collège" "18:06:00" 4019 26 "102884-1990" "Complexe R. Treille" "18:06:01"
251 "102884-277" "102884-166" 1448.9696269272267 0.4024915630353408 4789 9 "102884-2131" "Pierre de Coubertin" "08:45:00" 4790 10 "102884-2122" "08-mai-45" "08:45:01"
147 "102884-146" "102884-166" 607.6052376963906 0.16877923269344183 2527 6 "102884-2207" "Marne" "12:15:00" 2528 7 "102884-2123" "08-mai-45" "12:15:01"
255 "102884-330" "102884-166" 607.6052376963906 0.16877923269344183 4881 6 "102884-2207" "Marne" "12:15:00" 4882 7 "102884-2123" "08-mai-45" "12:15:01"
180 "102884-179" "102884-161" 716.8474092121867 0.19912428033671853 3330 22 "102884-1986" "Paron Collège" "15:51:00" 3331 23 "102884-1990" "Complexe R. Treille" "15:51:01"
164 "102884-163" "102884-165" 717.7031951595471 0.19936199865542975 2934 8 "102884-2017" "Rue du Clos" "13:56:00" 2935 9 "102884-2011" "Paul Bert" "13:56:01"
82 "102884-81" "102884-161" 716.8474092121867 0.19912428033671853 1223 22 "102884-1986" "Paron Collège" "07:47:00" 1224 23 "102884-1990" "Complexe R. Treille" "07:47:01"
227 "102884-226" "102884-161" 819.3747396615155 0.22760409435042098 4286 1 "102884-1989" "Complexe R. Treille" "18:35:00" 4287 2 "102884-1985" "Paron Collège" "18:35:01"
223 "102884-222" "102884-165" 767.6186784038506 0.21322741066773626 4208 1 "102884-2010" "Paul Bert" "18:02:00" 4209 2 "102884-2016" "Rue du Clos" "18:02:01"
129 "102884-128" "102884-161" 819.3747396615155 0.22760409435042098 2155 1 "102884-1989" "Complexe R. Treille" "11:00:00" 2156 2 "102884-1985" "Paron Collège" "11:00:01"
mixed_case_recommended_field WARNING 3

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.
"routes.txt" "route_short_name" "1tad" 3
"stops.txt" "stop_name" "08-mai-45" 102
"stops.txt" "stop_name" "08-mai-45" 103