GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-07T15:09:33Z,
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:
2024-05-14
Feed End Date:
2024-07-06

Files included

  1. agency.txt
  2. calendar.txt
  3. feed_info.txt
  4. routes.txt
  5. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts

  • Agencies: 1
  • Blocks: 1
  • Routes: 189
  • Shapes: 0
  • Stops: 1865
  • Trips: 1523

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

Feed InformationHeadsignsWheelchair AccessibilityLocation Types

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 3

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.
3 "676-10"
5 "676-12"
6 "676-13"
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 "20240607" "20240706" "20240707"
mixed_case_recommended_field WARNING 1525

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 1525 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" "MENNONNERIE-LES CHESNEAUX" 2
"trips.txt" "trip_headsign" "MENNONNERIE-LES CHESNEAUX" 3
"trips.txt" "trip_headsign" "JULES VERNES - M. AUBRY" 4
"trips.txt" "trip_headsign" "P.CLAUDEL - LOUVETS" 5
"trips.txt" "trip_headsign" "P.CLAUDEL - LOUVETS" 6
"trips.txt" "trip_headsign" "COLLEGE J. ROSTAND-M.AUBRY" 7
"trips.txt" "trip_headsign" "COLLEGE J. ROSTAND-M.AUBRY" 8
"trips.txt" "trip_headsign" "JEAN DE LA FONTAINE-ROOSEVELT" 9
"trips.txt" "trip_headsign" "LYCEE LA FONTAINE-MENNERORIE" 10
"trips.txt" "trip_headsign" "L'HORLOGE-JULES VERNE" 11
"trips.txt" "trip_headsign" "L'HORLOGE-LOUVETS" 12
"trips.txt" "trip_headsign" "LYCEE LA FONTAINE-L'HORLOGE" 13
"trips.txt" "trip_headsign" "JULES VERNE-LOUVETS" 14
"trips.txt" "trip_headsign" "LYCEE LA FONTAINE-CLOS LES VIGNES" 15
"trips.txt" "trip_headsign" "GARE SNCF-COLLEGE JEAN ROSTAND" 16
"trips.txt" "trip_headsign" "GARE SNCF-COLLEGE JEAN ROSTAND" 17
"trips.txt" "trip_headsign" "COLLEGE JEAN ROSTANC-GARE SNCF" 18
"trips.txt" "trip_headsign" "COLLEGE JEAN ROSTANC-GARE SNCF" 19
"trips.txt" "trip_headsign" "COLLEGE JEAN ROSTANC-GARE SNCF" 20
"trips.txt" "trip_headsign" "OTMUS-JEAN ROSTAND" 21
"trips.txt" "trip_headsign" "OTMUS-JEAN ROSTAND" 22
"trips.txt" "trip_headsign" "JEAN ROSTAND-OTMUS" 23
"trips.txt" "trip_headsign" "JEAN ROSTAND-OTMUS" 24
"trips.txt" "trip_headsign" "GARE SNCF-LOUVETS" 25
"trips.txt" "trip_headsign" "GARE SNCF-LOUVETS" 26
"trips.txt" "trip_headsign" "LA FONTAINE - GARESNCF" 27
"trips.txt" "trip_headsign" "LA FONTAINE - GARESNCF" 28
"trips.txt" "trip_headsign" "LA FONTAINE - GARESNCF" 29
"trips.txt" "trip_headsign" "CHIERRY-CHIERRY ECOLE" 30
"trips.txt" "trip_headsign" "CHIERRY ECOLE-BLESMES" 31
"trips.txt" "trip_headsign" "ESSOMES SUR MARNE VALLEE-ECOLE 204" 32
"trips.txt" "trip_headsign" "ESSOMES MONNEAUX-PLACE FERREOL" 33
"trips.txt" "trip_headsign" "BRASLES-BRASLES ECOLE" 34
"trips.txt" "trip_headsign" "BRASLES ECOLE-BRASLES" 35
"trips.txt" "trip_headsign" "MAUGUINS-MAUGUINS" 36
"trips.txt" "trip_headsign" "MAUGUINS - VINCELLES" 37
"trips.txt" "trip_headsign" "CHATEAU THIERRY-COLLEGE JEAN ROSTAND" 38
"trips.txt" "trip_headsign" "SOISSONS - ANIZY LE GRAND COLLEGE" 39
"trips.txt" "trip_short_name" "23SEGPA02A-1" 39
"trips.txt" "trip_headsign" "ANIZY LE GRAND COLL - SOISSONS" 40
"trips.txt" "trip_short_name" "23SEGPA02R-1" 40
"trips.txt" "trip_headsign" "ANIZY LE GRAND COLL - SOISSONS" 41
"trips.txt" "trip_short_name" "23SEGPA02R-2" 41
"trips.txt" "trip_headsign" "MAIZY - LAON COLLEGE JEAN MERMOZ" 42
"trips.txt" "trip_short_name" "23SEGPA04A-1" 42
"trips.txt" "trip_headsign" "LAON COLLEGE MERMOZ - MAIZY" 43
"trips.txt" "trip_short_name" "23SEGPA04R-1" 43
"trips.txt" "trip_headsign" "LAON COLLEGE MERMOZ - MAIZY" 44
"trips.txt" "trip_short_name" "23SEGPA04R-2" 44
"trips.txt" "trip_headsign" "ST QUENTIN CAFE DE L'HORLOGE-GRICOURT" 45
route_long_name_contains_short_name WARNING 1

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`.
"676-SEGPA|20210902" 13 "SEGPA" "Segpa Petits Vehicules"