This report was generated by the Canonical GTFS Schedule
validator,
version 7.1.0 at 2025-12-12T16:52:03Z,
for the dataset
file:///shared/transportes-de-murcia.zip. No country code was provided.
Use this report alongside our documentation.
| Notice Code | Severity | Total | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| duplicate_route_name | WARNING | 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
duplicate_route_nameTwo distinct routes have either the same All routes of the same Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route. Example of bad data:
You can see more about this notice here.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| leading_or_trailing_whitespaces | WARNING | 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
leading_or_trailing_whitespacesThe 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.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| missing_recommended_file | WARNING | 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
missing_recommended_fileA recommended file is missing. You can see more about this notice here.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| mixed_case_recommended_field | WARNING | 13 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
mixed_case_recommended_fieldThis 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.
You can see more about this notice here.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| route_long_name_contains_short_name | WARNING | 13 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
route_long_name_contains_short_nameLong name should not contain short name for a single route. In routes.txt, Good examples:
Bad examples:
You can see more about this notice here.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||