sopela-town-hall — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-29T07:56:56Z,
for the dataset file:///shared/sopela-town-hall_d15e0e69.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. fare_attributes.txt
  5. fare_rules.txt
  6. frequencies.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 4
  • Shapes: 11
  • Stops: 18
  • Trips: 33

Specification Compliance report

77 notices reported (0 errors, 10 warnings, 67 infos)

Notice Code Severity Total
expired_calendar WARNING 1

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 "1"
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"
mixed_case_recommended_field WARNING 7

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.
"trips.txt" "trip_headsign" "RESIDENCIA SOPELA" 31
"trips.txt" "trip_short_name" "L3_VER_RESIDENCIA" 31
"trips.txt" "trip_headsign" "PARKING ATXABIRIBIL" 32
"trips.txt" "trip_short_name" "L3_VER_PARKING" 32
"trips.txt" "trip_short_name" "L4_VER_MET" 33
"trips.txt" "trip_headsign" "PLAYA ARRIETARA" 34
"trips.txt" "trip_short_name" "L4_VER_PLA" 34
unused_shape WARNING 1

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.
"10" 147
trip_headsign_matches_intermediate_stop INFO 1

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
31 "30" "RESIDENCIA SOPELA" "11" 1 "10"
trip_with_shape_dist_traveled_but_no_shape_distances INFO 33

trip_with_shape_dist_traveled_but_no_shape_distances

A trip has shape_dist_traveled values in stop_times.txt but the shape referenced by the trip's shape_id does not have shape_dist_traveled values on all of its points in shapes.txt.

When stop times define distance values but the shape does not carry matching distances on every point, consumers cannot use those distances to align stops to the shape geometry reliably. This inconsistency may cause incorrect routing or display behaviour.

Note: Only the first stop time carrying a shape_dist_traveled value is referenced in the notice; this is a representative row rather than an exhaustive list.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record in trips.txt. tripId (?) The trip_id of the faulty trip. shapeId (?) The shape_id referenced by the trip. stopTimeCsvRowNumber (?) The row number of the first stop_times.txt record for this trip that contains a shape_dist_traveled value. Provided as a representative location; other stop times for the same trip may also carry distance values.
21 "22" "2" 153
22 "23" "2" 158
23 "24" "3" 165
24 "25" "4" 171
25 "26" "3" 186
26 "27" "3" 197
27 "28" "3" 208
28 "29" "3" 219
31 "30" "6" 234
32 "31" "7" 249
9 "10" "4" 12
33 "32" "8" 255
10 "11" "5" 26
34 "33" "9" 266
11 "12" "4" 32
12 "13" "3" 47
13 "14" "5" 57
14 "15" "11" 64
15 "16" "5" 78
16 "17" "11" 85
17 "18" "3" 100
18 "19" "11" 107
2 "1" "1" 2
3 "2" "1" 117
4 "3" "1" 224
5 "4" "1" 269
6 "5" "1" 278
7 "6" "1" 287
8 "7" "1" 296
29 "8" "2" 309
30 "9" "3" 316
19 "20" "3" 132
20 "21" "11" 139
unsorted_stop_times INFO 33

unsorted_stop_times

Stop times are not sorted by trip_id and stop_sequence.

'stop_times.txt' entries for a given trip are not sorted by stop_sequence, or are not contiguous in the file.

You can see more about this notice here.

tripId (?) The faulty record's trip_id. startCsvRowNumber (?) CSV row number of the first stop_times entry for this trip. endCsvRowNumber (?) CSV row number of the last stop_times entry for this trip.
"22" 149 153
"23" 154 158
"24" 159 169
"25" 170 179
"26" 180 190
"27" 191 201
"28" 202 212
"29" 213 223
"30" 233 243
"31" 244 254
"10" 11 20
"32" 255 261
"11" 21 30
"33" 262 268
"12" 31 40
"13" 41 51
"14" 52 61
"15" 62 72
"16" 73 82
"17" 83 93
"18" 94 104
"19" 105 116
"1" 2 10
"2" 117 125
"3" 224 232
"4" 269 277
"5" 278 286
"6" 287 295
"7" 296 304
"8" 305 309
"9" 310 320
"20" 126 136
"21" 137 148