GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T17:40:40Z,
for the dataset file:///shared/seastreak.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Seastreak
Publisher URL:
https://seastreak.com
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2020-09-20
Feed End Date:
2030-03-21

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: 64
  • Stops: 14
  • Trips: 183

Specification Compliance report

633 notices reported (0 errors, 633 warnings, 0 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 1

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"
missing_timepoint_value WARNING 612

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 612 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 "11957_0_0" 5
3 "11957_0_0" 6
4 "11957_0_0" 7
5 "11957_0_0" 8
6 "11957_0_1" 5
7 "11957_0_1" 6
8 "11957_0_1" 7
9 "11957_0_1" 8
10 "11957_1_0" 6
11 "11957_1_0" 7
12 "11957_1_0" 8
13 "11957_1_1" 6
14 "11957_1_1" 7
15 "11957_1_1" 8
16 "11957_2_0" 5
17 "11957_2_0" 6
18 "11957_2_0" 7
19 "11957_2_0" 8
20 "11957_2_1" 6
21 "11957_2_1" 7
22 "11957_2_1" 8
23 "11957_3_0" 4
24 "11957_3_0" 5
25 "11957_3_0" 6
26 "11957_3_0" 7
27 "11957_3_0" 8
28 "11957_3_1" 5
29 "11957_3_1" 6
30 "11957_3_1" 7
31 "11957_3_1" 8
32 "11957_4_0" 6
33 "11957_4_0" 7
34 "11957_4_0" 8
35 "11957_4_1" 5
36 "11957_4_1" 6
37 "11957_4_1" 7
38 "11957_4_1" 8
39 "11957_5_0" 6
40 "11957_5_0" 7
41 "11957_5_0" 8
42 "11957_5_1" 4
43 "11957_5_1" 5
44 "11957_5_1" 6
45 "11957_5_1" 7
46 "11957_5_1" 8
47 "11957_6_0" 6
48 "11957_6_0" 7
49 "11957_6_0" 8
50 "11957_6_1" 5
51 "11957_6_1" 6
same_name_and_description_for_stop WARNING 1

same_name_and_description_for_stop

Same name and description for stop.

The GTFS spec defines stops.txt stop_description as:

Description of the location that provides useful, quality information. Do not simply duplicate the name of the location.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty record. stopDesc (?) The faulty record's `stop_desc`.
2 "9954" "Paulus Hook, NJ"
stop_too_far_from_shape WARNING 16

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.
72 "211-176_168_9323" "11757_1_0" 261 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
93 "211-168_9323_175_176" "11743_5_1" 328 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
110 "211-175_176_168_9323" "11743_14_0" 397 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
122 "211-175_168_9323" "11743_20_0" 445 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
4 "211-176_170_168" "11957_1_0" 10 "176" "Highlands, NJ" [40.4665055,-74.03064] 6986.02055068323
95 "211-168_9323_176_175" "11743_6_1" 335 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
70 "211-176_9323_168" "11757_0_0" 254 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
106 "211-176_175_168_9323" "11743_12_0" 379 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
92 "211-175_9323_168" "11743_5_0" 325 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
119 "211-168_9323_175" "11743_18_1" 433 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
71 "211-168_9323_176" "11757_0_1" 257 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
88 "211-176_175_9323_168" "11743_3_0" 311 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
81 "211-9323_168_176" "11757_5_1" 286 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
89 "211-9323_168_175" "11743_3_1" 313 "9323" "Pier 11/Wall St., NYC" [40.702781,-74.005046] 107.2907532908471
7 "211-168_170_176" "11957_2_1" 22 "176" "Highlands, NJ" [40.4665055,-74.03064] 6986.02055068323
101 "211-8306_9825_9323_9819" "11743_9_1" 358 "8306" "West 39th St., NYC" [40.7607422,-74.0050842] 136.21362778677678
stops_match_shape_out_of_order WARNING 2

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.
171 "270-186_7777" "11280_0_0" 587 "7777" "Vineyard Haven, Martha’s Vineyard" [41.45574544886387,-70.60019346504806] 586 "186" "New Bedford, MA" [41.63552399999999,-70.9196609]
172 "270-7777_186" "11280_0_1" 589 "186" "New Bedford, MA" [41.63552399999999,-70.9196609] 588 "7777" "Vineyard Haven, Martha’s Vineyard" [41.45574544886387,-70.60019346504806]