svrta-steubenville-oh-us-2 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-23T19:57:59Z,
for the dataset file:///shared/svrta-steubenville-oh-us-2_8f52ac53.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:
SVRTA: Publisher URL:
https://svrta.com: Feed Email:
N/A: Feed Language:
English: 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: 14
Shapes: 65
Stops: 133
Trips: 176

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Shapes Feed Information Fares V1 Route Colors Trips Wheelchair Accessibility Bike Allowed Route-Based Fares Continuous Stops

Specification Compliance report

35 notices reported (0 errors, 35 warnings, 0 infos)

Notice Code Severity Total

expired_calendar WARNING 2

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
2	"1"
3	"2"

missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2

missing_recommended_field WARNING 3

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"feed_info.txt"	2	"feed_start_date"
"feed_info.txt"	2	"feed_end_date"
"feed_info.txt"	2	"feed_version"

route_color_contrast WARNING 11

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeColor (?) The faulty record's HTML route color.	routeTextColor (?) The faulty record's HTML route text color.
"Orange"	4	"#FABF8F"	"#FFFFFF"
"WedWintersville"	5	"#D8E4BC"	"#FFFFFF"
"Green"	6	"#C4D79B"	"#FFFFFF"
"GreenXP"	7	"#C4D79B"	"#FFFFFF"
"MnTripper"	8	"#C4BD97"	"#FFFFFF"
"RaylandTripper"	9	"#C4BD97"	"#FFFFFF"
"PurpleXP"	10	"#CCC0DA"	"#FFFFFF"
"RobinsonW"	11	"#92CDDC"	"#FFFFFF"
"RobinsonSat"	12	"#92CDDC"	"#FFFFFF"
"WintervilleSat"	14	"#C4D79B"	"#FFFFFF"
"FirstFridays"	15	"#F2DCDB"	"#FFFFFF"

route_long_name_contains_short_name WARNING 13

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name	Dataset
"N"/"Judah"	Muni San Fransisco
"6"/"ML King Jr Blvd"	Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent"	STM Montreal
"1"/"Rangiora/Cashmere"	Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.	routeLongName (?) The faulty record's `route_long_name`.
"Blue"	2	"Blue"	"Blue - Fourth Street"
"Red"	3	"Red"	"Red - City Limits"
"Orange"	4	"Orange"	"Orange - Mingo Junction"
"WedWintersville"	5	"Wednesdays in Wintersville"	"Wednesdays in Wintersville"
"Green"	6	"Green"	"Green - Wintersville"
"GreenXP"	7	"Green"	"Green - Express"
"RaylandTripper"	9	"Rayland"	"Rayland - Tripper"
"PurpleXP"	10	"Purple"	"Purple - Express"
"RobinsonW"	11	"Robinson"	"Robinson - Weirton"
"RobinsonSat"	12	"Robinson"	"Robinson - Saturday"
"SteubenvilleSat"	13	"Steubenville - Saturday"	"Steubenville - Saturday"
"WintervilleSat"	14	"Wintersville - Saturday"	"Wintersville - Saturday"
"FirstFridays"	15	"First Fridays"	"First Fridays Shuttle"

route_short_name_too_long WARNING 4

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.
"WedWintersville"	5	"Wednesdays in Wintersville"
"SteubenvilleSat"	13	"Steubenville - Saturday"
"WintervilleSat"	14	"Wintersville - Saturday"
"FirstFridays"	15	"First Fridays"

trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips 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.

currentDate (?) Current date (YYYYMMDD format).	serviceWindowStartDate (?) The start date of the majority service window.	serviceWindowEndDate (?) The end date of the majority service window.
"20260423"	"20250328"	"20251231"