Search
  1. Home
  2. United States Feeds
  3. the-jo
  4. Source Data Validation Report

the-jo — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T15:02:43Z,
for the dataset file:///shared/the-jo_16bc4b77.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:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 1
  • Shapes: 1
  • Stops: 5
  • Trips: 45

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 4

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 "Fridays"
3 "Tuesdays"
4 "Mondays_Tuesdays_Wednesdays_Thursdays"
5 "Weekdays"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
route_long_name_contains_short_name WARNING 1

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`.
"710 K10 Connector" 2 "710" "710 - K10 Connector"
stops_match_shape_out_of_order WARNING 7

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.
2 "710" "1011_255_Jun 20 2011 12:00AM" 3 "KU-Edwards-61" "KU-Edwards" [38.90077972744359,-94.72487575327894] 2 "JCCC Carlsen Center-52" "JCCC Carlsen Center-52" [38.926004348780914,-94.72799135060687]
3 "710" "1012_253_Jun 20 2011 12:00AM" 8 "JCCC Carlsen Center-52" "JCCC Carlsen Center-52" [38.926004348780914,-94.72799135060687] 7 "19th & Haskell-59" "19th & Haskell-59" [38.9499299087613,-95.22347204211474]
7 "710" "1016_254_Jun 20 2011 12:00AM" 22 "JCCC Carlsen Center-52" "JCCC Carlsen Center-52" [38.926004348780914,-94.72799135060687] 21 "19th & Haskell-59" "19th & Haskell-59" [38.9499299087613,-95.22347204211474]
23 "710" "2034_238_Jun 20 2011 12:00AM" 80 "KU-Edwards-61" "KU-Edwards" [38.90077972744359,-94.72487575327894] 79 "JCCC Carlsen Center-52" "JCCC Carlsen Center-52" [38.926004348780914,-94.72799135060687]
24 "710" "2038_159_Jun 20 2011 12:00AM" 85 "KU-Edwards-61" "KU-Edwards" [38.90077972744359,-94.72487575327894] 84 "JCCC Carlsen Center-52" "JCCC Carlsen Center-52" [38.926004348780914,-94.72799135060687]
26 "710" "2039_237_Jun 20 2011 12:00AM" 91 "KU-Lawrence-60" "KU-Lawrence" [38.945667876093125,-95.2634146282694] 90 "19th & Haskell-59" "19th & Haskell-59" [38.9499299087613,-95.22347204211474]
29 "710" "2513_256_Jun 20 2011 12:00AM" 102 "KU-Edwards-61" "KU-Edwards" [38.90077972744359,-94.72487575327894] 101 "JCCC Carlsen Center-52" "JCCC Carlsen Center-52" [38.926004348780914,-94.72799135060687]
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.
"20260509" "20131213" "20190531"