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

Keep the project universal, not dependent on a particular navigation app #7

Open
mvglasow opened this issue Sep 28, 2024 · 0 comments

Comments

@mvglasow
Copy link

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.).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant