GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T21:56:21Z,
for the dataset file:///shared/horariosdofunchal.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
Portuguese
Feed Start Date:
2025-11-29
Feed End Date:
2026-06-30

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: 91
  • Shapes: 255
  • Stops: 1729
  • Trips: 4575

Specification Compliance report

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

Notice Code Severity Total
mixed_case_recommended_field WARNING 1

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.
"stops.txt" "stop_name" "APS dos CTT S (857b)" 1011
stop_has_too_many_matches_for_shape WARNING 4

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.
4561 "1033-251" "1033-181_J_1_1800_1829_0_UE_034" 136569 "1033-013201" "CAM Seara Velha Baixo (13201)" [32.70780911398806,-16.973485063269088] 26
4561 "1033-251" "1033-181_J_1_1800_1829_0_UE_034" 136570 "1033-013202" "TV Seara Velha Baixo (13202)" [32.7073469264019,-16.97200104589063] 21
4561 "1033-251" "1033-181_J_1_1800_1829_0_UE_034" 136573 "1033-013205" "CAM Seara Velha Baixo (13205)" [32.707813,-16.973444999999998] 31
4561 "1033-251" "1033-181_J_1_1800_1829_0_UE_034" 136577 "1033-013205" "CAM Seara Velha Baixo (13205)" [32.707813,-16.973444999999998] 31