Anyone has context on the following not hidden over Git-* issues (I was left thoroughly confused trying to understand it)?
Plus the code that's necessary to generate the map files that OM relies on is no longer openly published. So while true that the actual app code is open source, you can't use it without relying on their proprietary map files.
I've wanted to run it on my wear OS watch, but while you can sideload the APK, wearOS does not have a file browser, so it's not possible to import a planned route or similar. Has anyone here any idea for how to solve this?
1. Address lookups. Many of the buildings in OSM have yet to get street addresses added, so navigating to an address is a bit hit or miss. This gets fixed with time as people update the maps and wouldn't be a show stopper.
2. Real time traffic and detour navigation. This is really needed when navigating around busy cities where a wreck on a major highway can result in significant delays. This needs a combination of an external service (separate from OSM) but also one that has enough adoption to have usable data.
I wonder if we can build a decentralized version of such a reporting service.
Google has the benefit of having their own street-level imagery for house numbers and street names, Android devices for real-time traffic info, and the ability to simply scrape web pages for shop data including opening hours. but in places with a reasonable number of active mappers, OSM is so much richer and more up to date.
There’s a fork from one year ago, CoMaps, that is gaining different features
E.g., I am adding CarPlay Dashboard support that you can test by joining the TestFlight
We are in great need of both more testers and some proper iOS devs (I am not). We’re racing to get scene lifecycle support by September, perfect opportunity if you like modernising old codebases!
https://www.comaps.app/ https://codeberg.org/comaps/comaps
https://codeberg.org/comaps/comaps/projects/21877