GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T23:28:46Z,
for the dataset file:///shared/lee-county-transit-1.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
LeeTran
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-01-15
Feed End Date:
2026-04-22

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: 153
  • Routes: 25
  • Shapes: 91
  • Stops: 1585
  • Trips: 3304

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 1

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"shp-100-52" 5451 17780.34 1309 5450 17780.34 1308
fast_travel_between_consecutive_stops WARNING 2

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

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.
644 "1700010" "600" 240.22132719722183 1.2678347824297818 84476 23 "3318" "US 41 @ BONITA BCH RD SE" "15:28:00" 84477 24 "3409" "S TAMIAMI TRL @ WOODS EDGE PKWY" "15:28:19"
644 "1700010" "600" 231.03562963743744 2.6312391153152594 84477 24 "3409" "S TAMIAMI TRL @ WOODS EDGE PKWY" "15:28:19" 84478 25 "3411" "US 41 @ WIGGINS PASS RD" "15:29:00"
leading_or_trailing_whitespaces WARNING 3

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

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.
"trips.txt" 510 "trip_headsign" " N Cleveland Ave @ Pine Island NB"
"trips.txt" 1546 "trip_headsign" " N Cleveland Ave @ Pine Island NB"
"trips.txt" 2700 "trip_headsign" " N Cleveland Ave @ Pine Island NB"
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 3

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"
"fare_attributes.txt" 4 "agency_id"
mixed_case_recommended_field WARNING 1595

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 1595 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.
"stops.txt" "stop_name" "EDISON MALL TRANSFER CTR" 2
"stops.txt" "stop_name" "EDISON MALL DR @ SOLOMON BLVD" 3
"stops.txt" "stop_name" "WNKLR AVE @ BROADWAY AVE" 4
"stops.txt" "stop_name" "WNKLR AVE @ CENTRAL AVE" 5
"stops.txt" "stop_name" "WNKLR AVE@ EVANS AVE-EB" 6
"stops.txt" "stop_name" "WNKLR AVE @ THE PALM APTS" 7
"stops.txt" "stop_name" "WNKLR AVE @ CENTER POINTE DR" 8
"stops.txt" "stop_name" "WNKLR AVE @ METRO PKWY" 9
"stops.txt" "stop_name" "WNKLR AVE @ METRO PKWY-EB1" 10
"stops.txt" "stop_name" "FORD ST EXT @ WNKLR AVE EXT" 11
"stops.txt" "stop_name" "FORD ST EXT @ KERNEL CIR" 12
"stops.txt" "stop_name" "WNKLR AVE @ SCHOOLHOUSE RD-EB1" 13
"stops.txt" "stop_name" "WNKLR AVE @ SHOEMAKER BLVD" 14
"stops.txt" "stop_name" "WNKLR AVE @ PROVINC PK BLVD" 16
"stops.txt" "stop_name" "COLONIAL BLVD @ WNKLR AVE" 17
"stops.txt" "stop_name" "WNKLR AVE @ SCHOOLHOUSE RD-EB2" 18
"stops.txt" "stop_name" "WNKLR AVE @ METRO PKWY-WB" 19
"stops.txt" "stop_name" "WNKLR AVE @ CENTER POINTE DR 1" 20
"stops.txt" "stop_name" "WNKLR AVE @ CENTER POINTE DR 2" 21
"stops.txt" "stop_name" "WNKLR AVE@ EVANS AVE-WB" 22
"stops.txt" "stop_name" "EVANS AVE @ WNKLR AVE 1" 23
"stops.txt" "stop_name" "EVANS AVE @ WNKLR AVE 2" 24
"stops.txt" "stop_name" "EVANS AVE@ PARK WINDSOR DR 1-NB" 25
"stops.txt" "stop_name" "EVANS AVE@ PARK WINDSOR DR 2-NB" 26
"stops.txt" "stop_name" "EVANS AVE @ CARRELL RD" 27
"stops.txt" "stop_name" "FOWLER ST @ CARRELL RD" 28
"stops.txt" "stop_name" "FOWLER ST@ HUNTER ST-NB" 29
"stops.txt" "stop_name" "FOWLER ST@ MORENO AVE-NB" 30
"stops.txt" "stop_name" "FOWLER ST@ HANSON ST-NB" 31
"stops.txt" "stop_name" "FOWLER ST@ MAPLE AVE-NB" 32
"stops.txt" "stop_name" "FOWLER ST @ CANAL ST" 33
"stops.txt" "stop_name" "FOWLER ST@ STELLA ST-NB" 34
"stops.txt" "stop_name" "FOWLER ST@ FRANKLIN ST-NB" 35
"stops.txt" "stop_name" "EDISON AVE @ ROYAL PALM AVE" 36
"stops.txt" "stop_name" "EDISON AVE @ JACKSON ST 1" 37
"stops.txt" "stop_name" "JACKSON ST @ CRAWFORD ST" 38
"stops.txt" "stop_name" "ROSA PARKS TRANSPORTATION CTR" 39
"stops.txt" "stop_name" "MLK BLVD @ EVANS AVE-EB" 40
"stops.txt" "stop_name" "MLK BLVD @ CRANFORD AVE-EB" 41
"stops.txt" "stop_name" "MLK BLVD @ PALM AVE-EB1" 42
"stops.txt" "stop_name" "SOLOMON BLVD @ WNKLR AVE" 43
"stops.txt" "stop_name" "S TAMIAMI TRL @ COMMONS WAY" 44
"stops.txt" "stop_name" "S TAMIAMI TRL @ COUNTY RD" 45
"stops.txt" "stop_name" "S TAMIAMI TRL @ LORDS WAY ST" 46
"stops.txt" "stop_name" "STARS COMPLEX-EB" 47
"stops.txt" "stop_name" "EDISON AVE@ WRIGHT ST-EB" 48
"stops.txt" "stop_name" "EDISON AVE@ FORD ST-EB" 49
"stops.txt" "stop_name" "EDISON AVE@ HENDERSON AVE-EB" 50
"stops.txt" "stop_name" "S TAMIAMI TRL @ JACK RABBIT RUN" 51
"stops.txt" "stop_name" "S TAMIAMI TRL @ HICKORY DR" 52
route_color_contrast WARNING 3

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.
"15" 8 "#FFA87A" "#FFFFFF"
"515" 20 "#9CD9C2" "#FFFFFF"
"590" 21 "#A3D963" "#FFFFFF"