GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T19:50:11Z,
for the dataset file:///shared/dq1-ncdotferries.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:
2025-01-01
Feed End Date:
2025-12-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 8
  • Shapes: 16
  • Stops: 13
  • Trips: 184

Specification Compliance report

33 notices reported (0 errors, 32 warnings, 1 infos)

Notice Code Severity Total
expired_calendar WARNING 10

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.
3 "114991"
4 "114992"
5 "114993"
7 "114995"
8 "114996"
9 "115001"
10 "115002"
11 "115003"
13 "114997"
15 "114999"
fast_travel_between_consecutive_stops WARNING 2

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
5 "6947985" "23229" 202.88280222584152 3.381380037097358 8 0 "310816" "Cherry Branch" "08:30:00" 9 1 "310817" "Minesott Branch" "08:30:00"
6 "8129402" "23229" 202.88280222584152 3.381380037097358 10 0 "310816" "Cherry Branch" "13:30:00" 11 1 "310817" "Minesott Branch" "13:30:00"
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

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 "20251212" "20251231" "20260111"
missing_bike_allowance WARNING 1

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
15 "23230" "10123907"
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 8

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"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
mixed_case_recommended_field WARNING 1

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.
"trips.txt" "trip_headsign" "oc" 112
same_stop_and_route_url WARNING 7

same_stop_and_route_url

Same stops.stop_url and routes.route_url.

A stop should not have the same stop.stop_url as a record from routes.txt.

You can see more about this notice here.

stopCsvRowNumber (?) The row number of the faulty record from `stops.txt`. stopId (?) The faulty record's id. stopUrl (?) The duplicate URL value. routeId (?) The faulty record's id from `routes.txt. routeCsvRowNumber (?) The row number of the faulty record from `routes.txt`.
2 "310816" "http://www.ncferries.com/ferries/cherry-branch-to-minnesott-beach" "23229" 5
4 "310821" "http://www.ncferries.com/ferries/hatteras-to-ocracoke" "23230" 6
6 "310819" "http://www.ncferries.com/ferries/bayview-to-aurora" "23233" 9
9 "277369" "http://www.ncferries.com/ferries/cedar-island-to-ocracoke" "23231" 7
10 "277633" "http://www.ncferries.com/ferries/swan-quarter-to-ocracoke" "23232" 8
12 "310822" "http://www.ncferries.com/ferries/currituck-to-knotts-island" "23234" 2
14 "310814" "http://www.ncferries.com/ferries/southport-to-fort-fisher" "23235" 3
stops_match_shape_out_of_order WARNING 1

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.
89 "Hatteras" "10123955" 177 "310821" "Hatteras" [35.20799,-75.70267] 176 "277370" "Ocracoke, south" [35.11557,-75.98671]
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