Messages

Ich habe seit kurzem auch ein Nexus 5, ich bin von der GPS-Genauigkeit begeistert. GPS-Fix i.d.R. in wenigen Sekunden, auch in Gebäuden und die Genauigkeit ist besser als bei dem alten Gerät (Nexus i9250).

Gesendet von meinem Nexus 5 mit Tapatalk

Do you know cachelab.net? I just found this app/site some days ago, very useful and easier to use than GCC formula editor. It's not yet able to 'speak' to Locus, but the developer is aware of Locus.

Gesendet von meinem Nexus 5 mit Tapatalk

You can use "GCC" (GeoCache Calculator) by "Eisbehr" for this.
It contains - amoung hundrets of other useful  geocaching tools - a "Formel Rechner" which should do what you are looking for.

IMHO this is too special to be integrated in Locus...

Leider habe ich die Frage zum verschieben des POI nicht richtig gestellt, es müsste heißen:

Wie kann ich nachträglich einen POI, den ich während einer Tour auf einer Karte markiere,
nachträglich verschieben, weil er nicht präzise genug sitzt?

Ah, dieses Verschieben meinst Du...
POI öffnen, dann (in V 2.20) auf das Fadenkreuz rechts neben den Koordinaten klicken und dann die Methode zur Bestimmung des neuen Ortes wählen. In dem von dir genannten Beispiel ist dann "von der Karte wählen" wahrscheinlich das beste...

Manchmal stört mich die Taste, oben links "Schneller Wechsel zu Off- Onlinekarten" Kann man sie dort endfernen, ich habe sie ja in der rechten Leiste

Die habe ich garnicht in der oberen Leiste, nur in der rechten... Lange "klicken", dann im Kontextmenü? Ist nur so eine Idee...

Wie kann ich nachträglich einen POI verschieben?

In v2.20: POI öffnen, dann im ganz rechten Menüpunkt ("^") "Verschieben nach..." wählen.

Update:

It seems like this does not happen with every cache. Refreshing some caches works without duplicating waypoints, refreshing some others not...

This one is an example for this behaviour: GC2T5CH.

I'm pretty sure this didn't happen in V2.19, and of course I didn't change any settings in Locus... 

Update 2:
Didn't see menions answer before posting this... Good to see it's already solved. 

In version 2.20:
If I refresh a geocache (using gc4l), each refresh creates a new "set" of associated waypoints for this cache. So after e.g. five refreshs, I have five "parking location" associated with that cache.

Moved to help desk, waiting for thousands of votes there... 
http://help.locusmap.eu/responses/geokrety-support

I'm sure this has been discussed before, but I can't find a topic matching the search term "geokrety"...

So, what about supporting geokretys in Locus?

Currently, we have an Android App (Geokrety Logger) which supports basic logging functions for GeoKretys, but is not (yet) integrated into Locus.

These are my ideas about basic GeoKrety support in Locus:

• A general switch to turn GeoKrety support on or off, there are may cachers which ignore them...
• Locus should know about GeoKretys in caches and display them in a separate tab similar to geocaching.com-trackables. This information can be retrieved online (e.g. http://geokrety.org/export2.php?wpt=GC43), Locus should be able to update this information for single caches or a list of selected caches (like gcvote support).
• Filter and sorting functions should support geokretys
• For basic logging functionality ("retrieve this geokrety from this cache", "drop a geokrety from my inventory in this cache", etc.), the Geokrety Logger App could be used, Locus should provide short cuts to call this app and pass GC-code, tracking code etc to the app, so I don't have to enter the same information there again.

Just my 2 cents, what do other geocachers think about this?

If you find later some time to test this, it will be nice

Fixed in v2.19.0, thank you!

If I display a list of geocaches, sorted by date of last update, and update some single geocaches manually, their position in the list is not changed unless I close the list and reopen it.
Is it possible to dynamically reorder the list after single geocaches have been updated/changed?

. I'm anyway unable to reproduce problem with incorrectly loaded map tiles.

I see this quite often (with vector maps), sometimes after zooming and often when "jumping" around from one vector map to another - maybe this helps reproducing it...

.. really four developers? Damn what they all do? ;-)

According to their app description in google play, they also have 6(!) people doing support... Quite a big team ...

Seems like Seattle has added some more hamsters to their API servers ... ;-)
Your fix works perfectly, thank you!

Gesendet von unterwegs mit Tapatalk 2.