GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T23:07:06Z,
for the dataset file:///shared/gtfs-transports-a-la-demande-tad-coqueligo.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 4
  • Shapes: 32
  • Stops: 50
  • Trips: 32

Specification Compliance report

256 notices reported (0 errors, 256 warnings, 0 infos)

Notice Code Severity Total
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
missing_timepoint_value WARNING 246

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 246 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 "701c3581-0378-4d53-b6fc-3c678bc40014" 1
3 "701c3581-0378-4d53-b6fc-3c678bc40014" 2
4 "701c3581-0378-4d53-b6fc-3c678bc40014" 3
5 "701c3581-0378-4d53-b6fc-3c678bc40014" 4
6 "701c3581-0378-4d53-b6fc-3c678bc40014" 5
7 "701c3581-0378-4d53-b6fc-3c678bc40014" 6
8 "701c3581-0378-4d53-b6fc-3c678bc40014" 7
9 "4488b5c4-7327-4071-aab6-b4f12581aeba" 1
10 "4488b5c4-7327-4071-aab6-b4f12581aeba" 2
11 "4488b5c4-7327-4071-aab6-b4f12581aeba" 3
12 "4488b5c4-7327-4071-aab6-b4f12581aeba" 4
13 "4488b5c4-7327-4071-aab6-b4f12581aeba" 5
14 "4488b5c4-7327-4071-aab6-b4f12581aeba" 6
15 "4488b5c4-7327-4071-aab6-b4f12581aeba" 7
16 "70bae3a7-bce1-4a7e-899b-304689fb8c62" 1
17 "70bae3a7-bce1-4a7e-899b-304689fb8c62" 2
18 "70bae3a7-bce1-4a7e-899b-304689fb8c62" 3
19 "70bae3a7-bce1-4a7e-899b-304689fb8c62" 4
20 "70bae3a7-bce1-4a7e-899b-304689fb8c62" 5
21 "70bae3a7-bce1-4a7e-899b-304689fb8c62" 6
22 "70bae3a7-bce1-4a7e-899b-304689fb8c62" 7
23 "dec4f4b7-f6e7-43ce-9149-1f0b6a57bcb8" 1
24 "dec4f4b7-f6e7-43ce-9149-1f0b6a57bcb8" 2
25 "dec4f4b7-f6e7-43ce-9149-1f0b6a57bcb8" 3
26 "dec4f4b7-f6e7-43ce-9149-1f0b6a57bcb8" 4
27 "dec4f4b7-f6e7-43ce-9149-1f0b6a57bcb8" 5
28 "dec4f4b7-f6e7-43ce-9149-1f0b6a57bcb8" 6
29 "dec4f4b7-f6e7-43ce-9149-1f0b6a57bcb8" 7
30 "87a57818-ee16-4259-90ad-93ba80e4033a" 1
31 "87a57818-ee16-4259-90ad-93ba80e4033a" 2
32 "87a57818-ee16-4259-90ad-93ba80e4033a" 3
33 "87a57818-ee16-4259-90ad-93ba80e4033a" 4
34 "87a57818-ee16-4259-90ad-93ba80e4033a" 5
35 "87a57818-ee16-4259-90ad-93ba80e4033a" 6
36 "87a57818-ee16-4259-90ad-93ba80e4033a" 7
37 "d1ffc9a4-c66d-4875-8c7f-56aec43d3e49" 1
38 "d1ffc9a4-c66d-4875-8c7f-56aec43d3e49" 2
39 "d1ffc9a4-c66d-4875-8c7f-56aec43d3e49" 3
40 "d1ffc9a4-c66d-4875-8c7f-56aec43d3e49" 4
41 "d1ffc9a4-c66d-4875-8c7f-56aec43d3e49" 5
42 "d1ffc9a4-c66d-4875-8c7f-56aec43d3e49" 6
43 "d1ffc9a4-c66d-4875-8c7f-56aec43d3e49" 7
44 "0b762d20-ab98-4ec9-8c83-42281c10573c" 1
45 "0b762d20-ab98-4ec9-8c83-42281c10573c" 2
46 "0b762d20-ab98-4ec9-8c83-42281c10573c" 3
47 "0b762d20-ab98-4ec9-8c83-42281c10573c" 4
48 "0b762d20-ab98-4ec9-8c83-42281c10573c" 5
49 "0b762d20-ab98-4ec9-8c83-42281c10573c" 6
50 "0b762d20-ab98-4ec9-8c83-42281c10573c" 7
51 "70e2781a-9cc2-4fde-ad5b-b66d3b4999ce" 1
mixed_case_recommended_field WARNING 4

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.
"routes.txt" "route_long_name" "TAD 1 ST-JULIEN-VOCANCE <> ANNONAY GARE ROUTIERE" 2
"routes.txt" "route_long_name" "TAD 2 LE MONESTIER <> ANNONAY GARE ROUTIERE" 3
"routes.txt" "route_long_name" "TAD 3 SAVAS <> ANNONAY GARE ROUTIERE" 4
"routes.txt" "route_long_name" "TAD 4 TALENCIEUX CENTRE <> ANNONAY GARE ROUTIERE" 5
route_color_contrast WARNING 1

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.
"TAD-2" 3 "#8EEDDD" "#FFFFFF"
route_long_name_contains_short_name WARNING 4

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`.
"TAD-1" 2 "TAD 1" "TAD 1 ST-JULIEN-VOCANCE <> ANNONAY GARE ROUTIERE"
"TAD-2" 3 "TAD 2" "TAD 2 LE MONESTIER <> ANNONAY GARE ROUTIERE"
"TAD-3" 4 "TAD 3" "TAD 3 SAVAS <> ANNONAY GARE ROUTIERE"
"TAD-4" 5 "TAD 4" "TAD 4 TALENCIEUX CENTRE <> ANNONAY GARE ROUTIERE"