GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T22:09:24Z,
for the dataset file:///shared/manatee.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 Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2025-11-22
Feed End Date:
2025-12-19

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: 29
  • Routes: 17
  • Shapes: 60
  • Stops: 927
  • Trips: 656

Specification Compliance report

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

Notice Code Severity Total
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20251205" "20251219" "20260104"
mixed_case_recommended_field WARNING 432

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 432 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" "SR 70 / 53rd AVE E" 10
"stops.txt" "stop_name" "29th ST E/60th AVE E" 3
"stops.txt" "stop_name" "60th AVE E/32nd ST E" 4
"stops.txt" "stop_name" "60th AVE E/35th LN E" 5
"stops.txt" "stop_name" "US 301/60th AVE E" 12
"stops.txt" "stop_name" "60th AVE E/20th CT E" 13
"stops.txt" "stop_name" "US 301/51st AVE E" 14
"stops.txt" "stop_name" "US 301/45th AVE E" 15
"stops.txt" "stop_name" "US 301/36th AVE E" 18
"stops.txt" "stop_name" "US 301/24th AVE E" 20
"stops.txt" "stop_name" "US 301/19th AVE E" 21
"stops.txt" "stop_name" "10th ST W/2ND AVE W" 27
"stops.txt" "stop_name" "10th ST W/4TH AVE W" 28
"stops.txt" "stop_name" "10th ST W/5TH AVE DR W" 29
"stops.txt" "stop_name" "10th ST W/13th AVE W" 31
"stops.txt" "stop_name" "10th ST W/14th AVE W" 32
"stops.txt" "stop_name" "14th AVE W/12th ST W" 33
"stops.txt" "stop_name" "14th AVE W/14th ST W" 34
"stops.txt" "stop_name" "14th AVE W/17th ST W" 35
"stops.txt" "stop_name" "8TH AVE W/7TH ST W" 36
"stops.txt" "stop_name" "7TH ST W/7TH AVE W" 37
"stops.txt" "stop_name" "17th ST W / 9TH AVE W" 38
"stops.txt" "stop_name" "17th ST E/1ST AVE E" 42
"stops.txt" "stop_name" "17th ST E/3RD AVE E" 43
"stops.txt" "stop_name" "17th ST W/3RD AVE W" 44
"stops.txt" "stop_name" "17th ST W/5TH AVE W" 45
"stops.txt" "stop_name" "US 301 N/25th AVE DR E" 52
"stops.txt" "stop_name" "US 301 N/40th AVE E" 55
"stops.txt" "stop_name" "US 301 N/44th AVE E" 56
"stops.txt" "stop_name" "US 301 N/18th ST E" 57
"stops.txt" "stop_name" "60th AVE E/US 301 N" 58
"stops.txt" "stop_name" "10th ST W/5TH AVE W" 59
"stops.txt" "stop_name" "17th ST W/6TH AVE W" 60
"stops.txt" "stop_name" "18th ST E/44th AVE E" 61
"stops.txt" "stop_name" "18th ST E/46th AVE E" 62
"stops.txt" "stop_name" "47th TER E/18th ST E" 63
"stops.txt" "stop_name" "19th ST CT E/47th TER E" 64
"stops.txt" "stop_name" "19th ST CT E/39th AVE E" 66
"stops.txt" "stop_name" "38th AVE E/18th ST E" 67
"stops.txt" "stop_name" "15th ST E/33rd AVE DR E" 68
"stops.txt" "stop_name" "15th ST E/31st AVE E" 69
"stops.txt" "stop_name" "15th ST E/32nd AVE E" 70
"stops.txt" "stop_name" "15th ST E/34th AVE E" 71
"stops.txt" "stop_name" "26th AVE E/19th ST E" 72
"stops.txt" "stop_name" "26th AVE E/18th ST E" 73
"stops.txt" "stop_name" "26th AVE E/16th ST CT E" 74
"stops.txt" "stop_name" "26th AVE E/15th ST E" 75
"stops.txt" "stop_name" "26th AVE E/9TH ST E" 77
"stops.txt" "stop_name" "26th AVE E/5TH ST E" 78
"stops.txt" "stop_name" "26th AVE E/3RD ST E" 79
route_long_name_contains_short_name WARNING 3

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`.
"101956-4" 5 "4" "4 9TH AVE East & West"
"101956-9" 9 "9" "9 26th ST West"
"101956-16" 12 "16" "16 15th Street E/Tallevast"
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.
657 "101956-7651_shp" "101956-t802-b3DF-sl2" 23207 "101956-2640" "SRQ BUS Loop BAY B" [27.38671,-82.55608] 147.67013603479026
621 "101956-7756_shp" "101956-t267-b3DF-sl2" 20252 "101956-2640" "SRQ BUS Loop BAY B" [27.38672402911731,-82.55638321806532] 143.33412200378044
619 "101956-7759_shp" "101956-t219-b3E0-sl2" 20090 "101956-2640" "SRQ BUS Loop BAY B" [27.38672402911731,-82.55638321806532] 143.33412200378044
stops_match_shape_out_of_order WARNING 2

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.
310 "101956-7665_shp" "101956-t2DA-bCE5-sl2" 8530 "101956-3334" "Bridge Street Water Taxi" [27.466821723700495,-82.69379012479517] 8529 "101956-3333" "Gulf Islands Ferry Riverwalk Stop" [27.49967,-82.57005]
311 "101956-7666_shp" "101956-t384-bCE5-sl2" 8532 "101956-3333" "Gulf Islands Ferry Riverwalk Stop" [27.49968,-82.57005] 8531 "101956-3334" "Bridge Street Water Taxi" [27.466821764752645,-82.69379012888409]