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
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).
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
[WIP]
Errors
stop_times.arrival_time
is missing).UnexpectedEnumValueError All possible enum values are detailed in the spec.
InvalidRowLength This is an invalid record
MissingRequiredColumnError
MissingRequiredFileError
OverlappingFrequencyNotice
http://gtfs.org/reference/static#stopstxt
Warnings
stop_times.departure_time
is missing.DuplicatedColumnNotice
DuplicateKeyError
FieldParsingError (e.g invalid date/time/url etc) ForeignKeyError
MoreThanOneEntityNotice
UnknownColumnNotice
BlockTripsWithOverlappingStopTimesNotice
DuplicateRouteNameNotice
StopTimeWithArrivalBeforePreviousDepartureTimeNotice
StopTimeWithDepartureBeforeArrivalTimeNotice
StartAndEndTimeOutOfOrderNotice
RouteShortNameTooLongNotice
RouteShortAndLongNameEqualNotice
System errors