GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 6.0.0 at 2024-11-15T16:46:08Z,
for the dataset file:/tmp/gtfs-validator-temp7089184767568563925/e1347a2d-493f-4218-931d-c651ef5554f76882042658010855569.zip, with the country code: US.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Jacksonville Transportation Authority
Publisher URL:
https://www.jtafla.com
Feed Email:
Feed Language:
English
Feed Start Date:
2024-08-26
Feed End Date:
2025-02-14

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: 370
  • Routes: 44
  • Shapes: 162
  • Stops: 2458
  • Trips: 4707

Specification Compliance report

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

Notice Code Severity Total
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
route_long_name_contains_short_name WARNING 4

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`.
"400" 36 "Baker" "Baker Wildcat Shuttle"
"800" 39 "Nassau" "Nassau Express Select"
"801" 40 "St. Johns" "St. Johns Express Select"
"811" 41 "Clay" "Clay Express Select"