city-of-commerce — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-28T01:08:01Z,
for the dataset file:///shared/city-of-commerce_f277023b.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Agencies included
- City Of Commerce Transit
- website: https://www.ci.commerce.ca.us/city-hall/transportation
- phone number: (323) 887-4419
- email: Not provided
Feed Info
- Publisher Name:
- GMV Syncromatics
- Publisher URL:
- https://gmvsyncromatics.com
- Feed Email:
- support@gmvsync.com
- Feed Language:
- English
- Feed Start Date:
- 2025-12-31
- Feed End Date:
- 2030-12-31
- Service Window:
- 2026-01-02 to 2030-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_attributes.txt
- calendar_dates.txt
- directions.txt
- feed_info.txt
- realtime_routes.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 11
- Routes: 7
- Shapes: 7
- Stops: 225
- Trips: 120
Specification Compliance report
11 notices reported (0 errors, 8 warnings, 3 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.
route_long_name_contains_short_name | WARNING | 7 | 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.
unknown_file | INFO | 3 | unknown_fileA file is unknown. You can see more about this notice here.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||