svrta-steubenville-oh-us-2 — Enhanced Validation Report
This report was generated by the Canonical GTFS Schedule
validator,
version 7.1.0 at 2026-04-23T19:57:58Z,
for the dataset
file:///shared/svrta-steubenville-oh-us-2_32659989.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Agencies included
-
Steel Valley Regional Transit Authority
- website: https://svrta.com
- phone number: (740) 282-6145
- email: tturner@svrta.com
Feed Info
- Publisher Name:
- Busmaps.com
- Publisher URL:
- https://busmaps.com
- Feed Language:
- English
- Feed Start Date:
- 2025-01-20
- Feed End Date:
- 2025-12-31
- Service Window:
- 2025-03-28 to 2025-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
- fare_attributes.txt
- fare_rules.txt
- feed_info.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 0
- Routes: 13
- Shapes: 57
- Stops: 132
- Trips: 175
Specification Compliance report
13 notices reported (0 errors, 13 warnings, 0 infos)
| Notice Code | Severity | Total | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| expired_calendar | WARNING | 2 | |||||||||||||||||||||||||||||||||||||||
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.
|
|||||||||||||||||||||||||||||||||||||||||
| 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.
|
|||||||||||||||||||||||||||||||||||||||||
| route_short_name_too_long | WARNING | 4 | |||||||||||||||||||||||||||||||||||||||
route_short_name_too_longShort name of a route is too long (more than 12 characters). 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.
|
|||||||||||||||||||||||||||||||||||||||||