Fleet Location Data
- Brian Ryu
GTFS Data Sources
The data on TransitFeeds is becoming increasingly out of date and cannot be updated, which is negatively impacting travelers. That’s why we’re encouraging users to use the Mobility Database catalogs repository instead, which they can actively contribute to and improve.
Based on feedback from the community in the prototype stage, we want to discuss the transition process in greater depth before committing to a specific date to remove access to http://transitfeeds.com . If you want to participate in a discussion about the deprecation of http://transitfeeds.com , let us know in the catalogs GitHub repo. We commit to giving 6 months notice once the decision is finalized.
GTFS Data routing
Ensure the file name uses the same
account_idas in the DB and follows the scheme likeAccountID_AgencyName_YYYYMMDD.zip.Upload to
s3://data.geopath.org/gtfs_raw/active/Triggers the loading process in AWS Lambda and routing machine.
Once the routing process is finished, a notification is sent through slack. The gzipped result file will be placed in
s3://data.geopath.org/gtfs_processor/production/gz/.If there is any issue, replace the GTFS data with an updated one and repeat the above steps.
Once the GTFS data is ready, append the agency information to the end of
s3://data.geopath.org/geopath/fleet/active_systems/active_systems.csv. This file will be automatically loaded into the Snowflake tableGP_INSIGHTS_DEV.JIE.ACTIVE_SYSTEMS_S3.The status is used to control the action as defined in the Table below
Status Code | Action |
|---|---|
-1 | system to be deleted |
0 | new system |
1 | system with routed trips processed |
2 | system with gtfs data loaded |
4 | system with base impression calculated |
8 | obsolete system |
9 | new system in preparation |
Update Schedule
GTFS data should be updated annually to account for route and calendar changes.
Currently there are 131 systems with written, shared GTFS data. 24 systems do not have GTFS data readily available.
The update process for the 131 systems with data is expected to take approximately 7-10 business days. This would include the download of each data set, formatting, and routing. Each of the files is documented.
Trouble shooting: in certain cases, the files require slight edits for routing purposes. The router highlights the data issue which creates the obstacle.
The 24 systems which require the GTFS data to be manually created will be handled on a individual basis. Geopath can provide direction in terms of building this data.