GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-11T02:09:31Z,
for the dataset file:///shared/liberty-transit_6b4cb582.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Liberty Transit
- website: http://www.libertytransit.org/
- phone number: +1 (912) 877-1472
- email: info@libertytransit.org

Feed Info

Publisher Name:
City of Hinesville: Publisher URL:
http://www.cityofhinesville.org/: Feed Email:
N/A: Feed Language:
English: Feed Start Date:
2021-11-01: Feed End Date:
2024-11-01: Service Window:
2025-11-03 to 2028-11-01 (?) 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
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

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

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

Shapes Feed Information Route Colors Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types

Specification Compliance report

10 notices reported (0 errors, 6 warnings, 4 infos)

Notice Code Severity Total

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	"20260711"	"20241101"	"20260718"

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.
"routes.txt"	2	"agency_id"
"routes.txt"	3	"agency_id"
"routes.txt"	4	"agency_id"

stops_match_shape_out_of_order WARNING 1

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.
13	"3 177726"	"200001"	424	"2461624"	"Azalea St"	[31.845171249186986,-81.60217124850806]	423	"T123001"	"Parkway Plaza"	[31.841210000000004,-81.60089]

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.
"2021-11-01"	"2024-11-01"	"2025-11-03"	"2028-11-01"

service_extends_far_in_the_future INFO 1

service_extends_far_in_the_future

A service end date is more than 2 years in the future.

You can see more about this notice here.

serviceId (?) The service_id that ends far in the future.	serviceWindowEndDate (?) The end date of the service (YYYY-MM-DD format).
"MF"	"2028-11-01"

service_window_outside_feed_period INFO 1

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).
"MF"	"2025-11-03"	"2028-11-01"	0	1461

unknown_column INFO 1

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.
"trips.txt"	"block_name"	11