regional-transportation — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T11:51:32Z,
for the dataset file:///shared/regional-transportation_f642d53e.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Regional Transportation Agency of Central Maryland
- website: http://www.transitrta.com/
- phone number: 1-800-270-9553
- email: Not provided

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Language:
English: Feed Start Date:
2025-05-17: Feed End Date:
2026-06-30: Service Window:
2025-05-17 to 2026-06-30 (?) 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
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 25
Routes: 14
Shapes: 50
Stops: 641
Trips: 1071

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

ShapesFeed InformationFares V1Route ColorsHeadsignsStops Wheelchair AccessibilityTrips Wheelchair AccessibilityBike AllowedLocation TypesContinuous Stops

Specification Compliance report

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

Notice Code Severity Total

feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

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	"20260619"	"20260630"	"20260719"

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`.
"287-OEC"	10	"Oec"	"OEC Trolley"