huntsville-shuttle2 — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T13:13:11Z,
for the dataset file:///shared/huntsville-shuttle2_910cf0e2.zip. No country code was provided.
Use this report alongside our documentation.
A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.
Summary
Agencies included
- AL_Huntsville
- website: https://www.huntsvilleal.gov/residents/streets/public-transportation/shuttle-bus/
- 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:
- 2026-03-11 to 2026-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: 12
- Shapes: 13
- Stops: 383
- Trips: 1221
Specification Compliance report
22 notices reported (0 errors, 22 warnings, 0 infos)
| Notice Code | Severity | Total | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| leading_or_trailing_whitespaces | WARNING | 21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||