GTFS Schedule Validation Report

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip.	tripIdA (?) The id of first faulty trip.	serviceIdA (?) The service id of the first faulty trip.	csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip.	tripIdB (?) The id of the other faulty trip.	serviceIdB (?) The service id of the other faulty trip.	blockId (?) The `trips.block_id` of the overlapping trip.	intersection (?) The overlapping period.
17438	"115565889"	"WK"	12347	"115565985"	"WK"	"a_FF 57"	"20250902"

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

Only the first 50 of 78 affected records are displayed below.

childFilename (?) The name of the file from which reference is made.	childFieldName (?) The name of the field that makes reference.	parentFilename (?) The name of the file that is referred to.	parentFieldName (?) The name of the field that is referred to.	fieldValue (?) The faulty record's value.	csvRowNumber (?) The row of the faulty record.
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	2
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	3
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	4
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	5
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	6
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	7
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	8
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	9
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	10
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	11
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	12
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	13
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	14
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	15
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	16
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	17
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	18
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	19
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	20
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	21
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	22
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	23
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	24
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	25
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	26
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	27
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	28
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	29
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	30
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	31
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"free_service"	32
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	33
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	34
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	35
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	36
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	37
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	38
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	39
"fare_leg_rules.txt"	"from_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	40
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	2
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"free_service"	3
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	4
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	5
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"free_service"	6
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	7
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"airport_fare_zone"	8
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"free_service"	9
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	10
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	11
"fare_leg_rules.txt"	"to_area_id"	"areas.txt"	"area_id"	"local_fare_zone"	12

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.
12	"FR_3787"

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_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

Only the first 50 of 100000 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record.	tripId (?) The faulty record's `stop_times.trip_id`.	stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2	"115569574"	1
3	"115569574"	2
4	"115569574"	3
5	"115569574"	4
6	"115569574"	5
7	"115569574"	6
8	"115569574"	7
9	"115569574"	8
10	"115569574"	9
11	"115569574"	10
12	"115569574"	11
13	"115569574"	12
14	"115569574"	13
15	"115569574"	14
16	"115569574"	15
17	"115569574"	16
18	"115569574"	17
19	"115569574"	18
20	"115569574"	19
21	"115569575"	1
22	"115569575"	2
23	"115569575"	3
24	"115569575"	4
25	"115569575"	5
26	"115569575"	6
27	"115569575"	7
28	"115569575"	8
29	"115569575"	9
30	"115569575"	10
31	"115569575"	11
32	"115569575"	12
33	"115569575"	13
34	"115569575"	14
35	"115569575"	15
36	"115569575"	16
37	"115569575"	17
38	"115569575"	18
39	"115569575"	19
40	"115547778"	1
41	"115547778"	2
42	"115547778"	3
43	"115547778"	4
44	"115547778"	5
45	"115547778"	6
46	"115547778"	7
47	"115547778"	8
48	"115547778"	9
49	"115547778"	10
50	"115547778"	11
51	"115547778"	12

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"	"CO 93 & CO 72"	1100
"stops.txt"	"stop_name"	"CO 119 & CO 52"	1508
"stops.txt"	"stop_name"	"CO 93 & CO 128"	1607
"stops.txt"	"stop_name"	"CO 93 & CO 128"	1608
"stops.txt"	"stop_name"	"CO 119 & CO 52"	4084
"stops.txt"	"stop_name"	"CO 93 & CO 72"	4923
"stops.txt"	"stop_name"	"US 287 & CO 52"	6825
"stops.txt"	"stop_name"	"US 287 & CO 52"	6826

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeColor (?) The faulty record's HTML route color.	routeTextColor (?) The faulty record's HTML route text color.
"101S"	71	"#FFFBF0"	"#FFFFFF"

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`.
"ART"	121	"ART"	"Art District Connector"

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
5410	"22924"	"Den Commercial Vehicle Holding Area"

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

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.	stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`.	stopId1 (?) The id of the first stop that is referred to.	stopName1 (?) The name of the first stop that is referred to.	match1 (?) Latitude and longitude pair of the first matching location.	stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`.	stopId2 (?) The id of the second stop that is referred to.	stopName2 (?) The name of the second stop that is referred to.	match2 (?) Latitude and longitude pair of the second matching location.
6471	"1317049"	"115551502"	232945	"34393"	"S Santa Fe Dr & Blakeland Dr"	[39.56060995307064,-105.03628991526678]	232944	"22252"	"S Santa Fe Dr & W County Line Rd"	[39.56745839882311,-105.0316204073135]
6241	"1317047"	"115551487"	224218	"34394"	"S Santa Fe Dr & Blakeland Dr"	[39.560528,-105.03648600000001]	224217	"25035"	"S Santa Fe Dr & Midway Dr"	[39.547411165757254,-105.03653656512391]
20312	"1317050"	"115551556"	752326	"34393"	"S Santa Fe Dr & Blakeland Dr"	[39.56060995307064,-105.03628991526678]	752325	"22252"	"S Santa Fe Dr & W County Line Rd"	[39.56745839882311,-105.0316204073135]

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id.	csvRowNumber (?) The row number of the faulty record.
"1317851"	50062
"1317872"	100324
"1317873"	207250
"1316767"	604472