Search

logan-county-historical-society — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-29T17:09:38Z,
for the dataset file:///shared/logan-county-historical-society_01e67c8a.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

First Capital Trolley
- website: https://www.firstcapitaltrolley.com/
- phone number: (888) 876-5591
- email: firstcapitaltrolley@yahoo.com

Feed Info

Publisher Name:
First Capital Trolley: Publisher URL:
https://www.firstcapitaltrolley.com/: Feed Email:
ballphin@nado.org: Feed Language:
English: Feed Start Date:
2023-01-01: Feed End Date:
2024-12-31: Service Window:
2024-01-02 to 2024-07-26 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
transfers.txt
trips.txt

Counts

Agencies: 1
Blocks: 4
Routes: 3
Shapes: 6
Stops: 15
Trips: 26

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

ShapesFeed InformationFares V1HeadsignsTrips Wheelchair AccessibilityBike Allowed

Specification Compliance report

18 notices reported (0 errors, 7 warnings, 11 infos)

Notice Code Severity Total

expired_calendar WARNING 5

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	"mtwf"
3	"th"
4	"wed"
5	"mwf"
6	"sat"

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	"20260629"	"20241231"	"20260706"

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.
"20260629"	"20240102"	"20240726"

big_gap_in_service INFO 2

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap.	gapStartDate (?) The first day of the gap.	gapEndDate (?) The last day of the gap.	gapDurationDays (?) The number of days in the gap.
"wed"	"2024-03-20"	"2024-06-05"	76
"sat"	"2024-03-16"	"2024-04-06"	20

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.
"2023-01-01"	"2024-12-31"	"2024-01-02"	"2024-07-26"

trip_headsign_matches_intermediate_stop INFO 8

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.
6	"guthrielangston_winter_IB_T01"	"Dollar General"	"gl_1"	8	"gl_2"
7	"guthrielangston_winter_IB_T02"	"Dollar General"	"gl_1"	8	"gl_2"
8	"guthrielangston_winter_IB_T03"	"Dollar General"	"gl_1"	8	"gl_2"
11	"guthrielangston_Wed_IB_T01"	"Dollar General"	"gl_1"	8	"gl_2"
15	"guthrielangston_summer_IB_T01"	"Dollar General"	"gl_1"	8	"gl_2"
16	"guthrielangston_summer_IB_T02"	"Dollar General"	"gl_1"	8	"gl_2"
17	"guthrielangston_summer_IB_T03"	"Dollar General"	"gl_1"	8	"gl_2"
24	"lanstonstillwater2_T02"	"Scholars Inn"	"gl_6"	2	"gl_7"