GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-13T05:00:35Z,
for the dataset file:///shared/lurraldebus-ekialdebus-esp.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Ingartek Consulting
Publisher URL:
https://www.ingartek.com/
Feed Email:
sanchez@gmail.com
Feed Language:
Spanish
Feed Start Date:
2025-12-08
Feed End Date:
2025-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 26
  • Shapes: 78
  • Stops: 229
  • Trips: 5778

Specification Compliance report

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

Notice Code Severity Total
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20251213" "20251231" "20260112"
mixed_case_recommended_field WARNING 2

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" "E71 P.donibane>lezo>errente>p.antxo>donostia (n-i)*" 10
"routes.txt" "route_long_name" "E01 P.donibane>lezo>errente>p.antxo>donostia (n-i)" 17
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 (ospitaletik)"
"71" 10 "E71" "E71 P.donibane>lezo>errente>p.antxo>donostia (n-i)*"
"72" 11 "E72" "E72 Oiartzun>errenteria>pasaia>donostia (n-i)*"
"78" 14 "E78" "E78 Hondarribia>irun*"
"1" 17 "E01" "E01 P.donibane>lezo>errente>p.antxo>donostia (n-i)"
"4" 20 "E04" "E04 Oiartzun>errenteria>donostia (ap-8)"
stop_has_too_many_matches_for_shape WARNING 1

stop_has_too_many_matches_for_shape

Stop entry that has many potential matches to the trip's path of travel, as defined by the shape entry in shapes.txt.

This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. matchCount (?) The number of matches for the stop that is referred to.
118 "shp_27_2704" "27_2704_4_80700" 3783 "53" "Hondarribia - Sabin Arana - Ama Guadalupekoa Ikastetxea" [43.365551563116526,-1.7923618757356286] 21