GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-08T18:51:24Z,
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:
GTFS.pro
Publisher URL:
https://gtfs.pro
Feed Language:
French
Feed Start Date:
2023-06-24
Feed End Date:
2023-09-02

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: 1
  • Routes: 10
  • Shapes: 76
  • Stops: 297
  • Trips: 496

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

ShapesFeed InformationRoute ColorsHeadsignsWheelchair AccessibilityLocation Types

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 7

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.
13 "102336-23954"
5 "102336-4934"
14 "102336-30617"
8 "102336-5402"
11 "102336-7797"
12 "102336-7799"
7 "102336-5074"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

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 "20240608" "20230902" "20240615"
mixed_case_recommended_field WARNING 446

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 446 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.
"trips.txt" "trip_headsign" "LES HOUCHES - LE PRARION" 2
"trips.txt" "trip_headsign" "LES HOUCHES - LE PRARION" 3
"trips.txt" "trip_headsign" "LES HOUCHES - LE PRARION" 4
"trips.txt" "trip_headsign" "ARGENTIERE LA FIS" 6
"trips.txt" "trip_headsign" "LES HOUCHES - LE PRARION" 7
"trips.txt" "trip_headsign" "ARGENTIERE LA FIS" 8
"trips.txt" "trip_headsign" "ARGENTIERE LA FIS" 9
"trips.txt" "trip_headsign" "ARGENTIERE LA FIS" 10
"trips.txt" "trip_headsign" "LE TOUR" 12
"trips.txt" "trip_headsign" "GLACIER DE TACONNAZ" 13
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 14
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 15
"trips.txt" "trip_headsign" "GLACIER TACONNAZ" 16
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 17
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 18
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 19
"trips.txt" "trip_headsign" "GLACIER TACONNAZ" 20
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 21
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 22
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 23
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 24
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 25
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 26
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 27
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 28
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 29
"trips.txt" "trip_headsign" "GLACIER TACONNAZ" 30
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 31
"trips.txt" "trip_headsign" "GLACIER TACONNAZ" 32
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 33
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 34
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 35
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 36
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 38
"trips.txt" "trip_headsign" "LE TOUR" 41
"trips.txt" "trip_headsign" "CHAMONIX SCOLAIRE" 42
"trips.txt" "trip_headsign" "CHAMONIX SCOLAIRE - CAR 2" 45
"trips.txt" "trip_headsign" "CHAMONIX SCOLAIRE" 48
"trips.txt" "trip_headsign" "LES PRAZ / FLEGERE" 49
"trips.txt" "trip_headsign" "CHAMONIX - LES PRAZ / FLEGERE" 52
"trips.txt" "trip_headsign" "CHAMONIX - LE TOUR" 53
"trips.txt" "trip_headsign" "LES HOUCHES - LE PRARION" 54
"trips.txt" "trip_headsign" "CHAMONIX - GLACIER DES BOSSONS" 55
"trips.txt" "trip_headsign" "GLACIER DES BOSSONS" 56
"trips.txt" "trip_headsign" "CHAMONIX - GLACIER DES BOSSONS" 57
"trips.txt" "trip_headsign" "CHAMONIX - LE TOUR" 58
"trips.txt" "trip_headsign" "CHAMONIX - PLACE MONT BLANC" 59
"trips.txt" "trip_headsign" "CHAMONIX - LES PRAZ / FLEGERE" 60
"trips.txt" "trip_headsign" "CHAMONIX - CENTRE" 61
"trips.txt" "trip_headsign" "LE TOUR" 62
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`.
"102336-V1" 10 "V1" "V1 LES Houches"
"102336-V2" 11 "V2" "V2 LE Tour"
stop_too_far_from_shape WARNING 1

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.
436 "102336-456" "102336-0b1b8f521491917436e2" 10395 "102336-36903" "Chamonix - Casino" [45.92331000000001,6.871670000000001] 121.00422847243567
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20240608" "20230624" "20230902"