This object is in archive! 

Missing line between the Final and the original placement.

Condor shared this problem 5 years ago
Solved

(EN)

After a system change, Locus works with the original coordinates, and their map mapping is no longer a line between the Final and the original placement.

It's a bad search on the map and it's orientated.


(SK)

Po zmene systemu ako Locus pracuje s pôvodnými súradnicami a ich zobrazením na mape už nie je čiara medzi Finalom a pôvodným umiestnenim.

Dosť zle sa to hľadá na mape a orientuje.

Replies (14)

photo
1

Good day Condor,

are you sure there was a line before? I see in code no such feature. The line is drawn between cache and its waypoints, but "Display on map" option, when you want to display original cache coordinates, never draw a line before. Little complicated task, because this new point has no information about cache itself. Why it is then complicated on the map? Too many caches at once?

photo
1

Hello Menion

I mean the change in the past.

Before that, Locus created the final WP and originally WP coordinates. I did not understand the meaning of the change to the current way. What's the benefit?

photo
1

Hello,

I also do not understand :). Can't remember any change around lines connecting cache with original coordinates, sorry. Maybe it was something made automatically by Geocaching4Locus? Do not know ...

Maybe some old screenshot that may show me better what you miss? Thanks

photo
1

Locus does not create WP original coordinates. With the old way he did it automatically when he created the final WP.

photo
1

@Arcao, wasn't this a feature of your add-on (Geocaching4Locus) some time ago? To be true, I really can't remember, that Locus Map created automatically some waypoints after a change of original coordinates.

It is also on discussion how useful this feature is. Currently, Locus Map place a point with an arrow on the place of original cache coordinates. Can't expect, you will have map full of these "original coordinates" points.

photo
1

Originally coordinates were default to hide setting.

photo
1

Under the new geocaching rules, the multi icon must have 1 stage coordinates. For this reason, people do not add stage 1 (identical coordinates) Locus (move to the final) now "deletes" the original coordinates when creating the final placement. the result is that cache lacks stage 1

photo
1

It is sometimes difficult for me to identify what Locus and what G4L provide. Sorry.

These WPs were created automatically on the following actions:

- Update cache action there is a final on the GC site.

- Automatically add final WP via addon Cache Solver

- Manually adding the WP type final or the name other type contained the "final" word

photo
1

Firstly no need to sorry. Except me and Arcao, probably no one exactly know who/where etc :).

And oki, it is possible that some time ago, it worked that way. I found a quite simple way to improve this ... so next version. Thanks

photo
1

OK and thank you.

As I already wrote. The previous system worked correctly, simply and automatically. A new way has added the skin to the card and a complicated (other non-standard) way of displaying the original coordinates on the map.

I did not understand the purpose of this "improvement".

photo
1

I'll really hardly search in head why I did this smaller change few years ago, sorry.

Anyway as I look on it now, it seems to me perfectly logical. Old coordinates are not separated on the first tab and it's clearly visible that these values are original defined coordinates.

There is no waypoint with exactly defined type "Original coordinates", so old system was more a "workaround" then a logical solution.

photo
1

All points related to cache are looking for a WP card. Parking, interesting places, signpost, stage, final. Everything is in this place. Why should the point originally coordinate should be elsewhere? The logic? My friends complain that the point originally disappeared. I have to explain to them that this one point must search and look elsewhere! Other contexts red line, quick view, hide, stage 1, etc. are unavailable for this point.

photo
1

It seems to me that this change occurred sometime last year. Over the winter season there is a slump. Another thing is that all the original older caches downloaded by the original system have this point on the WP card. They have been preserved. So we normally use them (look today my screen). New downloads if they no longer have them, and therefore this problem is coming slowly at this time.


So now we have a lot of caches in our databases that have this point and new ones without this point. We have to find it in two different places. If I wanted to switch to the new system overall I would have to delete or rewrite all my points in 5 years. We do not want this! This little change has a huge impact.

photo
1

I'm looking at the old cache manually. There is no option to filter by date of download. (updating date is irrelevant) and by 2016 this point. So the change occurred sometime at the end of 2016 or in 2017. But that is not important. We still have thousands of caches in this device with this WP originally coordinated. We also use them.


Edit:

I see that the filter to sort by the date of creation works from the date it was downloaded to the device! (Irrelevant) All my life I thought it was the date hide the cache. This is totally unnecessary. The date of publishing is relevant (hide)

photo
1

Sonny

Thanks for the link :-)

There was a requirement to see the coordinates on the base card. OK. It's OK. They should be added. That is all.

But do not then cancel a good yet functioning system!

This requirement is not there anywhere!

Do we understand @Menion?

photo
1

Sure ...

Replies have been locked on this page!