GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T18:06:03Z,
for the dataset file:///shared/dq2-gwta_a5e6d5f4.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Goldsboro-Wayne Transportation Authority

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. 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: 0
  • Routes: 5
  • Shapes: 5
  • Stops: 237
  • Trips: 113

Specification Compliance report

49 notices reported (1 errors, 12 warnings, 36 infos)

Notice Code Severity Total
invalid_url ERROR 1

invalid_url

A field contains a malformed URL.

Definitions for valid URLs are quite vague. We perform strict validation using the Apache Commons UrlValidator.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"feed_info.txt" 2 "feed_publisher_url" "itre.ncsu.edu"
missing_recommended_field WARNING 6

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.
"feed_info.txt" 2 "feed_version"
"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"
route_long_name_contains_short_name WARNING 5

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`.
"27164" 2 "Green" "Green Route"
"27165" 3 "Purple" "Purple Route"
"27166" 4 "Red" "Red Route"
"27162" 5 "Yellow" "Yellow Route"
"27163" 6 "Blue" "Blue Route"
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.
93 "87075 92609" "2563072" 4596 "1017684" "Swan @ Center" [35.396648502983794,-77.99164476043059] 4595 "3458188" "Dollar General" [35.40799637595907,-77.98297370983019]
big_gap_in_service INFO 25

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"47732" "2017-01-01" "2017-01-16" 14
"47732" "2017-01-16" "2017-04-14" 87
"47732" "2017-04-14" "2017-05-29" 44
"47732" "2017-05-29" "2017-07-04" 35
"47732" "2017-07-04" "2017-09-04" 61
"47734" "2017-01-01" "2017-01-16" 14
"47734" "2017-01-16" "2017-04-14" 87
"47734" "2017-04-14" "2017-05-29" 44
"47734" "2017-05-29" "2017-07-04" 35
"47734" "2017-07-04" "2017-09-04" 61
"47735" "2017-01-01" "2017-01-16" 14
"47735" "2017-01-16" "2017-04-14" 87
"47735" "2017-04-14" "2017-05-29" 44
"47735" "2017-05-29" "2017-07-04" 35
"47735" "2017-07-04" "2017-09-04" 61
"47736" "2017-01-01" "2017-01-16" 14
"47736" "2017-01-16" "2017-04-14" 87
"47736" "2017-04-14" "2017-05-29" 44
"47736" "2017-05-29" "2017-07-04" 35
"47736" "2017-07-04" "2017-09-04" 61
"47741" "2017-01-01" "2017-01-16" 14
"47741" "2017-01-16" "2017-04-14" 87
"47741" "2017-04-14" "2017-05-29" 44
"47741" "2017-05-29" "2017-07-04" 35
"47741" "2017-07-04" "2017-09-04" 61
service_extends_far_in_the_future INFO 10

service_extends_far_in_the_future

A service end date is more than 2 years in the future.

You can see more about this notice here.

serviceId (?) The service_id that ends far in the future. serviceWindowEndDate (?) The end date of the service (YYYY-MM-DD format).
"47738" "2029-12-31"
"47732" "2029-12-29"
"47733" "2029-12-31"
"47734" "2029-12-29"
"47735" "2029-12-29"
"47739" "2029-12-31"
"47736" "2029-12-29"
"47740" "2029-12-31"
"47737" "2029-12-31"
"47741" "2029-12-29"
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