lakexpress — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-16T05:49:11Z,
for the dataset file:///shared/lakexpress_5f25eca6.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included


Feed Info


Publisher Name:
LakeXpress
Feed Email:
info@ridelakexpress.com
Feed Language:
English
Feed Start Date:
2025-12-19
Feed End Date:
2026-09-30

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: 17
  • Routes: 9
  • Shapes: 21
  • Stops: 507
  • Trips: 193

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 5

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`.
"9f01e88a-8b61-42af-961a-b3f788db4b71" 3937 16144.98 107 1256 16144.98 106
"9f01e88a-8b61-42af-961a-b3f788db4b71" 5376 26571.44 175 3262 26571.44 174
"9f01e88a-8b61-42af-961a-b3f788db4b71" 91 26571.44 176 5376 26571.44 175
"9f01e88a-8b61-42af-961a-b3f788db4b71" 5355 27077.84 178 5633 27077.84 177
"e71efeab-306d-4bfc-ac4e-658638df5f3c" 5500 3693.0 42 5472 3693.0 41
mixed_case_recommended_field WARNING 9

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" "FL 50 & CR 33" 64
"stops.txt" "stop_name" "FL 50 & CR 33" 74
"stops.txt" "stop_name" "CR 565A & SR 50" 80
"stops.txt" "stop_name" "SR 19 & CR 452" 210
"stops.txt" "stop_name" "SR 19 & CR 44" 212
"stops.txt" "stop_name" "FL 50 & CR 455" 379
"stops.txt" "stop_name" "SR 50 & 4TH ST" 398
"stops.txt" "stop_name" "FL 50 & CR 565A" 409
"stops.txt" "stop_name" "SR 19 & CR 450A" 503