Search
  1. Home
  2. United States Feeds
  3. eastern-upper-peninsula-transporation-authority
  4. Source Data Validation Report

eastern-upper-peninsula-transporation-authority — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-25T06:18:39Z,
for the dataset file:///shared/eastern-upper-peninsula-transporation-authority_940288ae.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Eastern Upper Peninsula Transporation Authority

Feed Info

Publisher Name:
Eastern U.P. Transporation Authority
Publisher URL:
https://www.eupta.net/
Feed Email:
euptatrans@eupta.net
Feed Language:
English
Feed Start Date:
2024-04-22
Feed End Date:
2025-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 5
  • Shapes: 0
  • Stops: 21
  • Trips: 426

Specification Compliance report

272 notices reported (0 errors, 259 warnings, 13 infos)

Notice Code Severity Total
expired_calendar WARNING 3

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.
6 "ferry_smtwtfs_sug"
7 "ferry_smtwt_wsug"
8 "ferry_fs_wsug"
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.
425 "kinch_kcf_am_T25" "2kinch" 240.48211318919482 24.04821131891948 876 1 "170" "KCF" "05:45:00" 877 2 "105" "EUPTA" "05:50:00"
422 "kinch_kcf_am_T22" "2kinch" 1442.892679135169 24.04821131891948 872 1 "170" "KCF" "00:00:00" 873 2 "105" "EUPTA" "00:00:00"
426 "kinch_kcf_am_T26" "2kinch" 240.48211318919482 24.04821131891948 878 1 "170" "KCF" "13:45:00" 879 2 "105" "EUPTA" "13:50:00"
fast_travel_between_far_stops WARNING 3

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

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.
425 "kinch_kcf_am_T25" "2kinch" 240.48211318919482 24.04821131891948 876 1 "170" "KCF" "05:45:00" 877 2 "105" "EUPTA" "05:50:00"
422 "kinch_kcf_am_T22" "2kinch" 1442.892679135169 24.04821131891948 872 1 "170" "KCF" "00:00:00" 873 2 "105" "EUPTA" "00:00:00"
426 "kinch_kcf_am_T26" "2kinch" 240.48211318919482 24.04821131891948 878 1 "170" "KCF" "13:45:00" 879 2 "105" "EUPTA" "13:50:00"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260725" "20251231" "20260801"
missing_bike_allowance WARNING 245

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
22 "drummond" "Detour2Drummon_sun_wed_T01"
23 "drummond" "Detour2Drummon_sun_wed_T02"
24 "drummond" "Detour2Drummon_sun_wed_T03"
25 "drummond" "Detour2Drummon_sun_wed_T04"
26 "drummond" "Detour2Drummon_sun_wed_T05"
27 "drummond" "Detour2Drummon_sun_wed_T06"
28 "drummond" "Detour2Drummon_sun_wed_T07"
29 "drummond" "Detour2Drummon_sun_wed_T08"
30 "drummond" "Detour2Drummon_sun_wed_T09"
31 "drummond" "Detour2Drummon_sun_wed_T10"
32 "drummond" "Detour2Drummon_sun_wed_T11"
33 "drummond" "Detour2Drummon_sun_wed_T12"
34 "drummond" "Detour2Drummon_sun_wed_T13"
35 "drummond" "Detour2Drummon_sun_wed_T14"
36 "drummond" "Detour2Drummon_sun_wed_T15"
37 "drummond" "Detour2Drummon_sun_wed_T16"
38 "drummond" "Detour2Drummon_sun_wed_T17"
39 "drummond" "Detour2Drummon_sun_wed_T18"
40 "drummond" "Detour2Drummon_sun_wed_T19"
41 "drummond" "Detour2Drummon_sun_wed_T20"
63 "drummond" "Detour2Drummon_thurs_sat_T01"
64 "drummond" "Detour2Drummon_thurs_sat_T02"
65 "drummond" "Detour2Drummon_thurs_sat_T03"
66 "drummond" "Detour2Drummon_thurs_sat_T04"
67 "drummond" "Detour2Drummon_thurs_sat_T05"
68 "drummond" "Detour2Drummon_thurs_sat_T06"
69 "drummond" "Detour2Drummon_thurs_sat_T07"
70 "drummond" "Detour2Drummon_thurs_sat_T08"
71 "drummond" "Detour2Drummon_thurs_sat_T09"
72 "drummond" "Detour2Drummon_thurs_sat_T10"
73 "drummond" "Detour2Drummon_thurs_sat_T11"
74 "drummond" "Detour2Drummon_thurs_sat_T12"
75 "drummond" "Detour2Drummon_thurs_sat_T13"
76 "drummond" "Detour2Drummon_thurs_sat_T14"
77 "drummond" "Detour2Drummon_thurs_sat_T15"
78 "drummond" "Detour2Drummon_thurs_sat_T16"
79 "drummond" "Detour2Drummon_thurs_sat_T17"
80 "drummond" "Detour2Drummon_thurs_sat_T18"
81 "drummond" "Detour2Drummon_thurs_sat_T19"
82 "drummond" "Detour2Drummon_thurs_sat_T20"
83 "drummond" "Detour2Drummon_thurs_sat_T21"
129 "sugar" "SSM2Sugar_summer_sun_mon__T01"
130 "sugar" "SSM2Sugar_summer_sun_mon__T02"
131 "sugar" "SSM2Sugar_summer_sun_mon__T03"
132 "sugar" "SSM2Sugar_summer_sun_mon__T04"
133 "sugar" "SSM2Sugar_summer_sun_mon__T05"
134 "sugar" "SSM2Sugar_summer_sun_mon__T06"
135 "sugar" "SSM2Sugar_summer_sun_mon__T07"
136 "sugar" "SSM2Sugar_summer_sun_mon__T08"
137 "sugar" "SSM2Sugar_summer_sun_mon__T09"
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.
5 "115" "Woodside/Jon Patrick"
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.
"20260725" "20250117" "20260116"
unusable_trip WARNING 2

