GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-24T01:38:04Z,
for the dataset file:///shared/salamanca-de-transportes-eps.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_dates.txt
  3. routes.txt
  4. shapes.txt
  5. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 109
  • Shapes: 109
  • Stops: 349
  • Trips: 82410

Specification Compliance report

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

Notice Code Severity Total
leading_or_trailing_whitespaces WARNING 2

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stops.txt" 16 "stop_name" "C/ Coria s/n (Junto Iglesia) "
"stops.txt" 344 "stop_name" "C/ Abraham Zacut s/n "
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 42340

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 42340 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.
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 2
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 4
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 6
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 8
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 10
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 12
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 14
"trips.txt" "trip_headsign" "HUERTA OTEA" 24
"trips.txt" "trip_headsign" "SAN JOSE" 25
"trips.txt" "trip_headsign" "HUERTA OTEA" 26
"trips.txt" "trip_headsign" "SAN JOSE" 27
"trips.txt" "trip_headsign" "HUERTA OTEA" 28
"trips.txt" "trip_headsign" "SAN JOSE" 29
"trips.txt" "trip_headsign" "HUERTA OTEA" 30
"trips.txt" "trip_headsign" "SAN JOSE" 31
"trips.txt" "trip_headsign" "HUERTA OTEA" 32
"trips.txt" "trip_headsign" "SAN JOSE" 33
"trips.txt" "trip_headsign" "HUERTA OTEA" 34
"trips.txt" "trip_headsign" "SAN JOSE" 35
"trips.txt" "trip_headsign" "HUERTA OTEA" 36
"trips.txt" "trip_headsign" "SAN JOSE" 37
"trips.txt" "trip_headsign" "BUENOS AIRES" 53
"trips.txt" "trip_headsign" "BUENOS AIRES" 55
"trips.txt" "trip_headsign" "BUENOS AIRES" 57
"trips.txt" "trip_headsign" "BUENOS AIRES" 59
"trips.txt" "trip_headsign" "BUENOS AIRES" 61
"trips.txt" "trip_headsign" "SAN JOSE" 63
"trips.txt" "trip_headsign" "SAN JOSE" 65
"trips.txt" "trip_headsign" "SAN JOSE" 67
"trips.txt" "trip_headsign" "SAN JOSE" 69
"trips.txt" "trip_headsign" "SAN JOSE" 71
"trips.txt" "trip_headsign" "SAN JOSE" 73
"trips.txt" "trip_headsign" "SAN JOSE" 75
"trips.txt" "trip_headsign" "SAN JOSE" 78
"trips.txt" "trip_headsign" "SAN JOSE" 80
"trips.txt" "trip_headsign" "SAN JOSE" 82
"trips.txt" "trip_headsign" "SAN JOSE" 84
"trips.txt" "trip_headsign" "SAN JOSE" 86
"trips.txt" "trip_headsign" "SAN JOSE" 88
"trips.txt" "trip_headsign" "SAN JOSE" 90
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 91
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 93
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 95
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 97
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 99
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 102
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 104
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 106
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 108
"trips.txt" "trip_headsign" "PUENTE LADRILLO" 110
stop_without_stop_time WARNING 2

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.
313 "326" "Eco-Raya"
314 "327" "Feria Monografica"
unused_shape WARNING 19

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.
"6990011" 1764
"990011" 2164
"6990022" 2693
"990022" 3343
"980011" 4286
"980022" 5211
"130052" 6058
"960011" 7886
"960022" 8939
"960031" 10173
"950011" 10719
"100031" 11047
"960042" 11230
"950022" 12092
"100052" 13087
"940011" 13217
"940022" 14184
"930011" 14964
"930022" 15744