Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

+1 vote

I'm not sure if this is a bug or if it was intentionally done this way.
I know that mystery caches that have corrected coordinates on the site will show up on the Project-GC live map at the corrected coordinates.
However, I have just noticed that if I move or zoom in such that the original/bogus coordinates are outside the visible part of the map, but the corrected coordinates are in the middle of my screen, the cache disappears from the map.

So could it be that it shows the loaded caches at their corrected coordinates but only loads the caches of which the original/bogus coordinates are on the visible map section ?

Kind regards,
in Bug reports by AxelFox (3.8k points)

1 Answer

0 votes
Best answer
You are correct - this is a design limitation - the boundaries of the map are used to fetch the caches, and these are fetched based on published coordinates. However they are displayed using corrected coordinates (if any) and so some may be outside the display bounds - outside the map. I am unsure if the API will allow fetching based on corrected coordinates - I suspect not (remember that most caches do not have corrrected coordinates)

One solution would be to change the fetch code to specify an additional 3 kilometres outside the map, but a) of the many more caches fetched, only a very few would be displayed (low return for effort) and b) many older puzzle caches had no distance limit so these would still be missing, so fetching an additional 3km radius would be an incomplete solution anyway.
by the Seagnoid (Expert) (44.9k points)
selected by AxelFox
Thx a lot for the confirmation and detailed explanation.
I'm not asking for this to be solved, it's not an inconvenience at all.
It was just something I accidentally noticed and didn't immediately find an answer to in existing threads.
It is inconvenience. The proper solution would be to fetch caches also based on the corrected coordinates. I understand it would complicate queries and caching as these would be different of every user, but it would be least surprise for many of us.