unusable_trip

Trips must have more than one stop to be usable.

A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id.
423 "kinch_kcf_am_T23"
424 "kinch_kcf_am_T24"
feed_valid_beyond_total_service_window INFO 1

feed_valid_beyond_total_service_window

The feed is valid 14 days beyond its total service window.

You can see more about this notice here.

feedStartDate (?) The feed start date from feed_info.txt. feedEndDate (?) The feed end date from feed_info.txt. serviceWindowStartDate (?) The earliest active service date across all services. serviceWindowEndDate (?) The latest active service date across all services.
"2024-04-22" "2025-12-31" "2025-01-01" "2027-12-31"
service_window_outside_feed_period INFO 10

service_window_outside_feed_period

A service window is not covered by the feed's validity period.

You can see more about this notice here.

serviceId (?) The service_id whose active window extends outside the feed validity period. serviceWindowStartDate (?) The first active date of the service window. serviceWindowEndDate (?) The last active date of the service window. daysBeforeFeedStart (?) Number of days the service window extends before feed_start_date (0 if none). daysAfterFeedEnd (?) Number of days the service window extends after feed_end_date (0 if none).
"ferry_tfs_drum" "2025-01-02" "2027-01-15" 0 380
"ferry_smtw_drum" "2025-01-05" "2027-01-13" 0 378
"ferry_smtwtfs_sug" "2025-05-01" "2026-01-16" 0 16
"mtwtf_am_bus_kin_chip" "2025-01-01" "2027-12-31" 0 730
"ferry_mtwtf_wneeb" "2025-01-01" "2027-12-31" 0 730
"ferry_tfs_n" "2025-01-01" "2027-12-31" 0 730
"mtwtf" "2025-01-02" "2027-01-15" 0 380
"mtwtf_am_bus_kin_kcf" "2025-01-01" "2027-12-31" 0 730
"daily" "2025-01-02" "2027-12-31" 0 730
"ss_bus" "2025-01-04" "2027-01-10" 0 375
trip_headsign_matches_intermediate_stop INFO 2

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
416 "soo_weekend_casino_1_T01" "EUPTA" "105" 3 "120"
417 "soo_weekend_casino_1_T02" "EUPTA" "105" 3 "120"