c-tran — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-29T14:08:18Z,
for the dataset file:///shared/c-tran_e203725d.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
- C-TRAN
- website: http://www.C-TRAN.com
- phone number: 360-695-0123
- email: Not provided
Feed Info
- Publisher Name:
- C-TRAN
- Publisher URL:
- https://www.c-tran.com/
- Feed Email:
- gtfs@c-tran.org
- Feed Language:
- English
- Feed Start Date:
- 2026-05-10
- Feed End Date:
- 2026-09-12
- Service Window:
- 2026-05-10 to 2026-09-12 (?) 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_leg_rules.txt
- fare_media.txt
- fare_products.txt
- fare_transfer_rules.txt
- feed_info.txt
- rider_categories.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- timeframes.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 473
- Routes: 35
- Shapes: 132
- Stops: 915
- Trips: 10066
Specification Compliance report
21 notices reported (0 errors, 21 warnings, 0 infos)
| Notice Code | Severity | Total | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| route_long_name_contains_short_name | WARNING | 5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
stop_too_far_from_shape | WARNING | 16 | stop_too_far_from_shapeStop too far from trip shape. Per GTFS Best Practices, route alignments (in You can see more about this notice here.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||