GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-24T18:58:06Z,
for the dataset file:/tmp/gtfs-validator-temp16825868275774537662/e77aedad-f377-4efd-ad5e-787ba50decf612742269227025747564.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Metro Malaga
Publisher URL:
https://metromalaga.es/
Feed Email:
N/A
Feed Language:
Spanish
Feed Start Date:
2026-08-12
Feed End Date:
2026-10-07

Files included

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

Counts

  • Agencies: 1
  • Blocks: 5114
  • Routes: 2
  • Shapes: 4
  • Stops: 25
  • Trips: 5114

Specification Compliance report

3 notices reported (0 errors, 2 warnings, 1 infos)

Notice Code Severity Total
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

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. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
4552 "L2V1" "M12_26_01_ogt_206_3001_L2V1" 47423 "PRI" "Princesa - Huelin" [36.70425208894264,-4.440060701424793] 47422 "GD2" "Guadalmedina - L2" [36.7173867,-4.42936778]
trip_headsign_matches_intermediate_stop INFO 1

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
4552 "M12_26_01_ogt_206_3001_L2V1" "Guadalmedina - L2" "GD2" 4 "PRI"