Search
  1. Home
  2. United States Feeds
  3. visalia-transit
  4. Enhanced Validation Report

visalia-transit — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-01T09:29:49Z,
for the dataset file:///shared/visalia-transit_a2f3f1c3.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Language:
English
Feed Start Date:
2024-01-02
Feed End Date:
2026-12-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. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 35
  • Shapes: 25
  • Stops: 511
  • Trips: 1337

Specification Compliance report

11 notices reported (0 errors, 5 warnings, 6 infos)

Notice Code Severity Total
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"
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.
874 "2343-R9B" "2343-R9B_T01" 24786 "2343-2307715" "Palm & B Street (E)" [36.29866439438319,-119.13602270006974] 181.61460484950643
759 "2343-R8A" "2343-R8A_T01" 21826 "2343-5664514" "Court / Riggin" [36.35644608526441,-119.29366189129418] 188.98495803368252
800 "2343-R8B" "2343-R8B_T01" 22830 "2343-3861532" "Riggin & Dinuba (Eb)" [36.357122,-119.296877] 122.14667919003273
trip_headsign_matches_intermediate_stop INFO 6

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.
2 "2343-V-LINE_T01" "Transit Center" "2343-9900" 0 "2343-9905"
3 "2343-V-LINE_T02" "Transit Center" "2343-9900" 0 "2343-9905"
4 "2343-V-LINE_T03" "Transit Center" "2343-9900" 0 "2343-9905"
5 "2343-V-LINE_T04" "Transit Center" "2343-9900" 0 "2343-9905"
6 "2343-V-LINE_T05" "Transit Center" "2343-9900" 0 "2343-9905"
7 "2343-V-LINE_T06" "Transit Center" "2343-9900" 0 "2343-9905"