GTFS Schedule Validation Report

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape.	csvRowNumber (?) The row number from `shapes.txt`.	shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value.	shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`.	prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point.	prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value.	prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.	actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"shape_0244"	4081	13556.0	317	4080	13556.0	316	0.5365945335897657
"shape_0091"	1210	10283.0	237	1209	10283.0	236	0.5365945335897657
"shape_0221"	3146	8366.0	142	3145	8366.0	141	0.5346777455066593
"shape_0221"	3155	8411.0	151	3154	8411.0	150	0.18576344529775685

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape.	csvRowNumber (?) The row number from `shapes.txt`.	shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record.	shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`.	prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point.	prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point.	prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"shape_0269"	4469	2442.0	49	4468	2442.0	48
"shape_0158"	2405	3822.0	76	2404	3822.0	75

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.
2	"service_0001"

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	"20250422"	"20201231"	"20250429"

feed_info_lang_and_agency_lang_mismatch

Mismatching feed and agency language fields.

Files agency.txt and feed_info.txt should define matching agency.agency_lang and feed_info.feed_lang. The default language may be multilingual for datasets with the original text in multiple languages. In such cases, the feed_lang field should contain the language code mul defined by the norm ISO 639-2.

• If feed_lang is not mul and does not match with agency_lang, that's an error.
• If there is more than one agency_lang and feed_lang isn't mul, that's an error.
• If feed_lang is mul and there isn't more than one agency_lang, that's an error.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	agencyId (?) The agency id of the faulty record.	agencyName (?) The agency name of the faulty record.	agencyLang (?) The agency language of the faulty record.	feedLang (?) The feed language of the faulty record.
2	"socatur_duoala_02"	"Socatur Bus"	"fr"	"en"

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"fare_attributes.txt"	2	"agency_id"
"fare_attributes.txt"	3	"agency_id"
"fare_attributes.txt"	4	"agency_id"
"fare_attributes.txt"	5	"agency_id"
"fare_attributes.txt"	6	"agency_id"
"fare_attributes.txt"	7	"agency_id"
"fare_attributes.txt"	8	"agency_id"
"fare_attributes.txt"	9	"agency_id"
"fare_attributes.txt"	10	"agency_id"
"fare_attributes.txt"	11	"agency_id"
"fare_attributes.txt"	12	"agency_id"
"fare_attributes.txt"	13	"agency_id"
"fare_attributes.txt"	14	"agency_id"
"fare_attributes.txt"	15	"agency_id"
"fare_attributes.txt"	16	"agency_id"
"fare_attributes.txt"	17	"agency_id"
"fare_attributes.txt"	18	"agency_id"
"fare_attributes.txt"	19	"agency_id"
"fare_attributes.txt"	20	"agency_id"
"fare_attributes.txt"	21	"agency_id"

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.

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"	"carrefour douch"	36

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.
"20250422"	"20180606"	"20190706"

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row number of the faulty record.	fieldName (?) The name of the field where the error occurred.	fieldValue (?) Faulty value.
"routes.txt"	2	"route_type"	700
"routes.txt"	3	"route_type"	700
"routes.txt"	4	"route_type"	700
"routes.txt"	5	"route_type"	700
"routes.txt"	6	"route_type"	700
"routes.txt"	7	"route_type"	700
"routes.txt"	8	"route_type"	700
"routes.txt"	9	"route_type"	700
"routes.txt"	10	"route_type"	700
"routes.txt"	11	"route_type"	700
"routes.txt"	12	"route_type"	700
"routes.txt"	13	"route_type"	700
"routes.txt"	14	"route_type"	700
"routes.txt"	15	"route_type"	700
"routes.txt"	16	"route_type"	700
"routes.txt"	17	"route_type"	700
"routes.txt"	18	"route_type"	700
"routes.txt"	19	"route_type"	700
"routes.txt"	20	"route_type"	700
"routes.txt"	21	"route_type"	700