Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplication of f-piercetransit~rt buses into f-soundtransit~rt #6

Open
kylerchin opened this issue Feb 5, 2024 · 2 comments
Open
Labels
bug Something isn't working

Comments

@kylerchin
Copy link
Member

kylerchin commented Feb 5, 2024

image
The pierce transit feed is more accurate, contains bearing, and has a valid route id

This issue should be tackled during the rebuild of Catenary backend occuring this month.

Bug report made by Flippy on Discord server.

@kylerchin kylerchin added the bug Something isn't working label Feb 5, 2024
@bubonicswindle
Copy link

flippy here:

This issue appears on all sound transit express (bus) gtfs feeds from all operators (King County, Pierce Transit, Community Transit)
image
Using this as an example, King County Metro's route feeds are much more accurate than Sound Transit's, and both are tracking at the same time. I presume this is because the local operators (Metro, Pierce, and Community) operate Sound Transit routes, while also providing the GTFS data for them, and as a result the routes appear twice on Catenary.

@kylerchin
Copy link
Member Author

It appears to me the solution should be, for buses in this region is if the static file doesn't have a route id, then remove it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants