Refreshing a cache with corrected coords does not update changed corrected coords
I have downloaded an "Unknown" geocache with corrected coordinates with GC4L. After a while the owner moved the cache and provided a new formula. After recalculation I updated the corrected coordinates on GC.com and refreshed the cache with GC4L.
Problem: the corrected coordinates in Locus Map are not updated when refreshing the cache. I had to remove the corrected coordinates in Locus Map and refresh the geocache again.
How to troubleshoot:
1) Enter corrected coordinates on GC.com
2) Download the cache to Locus Map
3) change the corrected coords on GC.com
4) Refresh the cache with GC4L
5) corrected coords are not updated in Locus Map
Keep up your excellent work, Locus Map + GC4L + Fieldnotes + MCS + Coordinate Joker make geocaching a lot more easy and save the woods!
Cheers,Hampf
The same problem 
Hello Hampf,
sorry for the delay in response. Let's move with this issue a little bit.
From what I know (and @Arcao please correct me), there is no information, when coordinates of the cache and also your own corrected coordinates (on gc.com) were changed! So application itself, do not know if corrected coordinates in the application are older or newer than coordinates downloaded from the web.
And this is the problem. In your case, the app does not update coordinates in the downloaded cache. But in the opposite case without known time, the downloaded cache may overwrite your own local modified coordinates.
Ideas from anyone how to solve this are welcome. I'm anyway worried that we already discussed this few times during last years and never found a working solution.
Menion
Hello Hampf,
sorry for the delay in response. Let's move with this issue a little bit.
From what I know (and @Arcao please correct me), there is no information, when coordinates of the cache and also your own corrected coordinates (on gc.com) were changed! So application itself, do not know if corrected coordinates in the application are older or newer than coordinates downloaded from the web.
And this is the problem. In your case, the app does not update coordinates in the downloaded cache. But in the opposite case without known time, the downloaded cache may overwrite your own local modified coordinates.
Ideas from anyone how to solve this are welcome. I'm anyway worried that we already discussed this few times during last years and never found a working solution.
Menion
Hej Menion,
I suppose the only way would be to check if both corrected coord differ and post a warning dialog just like the way when a waypoint is already stored in the database. That way the user can decide what to do: keep the old info, overwrite them or create a new waypoint.
What I do NOT expect to be implemented: Mass update of cache information when selecting more than one geocache in the list. I only thought of just the actively shown geocache.
It would be very nice if Locus could overwrite the corrected coordinates in the geocaching database with the updated coords of the shown geocache after manual changes or by the "Cache Solver" in the field at my command (definitely not automatically and definitely a very, very low priority for me).
Cheers,
Hampf
Hej Menion,
I suppose the only way would be to check if both corrected coord differ and post a warning dialog just like the way when a waypoint is already stored in the database. That way the user can decide what to do: keep the old info, overwrite them or create a new waypoint.
What I do NOT expect to be implemented: Mass update of cache information when selecting more than one geocache in the list. I only thought of just the actively shown geocache.
It would be very nice if Locus could overwrite the corrected coordinates in the geocaching database with the updated coords of the shown geocache after manual changes or by the "Cache Solver" in the field at my command (definitely not automatically and definitely a very, very low priority for me).
Cheers,
Hampf
Hello Hampf,
this will need a little more complex approach. Suggest to vote for to an existing topic here https://help.locusmap.eu/topic/sync-local-computed-coordinates-to-geocachingcom-profile , where the point is opposite, but I believe that both cases should be covered. Thanks
Hello Hampf,
this will need a little more complex approach. Suggest to vote for to an existing topic here https://help.locusmap.eu/topic/sync-local-computed-coordinates-to-geocachingcom-profile , where the point is opposite, but I believe that both cases should be covered. Thanks
Replies have been locked on this page!