GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T11:00:48Z,
for the dataset file:///shared/franklin-county-public-transportation_f8e665e9.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Franklin County Public Transportation

Feed Info

Publisher Name:
Franklin County Public Transportation
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
N/A
Feed End Date:
N/A

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 4
  • Shapes: 9
  • Stops: 64
  • Trips: 14

Specification Compliance report

94 notices reported (0 errors, 91 warnings, 3 infos)

Notice Code Severity Total
fast_travel_between_consecutive_stops WARNING 1

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.
3 "FC_ADK_SB01_7Day_T01" "FC_FC_13157" 161.57589178972077 2.69293152982868 15 1 "FC_FC_364916" "Franklin County Court House" "05:45:00" 16 2 "15162291" "Wal-Mart - As Needed" "05:45:00"
leading_or_trailing_whitespaces WARNING 3

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

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.
"stops.txt" 18 "stop_desc" " 355 W Main St, Malone - Brewster St entrance"
"stops.txt" 49 "stop_desc" " 3324 State Route 11, Malone, NY 12953"
"stops.txt" 50 "stop_desc" " 3324 State Route 11, Malone, NY 12953"
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 3

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

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 65 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 "FC_ADK_SB02_7Day_T01" 0
5 "FC_ADK_SB02_7Day_T01" 3
8 "FC_ADK_SB02_7Day_T01" 6
11 "FC_ADK_SB02_7Day_T01" 9
14 "FC_ADK_SB01_7Day_T01" 0
16 "FC_ADK_SB01_7Day_T01" 2
17 "FC_ADK_SB01_7Day_T01" 3
20 "FC_ADK_SB01_7Day_T01" 6
35 "FC-TUP-AM-WD-01" 0
36 "FC-TUP-AM-WD-01" 1
37 "FC-TUP-AM-WD-01" 2
38 "FC-TUP-AM-WD-01" 3
39 "FC-TUP-AM-WD-01" 4
40 "FC-TUP-AM-WD-01" 5
41 "FC-TUP-AM-WD-01" 6
43 "FC-TUP-AM-WD-01" 8
44 "FC-TUP-AM-WD-01" 9
45 "FC-TUP-AM-WD-01" 10
46 "FC-TUP-AM-WD-01" 11
47 "FC-TUP-AM-WD-01" 12
57 "FC-PC-01-7D-02" 0
58 "FC-PC-01-7D-02" 1
59 "FC-PC-01-7D-02" 2
60 "FC-PC-01-7D-02" 3
61 "FC-PC-01-7D-02" 4
62 "FC-PC-01-7D-02" 5
63 "FC-PC-01-7D-02" 6
64 "FC-PC-01-7D-02" 7
65 "FC-PC-01-7D-02" 8
66 "FC-PC-01-7D-02" 9
67 "FC-PC-01-7D-02" 10
68 "FC-PC-01-7D-02" 11
69 "FC-PC-01-7D-02" 12
70 "FC-PC-01-7D-02" 13
71 "FC-PC-01-7D-01" 0
72 "FC-PC-01-7D-01" 1
73 "FC-PC-01-7D-01" 2
74 "FC-PC-01-7D-01" 3
75 "FC-PC-01-7D-01" 4
76 "FC-PC-01-7D-01" 5
77 "FC-PC-01-7D-01" 6
78 "FC-PC-01-7D-01" 7
79 "FC-PC-01-7D-01" 8
80 "FC-PC-01-7D-01" 9
81 "FC-PC-01-7D-01" 10
82 "FC-PC-01-7D-01" 11
83 "FC-PC-01-7D-01" 12
84 "FC-PC-01-7D-01" 13
85 "FC-Tup-PM02-WD-01" 0
86 "FC-Tup-PM02-WD-01" 1
stop_without_stop_time WARNING 18

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.
2 "446739468" "St. Regis Falls Adult Center"
3 "5gmm" "Constable"
7 "STOP_1d300e1b-b7fb-4f45-9ba9-adfd8ae8452c" "Crossroads Inn"
8 "STOP_4d03ce83-44fd-4e1a-abf4-05e41f298079" "Westville"
9 "STOP_95b25180-1cc6-4bcb-b183-43bdc56e80b3" "Bombay"
11 "p4wu" "B3CG Interconnect USA"
15 "aa7e5" "Malone-business area"
16 "iy3i" "Tupper Lake Demand Zone"
17 "217y" "Dorsey Local Pick-up Zone"
25 "f903" "Fort Covington"
32 "z4c4" "Jock Trailer Park"
34 "4f97" "Fort Covington Adult Center"
35 "5cf8" "Malone Demand Zone"
36 "dfac2" "Olde School"
44 "3vjg2" "NCCC Hodson Hall - As needed"
47 "76xd1" "L.P. Quinn"
56 "wylb" "St. Regis Falls"
61 "lleb1" "Wild Center"
unknown_column INFO 3

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
"feed_info.txt" "feed_id" 2
"routes.txt" "route_branding_url" 8