Search
  1. Home
  2. Spain Feeds
  3. sopela-town-hall
  4. Source Data Validation Report

sopela-town-hall — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T11:10:53Z,
for the dataset file:///shared/sopela-town-hall_72a6aae0.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Feed Info

Publisher Name:
AddTransit
Publisher URL:
https://addtransit.com
Feed Email:
gtfs@addtransit.com
Feed Language:
Spanish
Feed Start Date:
2025-10-01
Feed End Date:
2026-09-30

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. trips.txt

Counts

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

Specification Compliance report

14 notices reported (2 errors, 12 warnings, 0 infos)

Notice Code Severity Total
start_and_end_range_out_of_order ERROR 2

start_and_end_range_out_of_order

Two date or time fields are out of order.

Date or time fields have been found out of order in calendar.txt, feed_info.txt and stop_times.txt.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. entityId (?) The faulty service id. startFieldName (?) The start value's field name. startValue (?) The start value. endFieldName (?) The end value's field name. endValue (?) The end value.
"calendar.txt" 3 "3" "start_date" "20260601" "end_date" "20250930"
"calendar.txt" 5 "4" "start_date" "20260724" "end_date" "20251011"
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
unexpected_enum_value WARNING 4

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. fieldName (?) The name of the field where the error occurred. fieldValue (?) Faulty value.
"routes.txt" 2 "route_type" 700
"routes.txt" 3 "route_type" 700
"routes.txt" 4 "route_type" 700
"routes.txt" 5 "route_type" 700
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