Conversation
|
This one currently tracks each of the GTFS entities using 3 different classes. It currently works and have tested it against data from Cleveland RTA, SEPTA, and the Pioneer Valley Transit Authority. Wanted to jot this thought down before I forgot it: Some agencies use a JSON rest API instead of GTFS-RT for vehicle positions. Therefore it would be nice to lump all APIs that require polling together would be nice. For the custom JSON, a mapping of the fields to standard field names would need to be put in place before passing it into standard gobble logic. The more labor intensive alternative would be to create an Server-Sent Event API that would consume GTFS-RT or custom JSON and output the same schema as the MBTA. |
|
@devinmatte I have most of the parsing logic done I just need some help with the threading logic and the trips state manager, hence the ready for review. |
|
How do we run to test this? Normally we just run |
|
I set it up so we can run poetry run |
I remembered I had a project from a few months back where I was trying to convert GTFS_RT data to Moving Feature JSON.
https://anitagraser.com/2024/07/08/new-movingpandas-tutorial-taking-ogc-moving-features-full-circle-with-mf-json/
I was able to merge in most of the code that I had previously written and "gobblified" it as much as possible.
The main missing components for this one are:
Minor concerns