Home
Spain Feeds
lurraldebus-ekialdebus-esp
Source Data Validation Report

lurraldebus-ekialdebus-esp — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T03:21:36Z,
for the dataset file:///shared/lurraldebus-ekialdebus-esp_cb018408.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Lur-e-01_ekialdebus S.l.
- website: https://ekialdebus.eus/
- phone number: 900300340
- email: Not provided

Feed Info

Publisher Name:
Ingartek Consulting: Publisher URL:
https://www.ingartek.com/: Feed Email:
sanchez@gmail.com: Feed Language:
Spanish: Feed Start Date:
2026-04-20: Feed End Date:
2026-07-19: Service Window:
2026-04-20 to 2026-07-19 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 31
Shapes: 87
Stops: 231
Trips: 4869

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Shapes Feed Information Route Colors Headsigns Trips Wheelchair Accessibility Bike Allowed Location Types

Specification Compliance report

1037 notices reported (1021 errors, 16 warnings, 0 infos)

Notice Code Severity Total

foreign_key_violation ERROR 1021

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

Only the first 50 of 1021 affected records are displayed below.

childFilename (?) The name of the file from which reference is made.	childFieldName (?) The name of the field that makes reference.	parentFilename (?) The name of the file that is referred to.	parentFieldName (?) The name of the field that is referred to.	fieldValue (?) The faulty record's value.	csvRowNumber (?) The row of the faulty record.
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	4
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	6
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	7
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	16
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	33
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	38
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	46
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	48
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	49
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	61
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	63
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	64
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	65
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	67
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	78
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	81
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	84
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	87
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	96
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	109
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	110
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	112
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	113
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	116
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	119
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	122
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	130
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	131
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	136
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	146
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	147
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	152
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	166
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	168
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	170
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	177
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	178
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	179
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	181
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	184
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	186
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	188
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	190
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	212
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	218
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	221
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	222
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	226
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	231
"trips.txt"	"service_id"	"calendar.txt or calendar_dates.txt"	"service_id"	"J"	236

mixed_case_recommended_field WARNING 8

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"	"E23-hondarribia>irun (mendeb/oest)>donostia (ap-8)"	3
"routes.txt"	"route_long_name"	"E24-irun>donostia (ap-8)"	4
"routes.txt"	"route_long_name"	"E29-hondarribia>irun>donostia (ospitaleak)"	9
"routes.txt"	"route_long_name"	"E71-p.donibane>lezo>errenteria>p.antxo>donostia (n-i)"	10
"routes.txt"	"route_long_name"	"E72-oiartzun>errenteria>pasaia>donostia (n-i)"	12
"routes.txt"	"route_long_name"	"E78-hondarriba>irun"	18
"routes.txt"	"route_long_name"	"E01-p.donibane>lezo>errenteria>p.antxo>donostia (n-i)"	22
"routes.txt"	"route_long_name"	"E04-oiartzun>errenteria>donostia (ap-8)"	25

route_long_name_contains_short_name WARNING 8

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`.
"23"	3	"E23"	"E23-hondarribia>irun (mendeb/oest)>donostia (ap-8)"
"24"	4	"E24"	"E24-irun>donostia (ap-8)"
"29"	9	"E29"	"E29-hondarribia>irun>donostia (ospitaleak)"
"71"	10	"E71"	"E71-p.donibane>lezo>errenteria>p.antxo>donostia (n-i)"
"72"	12	"E72"	"E72-oiartzun>errenteria>pasaia>donostia (n-i)"
"78"	18	"E78"	"E78-hondarriba>irun"
"1"	22	"E01"	"E01-p.donibane>lezo>errenteria>p.antxo>donostia (n-i)"
"4"	25	"E04"	"E04-oiartzun>errenteria>donostia (ap-8)"