GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T21:56:26Z,
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:
HF
Feed Email:
geral@horariosdofunchal.pt
Feed Language:
Portuguese
Feed Start Date:
2025-11-21
Feed End Date:
2026-06-30

Files included


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

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 164
  • Shapes: 261
  • Stops: 1743
  • Trips: 10178

Specification Compliance report

59 notices reported (0 errors, 20 warnings, 39 infos)

Notice Code Severity Total
duplicate_route_name WARNING 1

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
122 "090_P" 123 "090_Q" "90" "" 3 "1"
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.
"stops.txt" "stop_name" "CAM STO A BC ESCL S (693)" 909
"stops.txt" "stop_name" "APS dos CTT S (857B)" 1019
route_color_contrast WARNING 9

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"005_0" 13 "#FBB900" "#FFFFFF"
"005_A" 14 "#FBB900" "#FFFFFF"
"105_0" 137 "#FBB900" "#FFFFFF"
"105_A" 138 "#FBB900" "#FFFFFF"
"105_B" 139 "#FBB900" "#FFFFFF"
"105_C" 140 "#FBB900" "#FFFFFF"
"105_D" 141 "#FBB900" "#FFFFFF"
"105_E" 142 "#FBB900" "#FFFFFF"
"115_0" 148 "#FBB900" "#FFFFFF"
stop_has_too_many_matches_for_shape WARNING 6

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.
5327 "251" "181_J_1_1800_1829_0_UE_034" 300305 "013201" "CAM Seara Velha Baixo (13201)" [32.70780911398873,-16.97348506324708] 34
5327 "251" "181_J_1_1800_1829_0_UE_034" 300306 "013202" "TV Seara Velha Baixo (13202)" [32.7073468355181,-16.972000263707532] 27
5327 "251" "181_J_1_1800_1829_0_UE_034" 300308 "013204" "TV Seara Velha Baixo (13204)" [32.707337,-16.971958999999995] 22
5327 "251" "181_J_1_1800_1829_0_UE_034" 300309 "013205" "CAM Seara Velha Baixo (13205)" [32.707813,-16.973444999999998] 35
5327 "251" "181_J_1_1800_1829_0_UE_034" 300313 "013205" "CAM Seara Velha Baixo (13205)" [32.707813,-16.973444999999998] 35
5327 "251" "181_J_1_1800_1829_0_UE_034" 300314 "013204" "TV Seara Velha Baixo (13204)" [32.707337,-16.971958999999995] 22
stop_without_stop_time WARNING 2

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
1743 "001700" "Garagem HF (1700)"
1744 "001701" "Parque CT1 (1701)"
unknown_column INFO 39

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"calendar_dates.txt" "holiday" 2
"calendar_dates.txt" "period" 3
"calendar_dates.txt" "day_type" 5
"feed_info.txt" "feed_type" 1
"feed_info.txt" "feed_desc" 8
"feed_info.txt" "feed_remarks" 9
"routes.txt" "line_id" 1
"routes.txt" "line_short_name" 2
"routes.txt" "line_long_name" 3
"routes.txt" "route_origin" 6
"routes.txt" "route_destination" 7
"routes.txt" "route_remarks" 11
"routes.txt" "contract" 13
"routes.txt" "path_type" 14
"routes.txt" "circular" 15
"routes.txt" "school" 16
"stops.txt" "stop_id_stepp" 2
"stops.txt" "stop_remarks" 6
"stops.txt" "zone_shift" 9
"stops.txt" "entrance_restriction" 16
"stops.txt" "exit_restriction" 17
"stops.txt" "slot" 18
"stops.txt" "signalling" 19
"stops.txt" "shelter" 20
"stops.txt" "bench" 21
"stops.txt" "network_map" 22
"stops.txt" "schedule" 23
"stops.txt" "real_time_information" 24
"stops.txt" "tariff" 25
"stops.txt" "preservation_state" 26
"stops.txt" "equipment" 27
"stops.txt" "observations" 28
"stops.txt" "region" 29
"stops.txt" "municipality" 30
"stops.txt" "municipality_fare_1" 31
"stops.txt" "municipality_fare_2" 32
"trips.txt" "pattern_id" 2
"trips.txt" "pattern_short_name" 3
"trips.txt" "demand" 12