southwest-ohio-regional-transit-authority — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-27T21:57:49Z,
for the dataset file:///shared/southwest-ohio-regional-transit-authority_eb53623d.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Greater Dayton RTA
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-03-01
Feed End Date:
2026-05-23

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 148
  • Routes: 23
  • Shapes: 190
  • Stops: 2731
  • Trips: 4376

Specification Compliance report

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

Notice Code Severity Total
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 2

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.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
mixed_case_recommended_field WARNING 2866

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

Only the first 50 of 2866 affected records are displayed below.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"routes.txt" "route_long_name" "NORTH CONNECTOR" 20
"routes.txt" "route_long_name" "WEST CONNECTOR" 21
"routes.txt" "route_long_name" "TEST ROUTES" 22
"stops.txt" "stop_name" "3RD @ PERRY" 2
"stops.txt" "stop_name" "3RD @ MARYS" 3
"stops.txt" "stop_name" "3RD @ GRIMES" 4
"stops.txt" "stop_name" "3RD @ SWEETMAN" 5
"stops.txt" "stop_name" "3RD @ WILLIAMS" 6
"stops.txt" "stop_name" "3RD @ BROADWAY" 7
"stops.txt" "stop_name" "3RD @ PAUL LAWRENCE DUNBAR" 8
"stops.txt" "stop_name" "3RD @ EUCLID" 9
"stops.txt" "stop_name" "3RD @ JAMES H MCGEE" 10
"stops.txt" "stop_name" "W 3RD ST @ CLEMMER ST" 11
"stops.txt" "stop_name" "W 3RD ST @ ORCHARD AV" 12
"stops.txt" "stop_name" "3RD @ ANNA" 13
"stops.txt" "stop_name" "3RD @ BROOKLYN" 14
"stops.txt" "stop_name" "3RD @ HALLOWAY" 15
"stops.txt" "stop_name" "3RD @ DECKER" 16
"stops.txt" "stop_name" "3RD @ GETTYSBURG" 17
"stops.txt" "stop_name" "3RD @ 4200 3RD" 18
"stops.txt" "stop_name" "3RD @ ELMHURST" 19
"stops.txt" "stop_name" "3RD @ ALMOND" 20
"stops.txt" "stop_name" "3RD @ MIA" 21
"stops.txt" "stop_name" "3RD @ CROWN" 22
"stops.txt" "stop_name" "3RD @ VICTORY" 23
"stops.txt" "stop_name" "3RD @ CHAIN" 24
"stops.txt" "stop_name" "3RD @ ELKINS" 25
"stops.txt" "stop_name" "3RD @ HANNA" 26
"stops.txt" "stop_name" "3RD @ MILLER" 27
"stops.txt" "stop_name" "3RD @ LANSDOWNE" 28
"stops.txt" "stop_name" "3RD @ IONA" 29
"stops.txt" "stop_name" "3RD @ NORTHAMPTON" 30
"stops.txt" "stop_name" "3RD @ U.S. 35" 31
"stops.txt" "stop_name" "3RD @ TAFT" 32
"stops.txt" "stop_name" "3RD @ DAVENPORT" 33
"stops.txt" "stop_name" "3RD @ POMEROY" 34
"stops.txt" "stop_name" "3RD @ HOLLAND" 35
"stops.txt" "stop_name" "3RD @ CHAIN" 36
"stops.txt" "stop_name" "3RD @ LISCUM" 37
"stops.txt" "stop_name" "3RD @ MIA" 38
"stops.txt" "stop_name" "3RD @ ALMOND" 39
"stops.txt" "stop_name" "3RD @ 4200 3RD" 40
"stops.txt" "stop_name" "3RD @ GETTYSBURG" 41
"stops.txt" "stop_name" "3RD @ DECKER" 42
"stops.txt" "stop_name" "3RD @ HALLOWAY" 43
"stops.txt" "stop_name" "3RD @ UPPER" 44
"stops.txt" "stop_name" "3RD @ ABBEY" 45
"stops.txt" "stop_name" "3RD @ INLAND" 46
"stops.txt" "stop_name" "W 3RD ST @ BISH AV" 47
"stops.txt" "stop_name" "3RD @ ORCHARD" 48
route_color_contrast WARNING 1

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.
"06" 6 "#8000FF" "#000000"
route_long_name_contains_short_name WARNING 1

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`.
"FLYER" 23 "FLYER" "FLYER"
stop_without_stop_time WARNING 12

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
2499 "3409" "STOP 1"
2500 "3410" "STOP 2"
2501 "3411" "STOP 3"
2502 "3412" "STOP 4"
2503 "3413" "STOP 5"
2504 "3414" "STOP 10"
2505 "3415" "STOP 6"
2506 "3416" "STOP 7"
2507 "3417" "STOP 8"
2508 "3418" "STOP 9"
2515 "3559" "STOP 5A"
2516 "3560" "STOP 4A"
unused_shape WARNING 50

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"shp-999-01" 201644
"shp-999-02" 201762
"shp-999-03" 202002
"shp-999-04" 202113
"shp-999-05" 202163
"shp-999-06" 202213
"shp-999-07" 202263
"shp-999-08" 202313
"shp-999-09" 202363
"shp-999-10" 202413
"shp-999-11" 202463
"shp-999-12" 202513
"shp-999-13" 202563
"shp-999-14" 202613
"shp-999-15" 202663
"shp-999-16" 202713
"shp-999-17" 202763
"shp-999-18" 202813
"shp-999-19" 202863
"shp-999-20" 202913
"shp-999-21" 202963
"shp-999-22" 203013
"shp-999-23" 203063
"shp-999-24" 203113
"shp-999-25" 203163
"shp-999-26" 203213
"shp-999-27" 203263
"shp-999-28" 203313
"shp-999-29" 203363
"shp-999-30" 203413
"shp-999-31" 203463
"shp-999-32" 203513
"shp-999-33" 203563
"shp-999-34" 203613
"shp-999-35" 203663
"shp-999-36" 203713
"shp-999-37" 203763
"shp-999-38" 203813
"shp-999-39" 203863
"shp-999-40" 203913
"shp-999-41" 203963
"shp-999-42" 204013
"shp-999-43" 204063
"shp-999-44" 204113
"shp-999-45" 204163
"shp-999-46" 204213
"shp-999-47" 204263
"shp-999-48" 204313
"shp-999-49" 204363
"shp-999-50" 204413