GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-24T18:03:26Z,
for the dataset file:///shared/roseview-transit_5a1e2c24.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Rose View Transit
Feed Email:
cbecker@richmondindiana.gov
Feed Language:
English
Feed Start Date:
2026-01-02
Feed End Date:
2027-04-30

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. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 6
  • Shapes: 10
  • Stops: 68
  • Trips: 243

Specification Compliance report

36 notices reported (0 errors, 13 warnings, 23 infos)

Notice Code Severity Total
stop_too_far_from_shape WARNING 6

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
176 "5_1Hosp" "Rt. 5-1St. Hos_T01" 1014 "33" "N 6th St and Service Drive" [39.829122,-84.895162] 117.72070254402703
83 "2" "Rt. 2-1S. Q St.Rt5_T01" 432 "33" "N 6th St and Service Drive" [39.828182169751905,-84.89392305160278] 150.11946375151976
130 "4" "Rt. 4-1S. 8th_T01" 699 "37" "Golden Living Center" [39.80013615891367,-84.88722512004583] 364.6120938223622
130 "4" "Rt. 4-1S. 8th_T01" 701 "20" "Greenwood Apts/Mt. Moriah Church" [39.81269195643388,-84.88088229481366] 263.8637028922285
142 "4" "Rt. 4-040 W._T01" 764 "36" "UHAUL" [39.82361233219261,-84.94123168887167] 193.59938075710073
164 "5" "Rt. 5-0St. Hos_T01" 918 "42" "Westwood Apts." [39.829176000000004,-84.920755] 814.7919738947642
stop_without_stop_time WARNING 6

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.
21 "21" "Bethelhem Manor"
22 "22" "Country Club Apts/Genesis"
24 "24" "Work One"
29 "29" "N 8th St N E St/Depot District"
41 "41" "SW 18th St. & Nat'l Rd W"
63 "63" "Annex Apts."
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
94 "3_OReid" "Rt. 3-0Reid_T01" 501 "62" "Ivy Tech" [39.870375000928874,-84.88087299983049] 500 "61" "IU east & Purdue" [39.869248005895464,-84.8826344213817]
trip_headsign_matches_intermediate_stop INFO 23

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
26 "Rt.1-0EM_T01" "Kroger" "50" 5 "51"
27 "Rt.1-0EM_T02" "Kroger" "50" 5 "51"
28 "Rt.1-0EM_T03" "Kroger" "50" 5 "51"
29 "Rt.1-0EM_T04" "Kroger" "50" 5 "51"
30 "Rt.1-0EM_T05" "Kroger" "50" 5 "51"
31 "Rt.1-0EM_T06" "Kroger" "50" 5 "51"
32 "Rt.1-0EM_T07" "Kroger" "50" 5 "51"
33 "Rt.1-0EM_T08" "Kroger" "50" 5 "51"
34 "Rt.1-0EM_T09" "Kroger" "50" 5 "51"
35 "Rt.1-0EM_T10" "Kroger" "50" 5 "51"
36 "Rt.1-0EM_T11" "Kroger" "50" 5 "51"
48 "Rt.2-0EM_T01" "Kroger" "50" 5 "51"
49 "Rt.2-0EM_T02" "Kroger" "50" 5 "51"
50 "Rt.2-0EM_T03" "Kroger" "50" 5 "51"
51 "Rt.2-0EM_T04" "Kroger" "50" 5 "51"
52 "Rt.2-0EM_T05" "Kroger" "50" 5 "51"
53 "Rt.2-0EM_T06" "Kroger" "50" 5 "51"
54 "Rt.2-0EM_T07" "Kroger" "50" 5 "51"
55 "Rt.2-0EM_T08" "Kroger" "50" 5 "51"
56 "Rt.2-0EM_T09" "Kroger" "50" 5 "51"
57 "Rt.2-0EM_T10" "Kroger" "50" 5 "51"
58 "Rt.2-0EM_T11" "Kroger" "50" 5 "51"
59 "Rt.2-0EM_T12" "Kroger" "50" 5 "51"