GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T14:40:17Z,
for the dataset file:///shared/laketran.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Laketran
Publisher URL:
https://laketran.com/
Feed Email:
laketran@laketran.com
Feed Language:
English
Feed Start Date:
2026-01-26
Feed End Date:
2026-05-24

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. trips.txt

Counts

  • Agencies: 1
  • Blocks: 43
  • Routes: 14
  • Shapes: 46
  • Stops: 808
  • Trips: 603

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 1

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

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 small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`. actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"70557b59-0d44-417c-9aac-8ba24c73e516" 12946 79104.84 490 15554 79104.84 489 0.0570480106044849
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`.
"e83ab9b5-c6b5-4145-9bbc-e42dff5450a1" 1697 57644.72 337 4608 57644.72 336
leading_or_trailing_whitespaces WARNING 1

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.
"stops.txt" 202 "stop_name" "EUCLID AVE, & 93RD. ST. "
mixed_case_recommended_field WARNING 806

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 806 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" "GREAT LAKES MALL" 2
"stops.txt" "stop_name" "SR-84 JOHNNYCAKE RIDGE RD. & DEEPWOOD APTS" 3
"stops.txt" "stop_name" "PLAZA BLVD. & CHASE BANK - GREAT LAKES MALL" 4
"stops.txt" "stop_name" "PLAZA BLVD. & PLANET FITNESS" 5
"stops.txt" "stop_name" "PLAZA BLVD. & OLIVE GARDEN - GREAT LAKES MALL" 6
"stops.txt" "stop_name" "SR-20 MENTOR AVE. & MENTOR CITY CENTER" 7
"stops.txt" "stop_name" "SR-20 MENTOR AVE. & BRENTWOOD RD." 8
"stops.txt" "stop_name" "SR-20 MENTOR AVE. & STOCKBRIDGE RD." 9
"stops.txt" "stop_name" "SR-20 MENTOR AVE.- POINTS EAST" 10
"stops.txt" "stop_name" "SR-20 MENTOR AVE. & QUEENSDALE APTS." 11
"stops.txt" "stop_name" "SR-20 MENTOR AVE. & BRODIE BLVD. (WB)" 12
"stops.txt" "stop_name" "SR-20 MENTOR AVE. & BUMPERS BAR" 13
"stops.txt" "stop_name" "SR-20 MENTOR AVE. & PELTON RD." 14
"stops.txt" "stop_name" "SR-20 MENTOR AVE & KIRTLAND RD. (NW CORNER)" 15
"stops.txt" "stop_name" "SR-20 MENTOR AVE. -RESIDENCES AT CHAGRIN RIVERWALK" 16
"stops.txt" "stop_name" "VINE ST. & ERIE ST." 17
"stops.txt" "stop_name" "VINE ST. & CHURCH ST." 18
"stops.txt" "stop_name" "VINE ST. & PATT CT." 19
"stops.txt" "stop_name" "VINE ST. & LAKELAND BLVD." 20
"stops.txt" "stop_name" "VINE ST. & E. 364 ST." 21
"stops.txt" "stop_name" "VINE ST. & E. 359 ST." 22
"stops.txt" "stop_name" "VINE ST. & E. 355 ST." 23
"stops.txt" "stop_name" "EASTLAKE TRANSIT CENTER" 24
"stops.txt" "stop_name" "VINE ST. & E. 348 ST." 25
"stops.txt" "stop_name" "VINE ST. & E. 343 ST." 26
"stops.txt" "stop_name" "VINE ST. & E. 340 ST." 27
"stops.txt" "stop_name" "VINE ST. & E. 337 ST." 28
"stops.txt" "stop_name" "VINE ST. & WAVERLY RD." 29
"stops.txt" "stop_name" "VINE ST. & E. 300 ST. (WB)" 30
"stops.txt" "stop_name" "WILLOWICK DR. & VINE ST." 31
"stops.txt" "stop_name" "32417 VINE ST." 32
"stops.txt" "stop_name" "VINE ST. & E. 322 ST." 33
"stops.txt" "stop_name" "VINE ST. & E. 320 ST." 34
"stops.txt" "stop_name" "VINE ST. & E. 317 ST." 35
"stops.txt" "stop_name" "VINE ST. & E. 312 ST." 36
"stops.txt" "stop_name" "SR-283 LAKESHORE BLVD. & SHOREGATE TOWER APTS." 37
"stops.txt" "stop_name" "SR-283 LAKESHORE BLVD. & LAKE METROPARKS" 38
"stops.txt" "stop_name" "SR-283 LAKESHORE BLVD. & E. 305 ST" 39
"stops.txt" "stop_name" "LAKESHORE BLVD. - GIANT EAGLE" 40
"stops.txt" "stop_name" "SR-283 LAKESHORE BLVD. - SHOREGATE SHOPPING CENTER" 41
"stops.txt" "stop_name" "LAKESHORE BLVD. & E 294 ST." 42
"stops.txt" "stop_name" "SR-283 LAKESHORE BLVD. & E. 291 ST." 43
"stops.txt" "stop_name" "E 288 ST. & WOODMERE DR." 44
"stops.txt" "stop_name" "E 288 ST. & ACACIA DR." 45
"stops.txt" "stop_name" "E. 288 ST. & FOREST RD." 46
"stops.txt" "stop_name" "WORDEN RD. & FRANKLIN AVE." 47
"stops.txt" "stop_name" "WORDEN RD. & HALIFAX ST." 48
"stops.txt" "stop_name" "WORDEN RD. & ROBERT ST." 49
"stops.txt" "stop_name" "WORDEN RD. & LAKELAND BLVD." 50
"stops.txt" "stop_name" "SR-20 EUCLID AVE. & E. 300 ST." 51
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260123" "20260126" "20260522"