[BUG] wrong cache position in search map

[+arisoft]

Map without search filters

 

 

 

Map with search filters

 

 

Sure you know which one is correct

[+Viajero Perdido]

Lemme guess...

 

Cache-at-center-of-icon

 

vs

Cache-below-the-icon ()

 

If I haven't already mentioned, I really prefer the second, assuming icons to match.

And in a broader sense...

[bUG] USABILITY: Maps look the same, act differently. (Also see, corrected coordinates.)

Edited December 13, 2016 by Viajero Perdido

[+TriciaG]

About a car-length's difference. Probably not enough to worry about.

[+arisoft]

About a car-length's difference. Probably not enough to worry about.

 

Offset depends on zoom level. In this case you are searching the cache from wrong building from wrong street, much longer than allowed saturation distance between caches.

 

 

And finally! The headquarters have been moved to Canada.

 

[+Walts Hunting]

That distance is less than the EPE on most GPSrs.

[+TriciaG]

Offset depends on zoom level. In this case you are searching the cache from wrong building from wrong street, much longer than allowed saturation distance between caches.

Because you always search for caches from an icon at a lower zoom level?

 

IMHO, I think there are bigger issues to be concerned about than a little offset of icons on the maps.

[+The A-Team]

That distance is less than the EPE on most GPSrs.

At high-zoom maybe, but the later example when zoomed out shows the icon off by over 200 miles and in a different country. I hope your GPSr is more accurate than that.

 

IMHO, I think there are bigger issues to be concerned about than a little offset of icons on the maps.

This new version of the map was just released, so now's the time to bring up issues like this while the code is still fresh in their minds.