Search
  1. Home
  2. United States Feeds
  3. newburgh-beacon-shuttle
  4. Source Data Validation Report

newburgh-beacon-shuttle — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T10:31:03Z,
for the dataset file:///shared/newburgh-beacon-shuttle_e1612c89.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

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. routes.txt
  4. shapes.txt
  5. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts

  • Agencies: 1
  • Blocks: 5
  • Routes: 5
  • Shapes: 22
  • Stops: 13
  • Trips: 26

Specification Compliance report

195 notices reported (0 errors, 193 warnings, 2 infos)

Notice Code Severity Total
expired_calendar WARNING 1

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.
2 "WD"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
missing_timepoint_value WARNING 189

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

Only the first 50 of 189 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "A5" 0
3 "A5" 1
4 "A5" 2
5 "A5" 3
6 "A5" 4
7 "A5" 5
8 "A5" 6
9 "A5" 7
10 "B1" 0
11 "B1" 1
12 "B1" 2
13 "B1" 3
14 "B1" 4
15 "B1" 5
16 "B1" 6
17 "B2" 0
18 "B2" 1
19 "B2" 2
20 "B2" 3
21 "B2" 4
22 "B2" 5
23 "B2" 6
24 "B2" 7
25 "B3" 0
26 "B3" 1
27 "B3" 2
28 "B4" 0
29 "B4" 1
30 "B4" 2
31 "B4" 3
32 "B4" 4
33 "B4" 5
34 "B4" 6
35 "B4" 7
36 "B5" 0
37 "B5" 1
38 "B5" 2
39 "B5" 3
40 "B5" 4
41 "B5" 5
42 "B5" 6
43 "B5" 7
44 "C1" 0
45 "C1" 1
46 "C1" 2
47 "C1" 3
48 "C1" 4
49 "C1" 5
50 "C1" 6
51 "C1" 7
stop_too_far_from_shape WARNING 1

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.
25 "2xqq" "E3" 181 "8" "Beacon Station" [41.50551,-73.98522] 112.87498098516177
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260509" "20210401" "20251231"
unknown_column INFO 2

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.
"agency.txt" "agency_branding_url" 7
"routes.txt" "route_branding_url" 8