MobilityData / gtfs-validator

Canonical GTFS Validator project for schedule (static) files.
https://gtfs-validator.mobilitydata.org/
Apache License 2.0
278 stars 100 forks source link

list validator's errors and warnings #709

Closed lionel-nj closed 3 years ago

lionel-nj commented 3 years ago

[WIP]

Errors

An arrival time must be specified for the first and the last stop in a trip. http://gtfs.org/reference/static#stop_timestxt

The field must be included in the dataset, and a value must be provided in that field for each record. http://gtfs.org/reference/static#term-definitions

Multiple headways for the same trip are allowed, but may not overlap. http://gtfs.org/reference/static#frequenciestxt

Values must increase along with shape_pt_sequence http://gtfs.org/reference/static#shapestxt

Values used for shape_dist_traveled must increase along with stop_sequence http://gtfs.org/reference/static#stop_timestxt

Do not simply duplicate the name of the route. http://gtfs.org/reference/static#routestxt

The color difference between route_color and route_text_color should provide sufficient contrast when viewed on a black and white screen. http://gtfs.org/reference/static#routestxt

Stop/platform (location_type=0): the parent_station field contains the ID of a station. http://gtfs.org/reference/static#stopstxt

Station (location_type=1): this field must be empty. http://gtfs.org/reference/static#stopstxt

Defines hierarchy between the different locations defined in stops.txt. It contains the ID of the parent location, as followed: • Stop/platform (location_type=0): the parent_station field contains the ID of a station. • Station (location_type=1): this field must be empty. • Entrance/exit (location_type=2) or generic node (location_type=3): the parent_station field contains the ID of a station (location_type=1) • Boarding Area (location_type=4): the parent_station field contains ID of a platform.

Conditionally Required: • Required for locations which are entrances (location_type=2), generic nodes (location_type=3) or boarding areas (location_type=4). • Optional for stops/platforms (location_type=0). • Forbidden for stations (location_type=1).

http://gtfs.org/reference/static#stopstxt

Either route_short_name or route_long_name must be specified, http://gtfs.org/reference/static/#routestxt

Using only printable ASCII characters is recommended. http://gtfs.org/reference/static/#field-types

Warnings

An arrival time must be specified for the first and the last stop in a trip. http://gtfs.org/reference/static#stop_timestxt

route_long_name should not contain the route_short_name. http://gtfs.org/best-practices/#routestxt

At any time, the published GTFS dataset should be valid for at least the next 7 days, and ideally for as long as the operator is confident that the schedule will continue to be operated. If possible, the GTFS dataset should cover at least the next 30 days of service. http://gtfs.org/best-practices/#dataset-publishing--general-practices

System errors