GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T18:39:17Z,
for the dataset file:///shared/lakeland-area-mass-transit-district.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:
2023-03-10
Feed End Date:
2024-03-09

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: 60
  • Routes: 25
  • Shapes: 52
  • Stops: 975
  • Trips: 474

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 3

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "2125-11"
3 "2125-12"
4 "2125-13"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

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" "20240309" "20251212"
mixed_case_recommended_field WARNING 23

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" "22000 US 27" 38
"stops.txt" "stop_name" "1088 US 92 E" 244
"stops.txt" "stop_name" "1052 US 92 E" 245
"stops.txt" "stop_name" "4747 SR 33 N" 402
"stops.txt" "stop_name" "2125 US 98 N" 510
"stops.txt" "stop_name" "2449 US 98 N" 517
"stops.txt" "stop_name" "2440 US 98 N" 518
"stops.txt" "stop_name" "2550 US 98 N" 520
"stops.txt" "stop_name" "2625 US 98 N" 522
"stops.txt" "stop_name" "2750 US 98 N" 535
"stops.txt" "stop_name" "2815 US 98 N" 537
"stops.txt" "stop_name" "6785 US 98 N" 607
"stops.txt" "stop_name" "1910 SR 37 S" 608
"stops.txt" "stop_name" "6108 US 98 N" 610
"stops.txt" "stop_name" "5135 US 98 N" 616
"stops.txt" "stop_name" "4705 US 98 N" 625
"stops.txt" "stop_name" "1500 SR 37" 638
"stops.txt" "stop_name" "3980 US 98 N" 776
"stops.txt" "stop_name" "3813 US 98 N" 839
"stops.txt" "stop_name" "7950 US 98 N" 857
"stops.txt" "stop_name" "8110 US 98 N" 858
"stops.txt" "stop_name" "1002 US 92 E" 894
"stops.txt" "stop_name" "2367 US 92 E" 895
route_long_name_contains_short_name WARNING 9

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`.
"2125-3" 2 "Gold" "Gold Line"
"2125-5" 3 "Purple" "Purple Line"
"2125-10" 6 "Pink" "Pink Line"
"2125-11" 7 "Lime" "Lime Flex"
"2125-45" 14 "Peach" "Peach Line"
"2125-53" 17 "Green" "Green Line"
"2125-55" 19 "Red" "Red Line"
"2125-58" 22 "Lemon" "Lemon Line"
"2125-59" 23 "Coral" "Coral Line"
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.
"20251205" "20230310" "20240308"