GTFS Schedule Validation Report

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file	oldCsvRowNumber (?) The row of the first occurrence.	newCsvRowNumber (?) The row of the other occurrence.	fieldName1 (?) Composite key's first field name.	fieldValue1 (?) Composite key's first value.
"calendar_dates.txt"	9545	9546	"service_id,date"	"4178,20240120"
"calendar_dates.txt"	9666	9667	"service_id,date"	"4181,20240120"
"calendar_dates.txt"	9787	9788	"service_id,date"	"4184,20240120"
"calendar_dates.txt"	9908	9909	"service_id,date"	"4187,20240120"
"calendar_dates.txt"	10097	10098	"service_id,date"	"4192,20240120"
"calendar_dates.txt"	10218	10219	"service_id,date"	"4195,20240120"
"calendar_dates.txt"	10339	10340	"service_id,date"	"4242,20240120"
"calendar_dates.txt"	10460	10461	"service_id,date"	"4248,20240120"
"calendar_dates.txt"	10581	10582	"service_id,date"	"4251,20240120"
"calendar_dates.txt"	10702	10703	"service_id,date"	"4254,20240120"
"calendar_dates.txt"	10823	10824	"service_id,date"	"4257,20240120"
"calendar_dates.txt"	33138	33139	"service_id,date"	"5577,20240120"
"calendar_dates.txt"	33259	33260	"service_id,date"	"5580,20240120"

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.
34	"3433"

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.
"feed_info.txt"	2	"feed_start_date"
"feed_info.txt"	2	"feed_end_date"
"feed_info.txt"	2	"feed_version"
"routes.txt"	2	"agency_id"
"routes.txt"	3	"agency_id"
"routes.txt"	4	"agency_id"
"routes.txt"	5	"agency_id"
"routes.txt"	6	"agency_id"
"routes.txt"	7	"agency_id"
"routes.txt"	8	"agency_id"
"routes.txt"	9	"agency_id"
"routes.txt"	10	"agency_id"
"routes.txt"	11	"agency_id"

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 9800 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	"3675"	0
3	"3675"	1
4	"3675"	2
5	"3675"	3
6	"3676"	0
7	"3676"	1
8	"3676"	2
9	"3676"	3
10	"4566"	0
11	"4566"	1
12	"4566"	2
13	"4566"	3
14	"4567"	0
15	"4567"	1
16	"4567"	2
17	"4567"	3
18	"4568"	0
19	"4568"	1
20	"4568"	2
21	"4568"	3
22	"4569"	0
23	"4569"	1
24	"4569"	2
25	"4569"	3
26	"4182"	0
27	"4182"	1
28	"4182"	2
29	"4182"	3
30	"4182"	4
31	"4182"	5
32	"4182"	6
33	"4182"	7
34	"4182"	8
35	"3410"	0
36	"3410"	1
37	"3410"	2
38	"3410"	3
39	"3410"	4
40	"3410"	5
41	"3410"	6
42	"3410"	7
43	"3410"	8
44	"3410"	9
45	"3411"	0
46	"3411"	1
47	"3411"	2
48	"3411"	3
49	"3411"	4
50	"3411"	5
51	"3411"	6

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 1035 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.
"agency.txt"	"agency_name"	"LES NAVETTES DU GIFFRE"	2
"routes.txt"	"route_long_name"	"LIGNE 2 BLEUE"	3
"routes.txt"	"route_long_name"	"LIGNE 5 BLANCHE"	5
"stops.txt"	"stop_name"	"CHATILLON SUR CLUSES - MAIRIE"	2
"stops.txt"	"stop_name"	"CHATILLON SUR CLUSES - MAIRIE"	3
"stops.txt"	"stop_name"	"FLAINE - FORUM"	4
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - CHEF LIEU"	5
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - CHEF LIEU"	6
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - GRAND MARVEL"	7
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - GRAND MARVEL"	8
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - LA GROTTE"	9
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - LA GROTTE"	10
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - LE PLAN"	11
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - LE PLAN"	12
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - PETIT MARVEL"	13
"stops.txt"	"stop_name"	"LA RIVIERE ENVERSE - PETIT MARVEL"	14
"stops.txt"	"stop_name"	"MORILLON - BOIS CHAMPELLE"	15
"stops.txt"	"stop_name"	"MORILLON - BOIS CHAMPELLE"	16
"stops.txt"	"stop_name"	"MORILLON - CCAS"	17
"stops.txt"	"stop_name"	"MORILLON - CCAS"	18
"stops.txt"	"stop_name"	"MORILLON - LA PERRIÈRE"	19
"stops.txt"	"stop_name"	"MORILLON - LE GRAND CHAMP"	20
"stops.txt"	"stop_name"	"MORILLON - MAIRIE / ECOLE"	21
"stops.txt"	"stop_name"	"MORILLON - OURSON BAS"	22
"stops.txt"	"stop_name"	"MORILLON - OURSON BAS"	23
"stops.txt"	"stop_name"	"MORILLON - OURSON HAUT"	24
"stops.txt"	"stop_name"	"MORILLON - TÉLÉCABINE"	25
"stops.txt"	"stop_name"	"MORILLON - TÉLÉCABINE"	26
"stops.txt"	"stop_name"	"MORILLON - VERNEY D'EN HAUT"	27
"stops.txt"	"stop_name"	"SAMOENS - ANCIENNE FRUITIERE"	28
"stops.txt"	"stop_name"	"SAMOENS - AVENUE DES LOISIRS"	29
"stops.txt"	"stop_name"	"SAMOENS - CINEMA"	30
"stops.txt"	"stop_name"	"SAMOENS - CLOS MOCCANS BAS"	31
"stops.txt"	"stop_name"	"SAMOENS - CLOS MOCCANS HAUT"	32
"stops.txt"	"stop_name"	"SAMOENS - CLOS PARCHET"	33
"stops.txt"	"stop_name"	"SAMOENS - CLOS PARCHET"	34
"stops.txt"	"stop_name"	"SAMOENS - ETELLEY"	35
"stops.txt"	"stop_name"	"SAMOENS - ETELLEY"	36
"stops.txt"	"stop_name"	"SAMOENS - FONTAINE DES VALLONS"	37
"stops.txt"	"stop_name"	"SAMOENS - FONTANYS"	38
"stops.txt"	"stop_name"	"SAMOENS - GRAND MASSIF EXPRESS"	39
"stops.txt"	"stop_name"	"SAMOENS - JOUX PLANE"	40
"stops.txt"	"stop_name"	"SAMOENS - LAC AUX DAMES"	41
"stops.txt"	"stop_name"	"SAMOENS - LE BÉROUZE"	42
"stops.txt"	"stop_name"	"SAMOENS - LE PETIT SAIX"	43
"stops.txt"	"stop_name"	"SAMOENS - LE PETIT SAIX"	44
"stops.txt"	"stop_name"	"SAMOENS - LE QUART"	45
"stops.txt"	"stop_name"	"SAMOENS - LES FONTAINES"	46
"stops.txt"	"stop_name"	"SAMOENS - LES MOULINS"	47
"stops.txt"	"stop_name"	"SAMOENS - LES PERTUETS"	48

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.
"159"	3	"#0883E8"	"#F77C17"
"163"	6	"#FF4FA7"	"#00B058"
"166"	9	"#00FF00"	"#FF00FF"
"167"	10	"#00B050"	"#FF4FAF"

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`.
"158"	2	"L1JAUNE"	"L1JAUNE"
"160"	4	"L3TURQUOISE"	"L3TURQUOISE"
"163"	6	"L6ROSE"	"L6ROSE"
"164"	7	"L7ORANGE"	"L7ORANGE"
"165"	8	"L8ROUGE"	"L8ROUGE"
"166"	9	"L9VERTE"	"L9VERTE"
"167"	10	"L9.1VERTE"	"L9.1VERTE"
"168"	11	"L11MARRON"	"L11MARRON"