Search for a place,finds an odd cache >10 miles away

[+jallwork]

If I do a normal search for a city, with a 10 mile radius (e.g. Lincoln UK, but also others, which is about 70 miles from me) it also finds one odd cache that is a solved (but not found) cache near me. Using the web app with windows 10.

See screen capture.

[Moun10Bike]

That's because the posted coordinates for that cache fall within the search radius. It's the correct coordinates that are so (unusually) far away.

[+jallwork]

?

No, sorry.The posted coordinates are N 53° 12.056' W 002° 23.262 - this is 123km from Lincoln (N 53° 13.559 W 000° 32.273)

 

FYI the cache it finds is GC2G22Q

Edited December 17, 2017 by jallwork
more information

[Moun10Bike]

Interesting; when I spoof log in as you, I see these same results. However, when logged in as myself, that cache does not show up in the identical search results. It appears that there is some bad data stored for that cache on your account. I'll have to follow up with a dev to see what might be going on.

[+jallwork]

Don't know if this helps, but I have a PCN that says: <removed>

 

Edited December 18, 2017 by Moun10Bike
Removing puzzle solution from post

[+The A-Team]

3 hours ago, jallwork said:

Don't know if this helps, but I have a PCN that says: [REDACTED]

 

You should edit your post and remove the text I redacted above. The owner of that cache probably wouldn't appreciate the solution being posted in a public forum.

[Moun10Bike]

Jallwork, are you still seeing this issue? It appears that my playing around with the cache has corrected it, at least when I try spoof logging in as you.

[+jallwork]

Oops, I forgot this was a public forum.

I still get the problem.

It looks like it occurs somewhere between a search for 7 miles from Lincoln (when it doesn't find the mystery cache) and 8 miles (when it does).

I'll try and find some time to home in a bit more on a possible cache that's causing the problem.

John

[+jallwork]

I've tried mapping 10 miles and 5 mile radius around Lincoln. It looks like it may be linked to a cache between 5 and 8 miles South of Lincoln. I have found a few (but not many) around there - maybe it's related to one of those. I'll try and narrow it down a bit further later.

The problem occurs with one of 175 caches within 4 miles of GC31VBE (but not 3 miles)
 - the only one I've found within this area (unless archived) is GC46KY2, but I found that AFTER I noticed the problem. 

More info later

.. and more info - it errors with the 82  caches within 3 miles of GC32BD0,  but not the 23 caches within 2 miles of same cache.

Edited December 19, 2017 by jallwork
More information