Home
United States Feeds
augusta-ga-us
Source Data Validation Report

augusta-ga-us — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-23T20:14:54Z,
for the dataset file:///shared/augusta-ga-us_fbce39fb.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Augusta Georgia
- website: http://www.augustaga.gov/
- phone number: 706-821-1721
- email: Not provided

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2023-06-06 to 2024-02-24 (?) 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_dates.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 41
Routes: 9
Shapes: 19
Stops: 617
Trips: 403

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

Shapes Route Colors Headsigns Location Types

Specification Compliance report

10 notices reported (0 errors, 10 warnings, 0 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.
2	"a9caf25d-5f6c-4f19-8370-186c68dab502"
3	"012f636c-03b4-44e7-b67e-10df0a100495"
7	"ff9bfd7b-8c78-4d27-8a89-5f5a726247e9"

leading_or_trailing_whitespaces WARNING 5

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"	36	"stop_name"	"Gordon Hwy Transfer Point "
"stops.txt"	58	"stop_name"	"Wrightsboro Rd @ 13th St "
"stops.txt"	196	"stop_name"	"Deans Bridge Rd @ Lyman St "
"stops.txt"	244	"stop_desc"	"Augusta University Apartments - University Village "
"stops.txt"	337	"stop_name"	"Career Dr - Bldg 100 "

missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"

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.
"20260423"	"20230606"	"20240223"