huntsville-shuttle — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T22:11:33Z,
for the dataset file:///shared/huntsville-shuttle_9fe51e05.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Agencies included
- AL_Huntsville
- website: https://www.huntsvilleal.gov/residents/streets/public-transportation/huntsvilletransit/
- phone number:
- email: Not provided
Feed Info
- Publisher Name:
- N/A
- Publisher URL:
- N/A
- Feed Email:
- N/A
- Feed Language:
- N/A
- Service Window:
- 2019-12-13 to 2022-12-31 (?) 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
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 0
- Routes: 11
- Shapes: 11
- Stops: 360
- Trips: 912
Specification Compliance report
37 notices reported (0 errors, 37 warnings, 0 infos)
| Notice Code | Severity | Total | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| expired_calendar | WARNING | 6 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
expired_calendarDataset should not contain date ranges for services that have already expired. This warning takes into account the You can see more about this notice here.
leading_or_trailing_whitespaces | WARNING | 29 | leading_or_trailing_whitespacesThe value in CSV file has leading or trailing whitespaces. This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser. The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces. You can see more about this notice here.
missing_recommended_file | WARNING | 1 | missing_recommended_fileA recommended file is missing. You can see more about this notice here.
trip_coverage_not_active_for_next7_days | WARNING | 1 | trip_coverage_not_active_for_next7_daysTrips data should be valid for at least the next seven days. This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days. You can see more about this notice here.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||