GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-10T22:10:35Z,
for the dataset file:///tmp/1_in.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Mecatran
Publisher URL:
https://www.mecatran.com/
Feed Language:
French
Feed Start Date:
2024-06-08
Feed End Date:
2024-07-07

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. trips.txt

Counts

  • Agencies: 1
  • Blocks: 3643
  • Routes: 131
  • Shapes: 457
  • Stops: 6046
  • Trips: 91154

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

ShapesFeed InformationRoute ColorsHeadsignsWheelchair AccessibilityBikes AllowanceLocation Types

Specification Compliance report

54483 notices reported (0 errors, 54470 warnings, 13 infos)

Notice Code Severity Total
expired_calendar WARNING 14

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
34 "2024_HIVER-M07_C01-Dimanche-11"
21 "2024_HIVER-M04_C01-Dimanche-10"
9 "2024_HIVER-M01_C01-Dimanche-41"
31 "2024_HIVER-M07_B01-Samedi-08"
57 "2024_HIVER-M16_C01-Dimanche-12"
103 "2024_HIVER-M31_C01-Dimanche-50"
209 "2024_HIVER-TR_C01-Dimanche-34"
58 "2024_HIVER-M18_C00-Dimanche-11"
51 "2024_HIVER-M15_C01-Dimanche-17"
27 "2024_HIVER-M05_C01-Dimanche-17"
15 "2024_HIVER-M02_C01-Dimanche-23"
44 "2024_HIVER-M09_B01-Samedi-55"
135 "2024_HIVER-M568_B00-Samedi-03"
137 "2024_HIVER-M568_C00-Dimanche-03"
fast_travel_between_consecutive_stops WARNING 12

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.
4300 "268435725_10" "02" 699.2888196359308 0.19424689434331413 160928 47 "3647" "Quinconces" "13:07:00" 160929 48 "5315" "Quinconces" "13:07:01"
4301 "268435725_11" "02" 699.2888196359308 0.19424689434331413 160976 47 "3647" "Quinconces" "13:07:00" 160977 48 "5315" "Quinconces" "13:07:01"
4302 "268435725_12" "02" 699.2888196359308 0.19424689434331413 161024 47 "3647" "Quinconces" "13:07:00" 161025 48 "5315" "Quinconces" "13:07:01"
4304 "268435725_18" "02" 699.2888196359308 0.19424689434331413 161120 47 "3647" "Quinconces" "13:07:00" 161121 48 "5315" "Quinconces" "13:07:01"
4305 "268435725_19" "02" 699.2888196359308 0.19424689434331413 161168 47 "3647" "Quinconces" "13:07:00" 161169 48 "5315" "Quinconces" "13:07:01"
4303 "268435725_17" "02" 699.2888196359308 0.19424689434331413 161072 47 "3647" "Quinconces" "13:07:00" 161073 48 "5315" "Quinconces" "13:07:01"
4307 "268435729_14" "02" 699.2888196359308 0.19424689434331413 161264 47 "3647" "Quinconces" "13:07:00" 161265 48 "5315" "Quinconces" "13:07:01"
4306 "268435729_13" "02" 699.2888196359308 0.19424689434331413 161216 47 "3647" "Quinconces" "13:07:00" 161217 48 "5315" "Quinconces" "13:07:01"
4309 "268435729_21" "02" 699.2888196359308 0.19424689434331413 161360 47 "3647" "Quinconces" "13:07:00" 161361 48 "5315" "Quinconces" "13:07:01"
4308 "268435729_20" "02" 699.2888196359308 0.19424689434331413 161312 47 "3647" "Quinconces" "13:07:00" 161313 48 "5315" "Quinconces" "13:07:01"
15718 "268436309_15" "08" 258.8097422767555 0.07189159507687654 668149 30 "1715" "Hôpital Pellegrin (entrée Est)" "20:29:00" 668150 31 "5417" "Hôpital Pellegrin" "20:29:01"
15719 "268436309_22" "08" 258.8097422767555 0.07189159507687654 668180 30 "1715" "Hôpital Pellegrin (entrée Est)" "20:29:00" 668181 31 "5417" "Hôpital Pellegrin" "20:29:01"
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20240610" "20240707" "20240710"
missing_bike_allowance WARNING 1209

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

