Search
  1. Home
  2. United States Feeds
  3. salisbury
  4. Source Data Validation Report

salisbury — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-07T20:48:08Z,
for the dataset file:///shared/salisbury_2441669d.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
TransLoc, Inc.
Feed Email:
N/A
Feed Language:
English

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 5
  • Shapes: 9
  • Stops: 200
  • Trips: 18

Specification Compliance report

29 notices reported (12 errors, 15 warnings, 2 infos)

Notice Code Severity Total
foreign_key_violation ERROR 10

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

childFilename (?) The name of the file from which reference is made. childFieldName (?) The name of the field that makes reference. parentFilename (?) The name of the file that is referred to. parentFieldName (?) The name of the field that is referred to. fieldValue (?) The faulty record's value. csvRowNumber (?) The row of the faulty record.
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "2941" 5
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "2941" 6
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "2941" 7
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "2941" 10
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "2941" 11
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "2941" 13
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3282" 14
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "2941" 16
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3282" 17
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "2941" 19
start_and_end_range_out_of_order ERROR 2

start_and_end_range_out_of_order

Two date or time fields are out of order.

Date or time fields have been found out of order in calendar.txt, feed_info.txt and stop_times.txt.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. startFieldName (?) The start value's field name. startValue (?) The start value. endFieldName (?) The end value's field name. endValue (?) The end value.
"frequencies.txt" 8 "start_time" "19:15:00" "end_time" "15:20:00"
"frequencies.txt" 11 "start_time" "19:15:00" "end_time" "15:20:00"
fast_travel_between_consecutive_stops WARNING 3

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.
4 "774155" "8566" 158.48443309233116 0.6603518045513799 83 26 "337465" "Clancy Hills On Mall Property" "06:57:15" 84 27 "337466" "Jake Alexander Blvd Woodleaf Bowling" "06:57:30"
4 "774155" "8566" 491.89038604924264 2.0495432752051777 84 27 "337466" "Jake Alexander Blvd Woodleaf Bowling" "06:57:30" 85 28 "337338" "Harris Teeter Brenner Ave" "06:57:45"
4 "774155" "8566" 157.20431149476886 0.6550179645615369 85 28 "337338" "Harris Teeter Brenner Ave" "06:57:45" 86 29 "337339" "Standish St Hall St" "06:58:00"
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.
"feed_info.txt" 2 "feed_start_date"
"feed_info.txt" 2 "feed_end_date"
"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"
stop_without_stop_time WARNING 1

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
118 "337350" "Old Concord Rd and S Clay St"
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.
3 "25558" "774153" 33 "337550" "E Council St and N Long St" [35.66573,-80.46577] 32 "337503" "Transfer Site" [35.66646,-80.46761]
unused_shape WARNING 1

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"24306" 1532
service_extends_far_in_the_future INFO 2

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).
"2939" "2029-12-31"
"3281" "2029-12-28"