When doing a Multi or other geocache with multiple steps I usually add a new waypoint for each step. Seldom do I know when it was the last step and my final waypoint in GCDroid could then be named something like "step 7".

I then want to save that Final to  Geocaching.com for future use, to see cache collisions for example. As it works today, I need to read the coordinates from my last waypoint, edit the "original" and add them there, and submit online.

I would like to be able to push any waypoint to Geocaching.com as corrected coordinates to simplify this flow.

I really love that GCDroid caches map tiles. I currently have over 3 GB of map tiles cached in my phone, which is quite a lot.

The downside is of course the size of the data. I would suggest saving a timestamp of when each tile was last used, and an option to (automatically, or manually) remove tiles not accessed in X days. I figure X would be useful as anything between 30 and 500 days.

Ich verwende GCDroid mit Offlinekarten von OpenAndroMaps.

Seit geraumer Zeit kann ich aber keine neueren Karten mehr einspielen, weil die V5 Karten bei mir nicht richtig dargestellt werden.

Wenn ich dagegen die V3 Karten vom September 2019 verwende, dann funktioniert alles wunderbar.

Ich habe zur Verdeutlichung zwei Screenshots mit exakt dem selben Kartenausschnitt unten angehängt.

Mache ich was falsch, oder wird V5 einfach nicht unterstützt?

Currently, the Live map works only when you zoom the map to a certain level, in any other case the map is "Live paused". When I bought the app I was really confused, now I'm used to it but I never liked how it works. I would love to have an option to load caches from further away. I know that's something different, but I would use c:geo as a reference, where all caches load regardless of the zoom. I guess (hope) there is no limitation on that from the API side?

I often plan where to go next (on bigger distances), and the only way to do that, is to zoom out (very far) activate normal search and copy all caches to offline DB. That is not convenient on short trips, or when the plans change. Actually, this is never convenient ;)

So I would propose a setting, where you can change the zoom level required to activate "Live map". I know it may get laggy sometimes, but I'm still in favor of that - I like to see where I can go, being able to load caches in a whole city with one refresh of the Live map, and not having to zoom to different districts. That's one of the things that bothers me for some time already. The default setting could be as it is now, so it wouldn't change anything for others who like how it is.

Edit:

To be more precise I've recorded a short video. I'm being zoomed out a little bit more, and can't see any caches (and I would love to see!). I have to go very deep to be able to see anything. That's just frustrating.

When I go to waypoints and correct the coordinates (same when using a GSAK DB with corrected coords) and then use refresh in GCDroid this correction including the new coords are lost

From my point of view a correcteion should not be lost during an update is it is localally and not on gc.com. Only the listing original coords and waypoints (not user related) should be updated

Aktuell scheint keine Funktion vorhanden zu sein, dass man die Höhenlinien auf der Karte erkennen kann. Betrifft die Offline- wie auch die Onlinekarten.

Ich kenne das von den Mapsforge Maps mit passendem Theme, da kann man aktuell auswählen, was man auf der Karte sehen möchte. Ist der Haken im Theme gesetzt, dann kann man die auch sehen.

Fände sowas total praktisch bei längeren Touren.

Es gibt ja eine Möglichkeit bei anderen Apps die diversen Inhalte auf der Karte, die man gerne sehen möchte (u.a. Höhenlinien, Sitzbänke, spezielle Wege/Objekte usw.) einzublenden. Ich fände es schön, wenn es hier auch möglich wäre.

Again, I love the caching of map tiles that GCDroid does. However, some of my tiles are several years old, and they potentially has changed on the tile server by now. Quite likely in the outside areas of cities where new construction is happening all the time. Or satellite images which are "regularly" updated. Most important for Openstreetmap though, since it's community updated.

I would suggest the following change in the flow.

1) Use whatever tiles that are cached, exactly like now.

2) If the tiles is older than X days (configurable, 30-1000 maybe), use that tile while fetching a new fresh one.

3) Replace the used map tile with a new one once fetched, if they differ (crc32 or similar).

Not sure what is actually doable with the map library you are using, but this is my suggestion without any technical insight. You can probably figure out variants that technically works out.

Es ist bei der Suche nach aktuellen Events, gerade in Ballungsgebieten echt nervig, wenn von 10 angezeigten Events, 5 in der Vergangenheit liegen. Hier könnte ein einfacher Filter Eventdatum >= Tagesdatum sofort Abhilfe schaffen. Gerade in einer App wo man nicht wie im Browser ein SlideOver / FirstKlick mit den Basisinformationen realisieren kann.