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
I would suggest keeping the traffic backend universal so it can work with any navigation app (of all FOSS navigation apps I know, Navit is currently the only one with support for traffic (based on TraFF, which was designed to be app-agnostic); Osmand and Organic Maps would need to have traffic support added). Being able to be used by as many apps as possible would enhance the user base of such a service – more people might be interested in contributing code and ideas, and once we start crowdsourcing traffic data, we’ll have a bigger user base, which in turn means better coverage, better accuracy and more up-to-date information.
#4 has some points on how to encode locations in a universal way that works with any reasonably up-to-date map. The TraFF specification at https://gitlab.com/traffxml/traff also has a scheme to encode event information (predefined event codes for what has happened, speed restrictions, delays etc.).
The text was updated successfully, but these errors were encountered:
I came here via an Osmand ticket (osmandapp/OsmAnd#6878 (comment)), whereas the README mentions Organic Maps.
I would suggest keeping the traffic backend universal so it can work with any navigation app (of all FOSS navigation apps I know, Navit is currently the only one with support for traffic (based on TraFF, which was designed to be app-agnostic); Osmand and Organic Maps would need to have traffic support added). Being able to be used by as many apps as possible would enhance the user base of such a service – more people might be interested in contributing code and ideas, and once we start crowdsourcing traffic data, we’ll have a bigger user base, which in turn means better coverage, better accuracy and more up-to-date information.
#4 has some points on how to encode locations in a universal way that works with any reasonably up-to-date map. The TraFF specification at https://gitlab.com/traffxml/traff also has a scheme to encode event information (predefined event codes for what has happened, speed restrictions, delays etc.).
The text was updated successfully, but these errors were encountered: