moving-bits

Yes, both limitations have to be taken into account. > > No heavy uses (an absolute maximum of 1 request per second). > > […] > > Note that the...

I'm playing around a bit with the Nominatim API currently - seems to be easy enough to use for our use-cases. I can dig a bit deeper into it. To...

> You are thinking of a request cache / proxy? Yeah, c:geo would query our server - our server would look up in its own db and report back, if...

> That makes me think: Isn't there some database + code publicly available to completely host it ourselves? Yes, it is. For self-hosting of a world file they [recommend](https://nominatim.org/release-docs/latest/admin/Installation/#hardware) 128...

> Why do you think a caching proxy would help reducing the calls in any way? How likely is it that people ever search for exactly the same location a...

FYI: Just found out that reverse geocoding ("coords to address" on home screen) always uses the builtin `AndroidGeocoder` as of today, with no fallback to MapQuest. Will be fixed with...

Moving the elevation info I'm fine with, but I don't have a good solution for the second issue yet. I see a couple of alternatives: - have it as a...

Setting WIP label for this PR, as the discussion favors a different solution, as proposed in https://github.com/cgeo/cgeo/pull/15429#issuecomment-2002128498 by @ztNFny

From today's dev meeting: - current solution is fine for GC as well, offers short cut (checkbox) + separate logs (and both are working) => leave it as is -...

FYI: I'm using a slightly different approach: - mark your route, probably having several points (caches, waypoint etc.) along the route - then select "set route start as target" from...