busmaps.com

Search

Home
United States Feeds
amarillo-city-transit
Source Data Validation Report

amarillo-city-transit — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T06:55:24Z,
for the dataset file:///shared/amarillo-city-transit_c2bc87ff.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Amarillo City Transit
- website: https://amarillo.gov/departments/community-services/transit
- phone number: (806) 378-3095
- email: transit.manager@amarillo.gov

Feed Info

Publisher Name:
Amarillo City Transit: Publisher URL:
https://amarillo.gov/: Feed Email:
N/A: Feed Language:
English: Feed Start Date:
2019-04-15: Feed End Date:
2021-12-31: Service Window:
2019-01-01 to 2021-12-31 (?) 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
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 12
Shapes: 13
Stops: 345
Trips: 576

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

Shapes Feed Information Fares V1 Route Colors Headsigns Trips Wheelchair Accessibility Bike Allowed

Specification Compliance report

12 notices reported (0 errors, 12 warnings, 0 infos)

Notice Code Severity Total

expired_calendar WARNING 8

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	"WD"
3	"WE"
4	"WE1"
5	"WE2"
6	"WD1"
7	"WD2"
8	"WDRS"
9	"WERS"

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	"20260424"	"20211231"	"20260501"

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 1

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.
"fare_attributes.txt"	2	"agency_id"

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.
"20260424"	"20190101"	"20211231"