municipality-aguada — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-28T18:40:23Z,
for the dataset file:///shared/municipality-aguada_2e226b3f.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Agencies included
- Municipality of Aguada
- website: https://aguada.gov.pr/
- phone number: 787-868-6400
- email: dfeliciano@aguada.gov.pr
Feed Info
- Publisher Name:
- Municipality of Vega Baja
- Feed Email:
- dfeliciano@aguada.gov.pr
- Feed Language:
- English
- Feed Start Date:
- 2025-11-01
- Feed End Date:
- 2026-10-31
- Service Window:
- 2025-11-03 to 2026-10-30 (?) 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
- fare_attributes.txt
- fare_rules.txt
- feed_info.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- transfers.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 0
- Routes: 1
- Shapes: 0
- Stops: 9
- Trips: 8
Specification Compliance report
4 notices reported (0 errors, 4 warnings, 0 infos)
| Notice Code | Severity | Total | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| missing_timepoint_value | WARNING | 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
missing_timepoint_value
When at least one of You can see more about this notice here.
mixed_case_recommended_field | WARNING | 1 | mixed_case_recommended_fieldThis 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.
You can see more about this notice here.
route_long_name_contains_short_name | WARNING | 1 | route_long_name_contains_short_nameLong name should not contain short name for a single route. In routes.txt, Good examples:
Bad examples:
You can see more about this notice here.
same_name_and_description_for_route | WARNING | 1 | same_name_and_description_for_routeSame name and description for route. The GTFS spec defines Description of a route that provides useful, quality information. Do not simply duplicate the name of the route. See the GTFS and GTFS Best Practices links below for more examples of how to populate the
You can see more about this notice here.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||