streamline2 — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule
validator,
version 7.1.0 at 2026-04-24T06:53:10Z,
for the dataset
file:///shared/streamline2_fc883700.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Agencies included
-
B-Line
- website: http://blinetransit.com
- phone number: 530-342-0221
- email: info@bcag.org
Feed Info
- Publisher Name:
- B-Line
- Publisher URL:
- http://blinetransit.com
- Feed Email:
- info@bcag.org
- Feed Language:
- English
- Feed Start Date:
- 2025-08-24
- Feed End Date:
- 2025-12-27
- Service Window:
- 2025-08-24 to 2025-12-27 (?) 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_dates.txt
- feed_info.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 125
- Routes: 21
- Shapes: 52
- Stops: 515
- Trips: 1378
Specification Compliance report
9 notices reported (0 errors, 9 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.
|
|||||||||||||||||
| feed_expiration_date7_days | WARNING | 1 | |||||||||||||||
feed_expiration_date7_daysDataset should be valid for at least the next 7 days. The dataset expiration date defined in You can see more about this notice here.
|
|||||||||||||||||
| 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.
|
|||||||||||||||||
| 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.
|
|||||||||||||||||