Call-prep brief · checked 2026-07-11
Southwest Ohio Regional Transit Authority (SORTA Metro)
Grade C · 70.1 / 100
Down 0.4 points since 2026-07-10 (C to C).
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
Top three things to fix
Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Equal shape distance same coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Effort: Often a bulk fix in your scheduling software.
Review the flagged fields and fill in the ones your riders would use.
Some files are missing recommended (not required) fields. Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Effort: A field at a time; not urgent.
NTD GTFS readiness: Ready
This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 49 days.
agency_id and NTD ID: Not aligned. Your feed's agency_id is METRO; your National Transit Database ID is 50012. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 50012 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.
Key facts
- Feed URL
- https://www.go-metro.com/uploads/GTFS/google_transit_info.zip
- Last checked
- 2026-07-11
- Service window
- 35 days of service data remain. Last service date 2026-08-15.
- Feed version
- gtfs_20260531-20260815_20260603
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.