treasure-valley — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-15T00:55:52Z,
for the dataset file:///shared/treasure-valley_14484b6b.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Agencies included
- Treasure Valley Transit
- website: https://www.treasurevalleytransit.com/
- phone number: 1-208-463-9111
- email: Not provided
Feed Info
- Publisher Name:
- Treasure Valley Transit
- Publisher URL:
- https://www.treasurevalleytransit.com/
- Feed Email:
- N/A
- Feed Language:
- English
- Feed Start Date:
- 2026-07-17
- Feed End Date:
- 2027-09-07
- Service Window:
- 2026-07-17 to 2027-09-07 (?) 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
- feed_info.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 50
- Routes: 7
- Shapes: 12
- Stops: 89
- Trips: 570
Specification Compliance report
7 notices reported (0 errors, 6 warnings, 1 infos)
| Notice Code | Severity | Total | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| leading_or_trailing_whitespaces | WARNING | 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
same_name_and_description_for_route | WARNING | 4 | 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.
same_name_and_description_for_stop | WARNING | 1 | same_name_and_description_for_stopSame name and description for stop. The GTFS spec defines Description of the location that provides useful, quality information. Do not simply duplicate the name of the location. You can see more about this notice here.
big_gap_in_service | INFO | 1 | big_gap_in_serviceA service has a gap of more than 13 days between active service dates. You can see more about this notice here.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||