GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T15:17:50Z,
for the dataset file:///shared/indian-river-county_0a460760.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

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

Counts

  • Agencies: 0
  • Blocks: 25
  • Routes: 15
  • Shapes: 15
  • Stops: 479
  • Trips: 344

Specification Compliance report

28 notices reported (9 errors, 19 warnings, 0 infos)

Notice Code Severity Total
invalid_url ERROR 1

invalid_url

A field contains a malformed URL.

Definitions for valid URLs are quite vague. We perform strict validation using the Apache Commons UrlValidator.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"agency.txt" 2 "agency_url" "IndianRiverTransit.transloc.com"
stop_time_with_arrival_before_previous_departure_time ERROR 8

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. prevCsvRowNumber (?) The row of the previous stop time. tripId (?) The trip_id associated to the faulty record. arrivalTime (?) Arrival time at the faulty record. departureTime (?) Departure time at the previous stop time.
12460 12447 "TL-821" "17:15:00" "17:30:00"
49 26 "TL-1061" "20:30:00" "20:33:00"
2685 2675 "TL-536" "06:30:00" "06:33:00"
2714 2704 "TL-537" "07:30:00" "07:33:00"
11200 11178 "TL-779" "17:15:00" "17:30:00"
11600 11582 "TL-793" "17:15:00" "17:30:00"
10390 10374 "TL-751" "17:15:00" "17:30:00"
10740 10723 "TL-765" "17:15:00" "17:30:00"
fast_travel_between_far_stops WARNING 8

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
253 "TL-779" "TL-20" 705.2364021347713 11.753940035579522 11178 230 "TL-17" "Main Transit Hub" "17:30:00" 11200 460 "TL-131" "Oslo Rd & TCCH Clinic (WB)" "17:15:00"
293 "TL-835" "TL-24" 1770.9927714981432 29.51654619163572 12812 1 "TL-29" "Indian River Mall" "17:00:00" 12850 330 "TL-506" "58 Ave & College Ln (OB)" "17:00:00"
283 "TL-821" "TL-23" 697.8319549882672 11.630532583137786 12447 350 "TL-150" "North County HUB" "17:30:00" 12460 480 "TL-318" "SR 512 & Dollar General" "17:15:00"
273 "TL-807" "TL-22" 2373.835348721392 39.563922478689875 11934 1 "TL-29" "Indian River Mall" "17:00:00" 11970 360 "TL-272" "26th St & Woodfield Blvd (WB)" "17:00:00"
303 "TL-849" "TL-25" 1468.8700942195073 24.481168236991792 13211 1 "TL-532" "Gifford Health Center" "17:00:00" 13250 410 "TL-452" "49th St & 28th Ave (SB)" "17:00:00"
263 "TL-793" "TL-21" 717.0647530632066 11.95107921772011 11582 190 "TL-150" "North County HUB" "17:30:00" 11600 360 "TL-156" "Roseland & US 1" "17:15:00"
103 "TL-619" "TL-22" 182.6027191324148 39.563922478689875 5645 1 "TL-29" "Indian River Mall" "19:03:00" 5681 360 "TL-272" "26th St & Woodfield Blvd (WB)" "19:15:00"
153 "TL-1061" "TL-6" 790.1193084441854 13.168655140736425 26 240 "TL-17" "Main Transit Hub" "20:33:00" 49 460 "TL-464" "The Preserve at Oslo (NB)" "20:30:00"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 7

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.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "PARC 24 (SB)" 208
"stops.txt" "stop_name" "PARC 24 (NB)" 217
"stops.txt" "stop_name" "US 1 & MAIN ST (SB)" 330
"stops.txt" "stop_name" "CR 510 & VLE (NB)" 363
"stops.txt" "stop_name" "CR 510 & VLE (SB)" 366
"stops.txt" "stop_name" "82nd (B) & SR 60" 474
"stops.txt" "stop_name" "US 1 and TCCH (specialty stop)" 478
stop_too_far_from_shape WARNING 3

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.
2 "TL-12" "TL-356" 521 "TL-467" "Auto Zone (Request Only)" [27.767199999999995,-80.51115] 127.53446390160782
74 "TL-21" "TL-1256" 57 "TL-137" "Grace's Landing (By Request Only)" [27.8171668831091,-80.47152495473291] 202.81016379199554
16 "TL-16" "TL-360" 548 "TL-532" "Gifford Health Center" [27.682170000000003,-80.41447] 439.2357625636024