el-aguila-rural-transportation — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-18T09:52:45Z,
for the dataset file:///shared/el-aguila-rural-transportation_ca70a366.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

El Aguila Rural Transportation
- website: https://webbcountytx.gov/CommunityActionAgency/ElAguila/default.aspx
- phone number: 9567226100
- email: romartinez@webbcountytx.gov

Feed Info

Publisher Name:
El Aguila Rural Transportation: Publisher URL:
https://webbcountytx.gov/CommunityActionAgency/ElAguila/default.aspx: Feed Email:
romartinez@webbcountytx.gov: Feed Language:
English: Feed Start Date:
2024-12-01: Feed End Date:
2026-11-01: Service Window:
2023-11-01 to 2026-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
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: 0
Routes: 3
Shapes: 8
Stops: 80
Trips: 28

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

ShapesFeed InformationFares V1Stops Wheelchair AccessibilityTrips Wheelchair AccessibilityContinuous Stops

Specification Compliance report

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

Notice Code Severity Total

route_long_name_contains_short_name WARNING 1

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name	Dataset
"N"/"Judah"	Muni San Fransisco
"6"/"ML King Jr Blvd"	Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent"	STM Montreal
"1"/"Rangiora/Cashmere"	Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.	routeLongName (?) The faulty record's `route_long_name`.
"3"	4	"Quad"	"Quad City Area"

same_route_and_agency_url WARNING 3

same_route_and_agency_url

Same routes.route_url and agency.agency_url.

A route should not have the same routes.route_url as a record from agency.txt.

You can see more about this notice here.

routeCsvRowNumber (?) The row number of the faulty record from `routes.txt`.	routeId (?) The faulty record's id.	agencyName (?) The faulty record's referenced agency name.	routeUrl (?) The duplicate URL value	agencyCsvRowNumber (?) The row number of the faulty record from `agency.txt`.
2	"1"	"El Aguila Rural Transportation"	"https://webbcountytx.gov/CommunityActionAgency/ElAguila/default.aspx"	2
3	"2"	"El Aguila Rural Transportation"	"https://webbcountytx.gov/CommunityActionAgency/ElAguila/default.aspx"	2
4	"3"	"El Aguila Rural Transportation"	"https://webbcountytx.gov/CommunityActionAgency/ElAguila/default.aspx"	2