Only the first 50 of 1209 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
74608 "69" "268440206_10"
74609 "69" "268440206_11"
74610 "69" "268440206_17"
74611 "69" "268440206_18"
74612 "69" "268440207_12"
74613 "69" "268440207_19"
74614 "69" "268440227_10"
74615 "69" "268440227_11"
74616 "69" "268440227_17"
74617 "69" "268440227_18"
74618 "69" "268440228_12"
74619 "69" "268440228_19"
74620 "69" "268440278_13"
74621 "69" "268440278_14"
74622 "69" "268440278_20"
74623 "69" "268440278_21"
74624 "69" "268440299_13"
74625 "69" "268440299_14"
74626 "69" "268440299_20"
74627 "69" "268440299_21"
74628 "69" "37663158-2024_HIVER-M69_A10-Semaine-02"
74629 "69" "37663191-2024_HIVER-M69_A10-Semaine-02"
74630 "69" "40494947-2024_HIVER-M69_A00-Semaine-03"
74631 "69" "40494980-2024_HIVER-M69_A00-Semaine-03"
74632 "69" "268440229_10"
74633 "69" "268440229_11"
74634 "69" "268440229_17"
74635 "69" "268440229_18"
74636 "69" "268440230_12"
74637 "69" "268440230_19"
74638 "69" "268440301_13"
74639 "69" "268440301_14"
74640 "69" "268440301_20"
74641 "69" "268440301_21"
74642 "69" "37663159-2024_HIVER-M69_A10-Semaine-02"
74643 "69" "40494948-2024_HIVER-M69_A00-Semaine-03"
74644 "69" "268440231_10"
74645 "69" "268440231_11"
74646 "69" "268440231_17"
74647 "69" "268440231_18"
74648 "69" "268440232_12"
74649 "69" "268440232_19"
74650 "69" "268440303_13"
74651 "69" "268440303_14"
74652 "69" "268440303_20"
74653 "69" "268440303_21"
74654 "69" "37663184-2024_HIVER-M69_A10-Semaine-02"
74655 "69" "40494973-2024_HIVER-M69_A00-Semaine-03"
74656 "69" "268440233_10"
74657 "69" "268440233_11"
mixed_case_recommended_field WARNING 53230

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.

Only the first 50 of 53230 affected records are displayed below.

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" "BA 106 (terminus)" 113
"stops.txt" "stop_name" "ESAT du GUA" 723
"stops.txt" "stop_name" "BA 106 (terminus)" 2355
"routes.txt" "route_long_name" "BUS EXPRESS G" 69
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 5
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 6
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 7
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 8
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 9
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 10
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 11
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 12
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 13
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 14
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 15
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 16
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 17
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 18
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 19
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 20
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 21
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 22
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 23
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 24
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 25
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 26
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 29
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 30
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 34
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 35
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 36
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 37
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 38
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 39
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 40
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 41
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 42
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 43
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 44
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 45
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 47
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 48
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 49
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 50
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 51
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 52
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 53
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 54
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 55
"trips.txt" "trip_headsign" "MERIGNAC BEAUDESERT" 56
route_long_name_contains_short_name WARNING 2

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"69" 65 "BAT3" "BAT3"
"58" 132 "TBNight" "TBNight"
stops_match_shape_out_of_order WARNING 2

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

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. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
11348 "17" "41234030-2024_HIVER-M07_A10-Lun-Mer-29" 467039 "5650" "Parabelle" [44.94180130390687,-0.48579170935790356] 467038 "5649" "Parabelle (arrêt de Descente)" [44.94171143,-0.48569939000000006]
50133 "172" "268438434_15" 2331704 "9708" "Pyrénées" [44.774207714320674,-0.5647454644725021] 2331703 "8431" "Pyrénées" [44.77409744,-0.5647313]
unknown_column INFO 13

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"stops.txt" "ineo_id" 13
"stops.txt" "ineo_mnemoc" 14
"stops.txt" "ineo_mnemol" 15
"stops.txt" "ineo_noc" 16
"stops.txt" "ineo_nol" 17
"stops.txt" "ineo_nomc" 18
"routes.txt" "direction0_name" 9
"routes.txt" "direction1_name" 10
"routes.txt" "ineo_id" 11
"calendar.txt" "service_name" 11
"trips.txt" "ineo_id_chainage" 10
"trips.txt" "ineo_id_course" 11
"trips.txt" "ineo_id_jour" 12