You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue appears on all sound transit express (bus) gtfs feeds from all operators (King County, Pierce Transit, Community Transit)
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.
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.
The text was updated successfully, but these errors were encountered: