GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T18:25:57Z,
for the dataset file:///shared/dq1p-carts.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
ITRE
Publisher URL:
https://itre.ncsu.edu/
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2024-01-01
Feed End Date:
2026-12-31

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: 3
  • Routes: 3
  • Shapes: 12
  • Stops: 26
  • Trips: 20

Specification Compliance report

18 notices reported (0 errors, 17 warnings, 1 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
missing_recommended_field WARNING 3

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
route_long_name_contains_short_name WARNING 3

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`.
"102357" 2 "Blue Route" "Blue Route"
"102358" 3 "Orange Route" "Orange Route"
"102359" 4 "Green Route" "Green Route"
stop_too_far_from_shape WARNING 10

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
12 "12" "7918021" 145 "1365995" "Craven DSS" [35.12240925977521,-77.0835291903658] 126.95747936290803
16 "13" "7918025" 209 "1365995" "Craven DSS" [35.12240925977521,-77.0835291903658] 126.95747936290803
17 "14" "7918026" 217 "1365995" "Craven DSS" [35.122418356566044,-77.08352784186961] 126.19343751316792
21 "15" "7918030" 289 "1365995" "Craven DSS" [35.122418356566044,-77.08352784186961] 126.19343751316792
2 "1" "7917364" 2 "1365995" "Craven DSS" [35.12240925977521,-77.0835291903658] 126.95747936290803
4 "2" "7917366" 26 "1365995" "Craven DSS" [35.12242569273255,-77.0835465185646] 126.93664497870961
6 "3" "7917368" 64 "1365995" "Craven DSS" [35.12242569273255,-77.0835465185646] 126.93664497870961
7 "4" "7917655" 69 "1365995" "Craven DSS" [35.12242569273255,-77.0835465185646] 126.93664497870961
8 "5" "7917656" 84 "1365995" "Craven DSS" [35.12242569273255,-77.0835465185646] 126.93664497870961
10 "10" "7918019" 117 "1365995" "Craven DSS" [35.12240925977521,-77.0835291903658] 126.95747936290803
unknown_column INFO 1

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"trips.txt" "block_name" 11