This object is in archive!
"Automatically load waypoints" : option to hide original coordinates missing
Declined
Can you please add "hide original coordinates from mysteries" in
Settings > Geocaching > Automatically load waypoints
Thank you very much in advance.
Beste regards from Germany,
Locke.
I like this idea 
Good day Locke,
may you please explain in bigger detail your idea? In best case with some sample GPX Geocache file, so we may try and test in case of bigger interest in implementation. Thank you.
Good day Locke,
may you please explain in bigger detail your idea? In best case with some sample GPX Geocache file, so we may try and test in case of bigger interest in implementation. Thank you.
Hello Menion,
sorry for the delay.
Find attached screenshots I took.
On the left side you can see some points (original coordinates from mysteries) although the mysteries have already been solved, as you can see (mystery icons with red marks).
In my opinion it would be much clearer, when a mystery has corrected coordinates, the original coordinates will be hidden automatically (see on the right).
Therefore I would suggest a checkmark in Settings > Geocaching > Automatically load waypoints to choose whether or not.
Best regards from Germany,
Locke
Hello Menion,
sorry for the delay.
Find attached screenshots I took.
On the left side you can see some points (original coordinates from mysteries) although the mysteries have already been solved, as you can see (mystery icons with red marks).
In my opinion it would be much clearer, when a mystery has corrected coordinates, the original coordinates will be hidden automatically (see on the right).
Therefore I would suggest a checkmark in Settings > Geocaching > Automatically load waypoints to choose whether or not.
Best regards from Germany,
Locke
Good day Locke, thanks for a screenshot and explanation, understand.
So generally you wants to automatically load "reference point" waypoints except! cases when these waypoints are equal original cache coordinates right?
I have to ask, why you store original cache coordinates as a separate waypoints? Maybe this change that will be available in next Locus Map version helps here, because then there should be no need to create such waypoints.
Good day Locke, thanks for a screenshot and explanation, understand.
So generally you wants to automatically load "reference point" waypoints except! cases when these waypoints are equal original cache coordinates right?
I have to ask, why you store original cache coordinates as a separate waypoints? Maybe this change that will be available in next Locus Map version helps here, because then there should be no need to create such waypoints.
Hello Menion,
I do not intentionally store the original cache coordinates as a waypoint. Maybe this is done automatically as soon as I enter the corrected coordinates.
If it is desired in the other thread , that the original coordinates are displayed too, then please make it optional as I suggested in my first posting.
Then everyone can decide for themselves.
Thank you in advance.
Hello Menion,
I do not intentionally store the original cache coordinates as a waypoint. Maybe this is done automatically as soon as I enter the corrected coordinates.
If it is desired in the other thread , that the original coordinates are displayed too, then please make it optional as I suggested in my first posting.
Then everyone can decide for themselves.
Thank you in advance.
Good evening,
interesting because Locus Map do not create these waypoints.
Anyway you will see in next version. It is now possible to display single point on the map that is on place of original cache coordinates. I believe that usage of these original coordinates is really rare so manual display is enough for now.
Anyway this does no solve your problem with unwanted waypoints.
You have a computed coordinates defined on geocaching.com web page? If so, then Geocaching4Locus probably generate this waypoint during download. I personally never needed such waypoint and because over object in application may hold original and also corrected coordinates, I believe that such point is redundant.
@Arcao, it is probably waypoint from your add-on right? Do you have positive experience with this behavior?
Good evening,
interesting because Locus Map do not create these waypoints.
Anyway you will see in next version. It is now possible to display single point on the map that is on place of original cache coordinates. I believe that usage of these original coordinates is really rare so manual display is enough for now.
Anyway this does no solve your problem with unwanted waypoints.
You have a computed coordinates defined on geocaching.com web page? If so, then Geocaching4Locus probably generate this waypoint during download. I personally never needed such waypoint and because over object in application may hold original and also corrected coordinates, I believe that such point is redundant.
@Arcao, it is probably waypoint from your add-on right? Do you have positive experience with this behavior?
Hello Menion,
I am looking forward to the next version to see the function in action.
Do I understand correctly? All mystery coordinates are hidden. One can choose on demand to unhide it?!
Hello Menion,
I am looking forward to the next version to see the function in action.
Do I understand correctly? All mystery coordinates are hidden. One can choose on demand to unhide it?!
Good day Locke,
not sure if I perfectly understand.
Anyway there won't be a change in next version, that solve your issue. I do not agree with need for extra settings you suggested.
Problem I see here is "why these waypoints are created". You wrote that you do not create them manually, so where they come from? Do you have coordinates of final cache defined in personal notes? If so, then these waypoints are probably created by Geocaching4Locus during download. And I'm waiting on Arcao's answer (developer of Geocaching4Locus) if this is correct.
Good day Locke,
not sure if I perfectly understand.
Anyway there won't be a change in next version, that solve your issue. I do not agree with need for extra settings you suggested.
Problem I see here is "why these waypoints are created". You wrote that you do not create them manually, so where they come from? Do you have coordinates of final cache defined in personal notes? If so, then these waypoints are probably created by Geocaching4Locus during download. And I'm waiting on Arcao's answer (developer of Geocaching4Locus) if this is correct.
Hello Locke and Menion,
Sorry for later answer.
Yes, this waypoint come from Geocaching4Locus (G4L). Actually it's created when coordinates are computed in Locus Map or directly on website. The waypoint contain original Geocache coordinates. Unfortunately this feature can't be turned off without change in G4L code. I will try to add possibility to configure this unwanted waypoint creation in a next G4L release.
Hello Locke and Menion,
Sorry for later answer.
Yes, this waypoint come from Geocaching4Locus (G4L). Actually it's created when coordinates are computed in Locus Map or directly on website. The waypoint contain original Geocache coordinates. Unfortunately this feature can't be turned off without change in G4L code. I will try to add possibility to configure this unwanted waypoint creation in a next G4L release.
Hello Locke and Menion,
Sorry for later answer.
Yes, this waypoint come from Geocaching4Locus (G4L). Actually it's created when coordinates are computed in Locus Map or directly on website. The waypoint contain original Geocache coordinates. Unfortunately this feature can't be turned off without change in G4L code. I will try to add possibility to configure this unwanted waypoint creation in a next G4L release.
Hello Locke and Menion,
Sorry for later answer.
Yes, this waypoint come from Geocaching4Locus (G4L). Actually it's created when coordinates are computed in Locus Map or directly on website. The waypoint contain original Geocache coordinates. Unfortunately this feature can't be turned off without change in G4L code. I will try to add possibility to configure this unwanted waypoint creation in a next G4L release.
Good day Arcao,
thanks for an answer.
I think that such waypoints are not needed at all. You may simply use "original coordinates" of GeocachingData container. Locus Map then display these coordinates in first tab of geocache and user may work with them. What you think?
Good day Arcao,
thanks for an answer.
I think that such waypoints are not needed at all. You may simply use "original coordinates" of GeocachingData container. Locus Map then display these coordinates in first tab of geocache and user may work with them. What you think?
Yes, it sounds reasonable. I'll change it in a next release.
Issue #88 - Move original coordinates from waypoint to GeocachingData
Yes, it sounds reasonable. I'll change it in a next release.
Issue #88 - Move original coordinates from waypoint to GeocachingData
Perfect, thanks Arcao!
Locke, I then decline this idea as it should not be needed to implement. Original cache coordinates will be available in first tab of cache detail from where is possible to work with them when needed. Thanks for understanding.
Perfect, thanks Arcao!
Locke, I then decline this idea as it should not be needed to implement. Original cache coordinates will be available in first tab of cache detail from where is possible to work with them when needed. Thanks for understanding.
Hi Locke and Menion,
Could you try a new version 2.1.5.2? It should be fixed there.
Hi Locke and Menion,
Could you try a new version 2.1.5.2? It should be fixed there.
Good day Arcao,
thank you, for me it looks correctly!
Menion
Good day Arcao,
thank you, for me it looks correctly!
Menion
Sorry for the delay...
Looks for me correctly, too!
Thanks for all your great work @Arcao anf @Menion !!!
Regards, Locke.
Sorry for the delay...
Looks for me correctly, too!
Thanks for all your great work @Arcao anf @Menion !!!
Regards, Locke.
Perfect, thanks too!
Perfect, thanks too!
Replies have been locked on this page!