MobilityData
New Feed Added: CUE Bus - Official Feed
Agency name/Transit Provider:
Location
US
Details
Data type
gtfs
Issue type
New feed
URLs
| Current URL on OpenMobilityData.org | Updated/new feed URL |
|---|---|
| https://data.trilliumtransit.com/gtfs/cuebus-va-us/cuebus-va-us.zip |
Authentication
Authentication type
None - 0
View more details
https://docs.google.com/spreadsheets/d/10eIUxWVtLmc2EATiwivgXBf4bOMErOnq7GFIoRedXHU/edit
Hey @cka-y I noticed in the mobility database ui that this feed is not being shown as deprecated, although it is marked as such in the catalog.
Mobility Database UI: https://mobilitydatabase.org/feeds/gtfs/mdb-2609 Mobility Data Catalog File: https://github.com/MobilityData/mobility-database-catalogs/blob/main/catalogs/sources/gtfs/schedule/us-virginia-fairfax-cue-bus-cue-gtfs-2609.json
@ianktc Thanks for catching this! 🙏 After investigating, I found that we read the catalogs CSV using:
read_csv(filepath, comment="#", low_memory=False)
Since the urls.license column appears before the status column in the spreadsheet and the license url contains # as a character, the status value is being read as np.nan and therefore assumed to be active.
Another side effect of reading the file this way is that any text after a # character gets ignored. For example, the license URL https://www.fairfaxva.gov/government/public-works/cue-bus-map-schedule#GTFS%20Schedule%20Data%20anchor is read as https://www.fairfaxva.gov/government/public-works/cue-bus-map-schedule in the database.
This means any feed containing a # in any field could be affected, so we should address this more generally.
This needs to be fix in the mobility-feeds-api repo
