This topic contains 25 replies, has 17 voices, and was last updated by 
-
Posts
-
We were just looking for some caches to find tomorrow. When we put in our own zip code, the caches that came up were not even close to the zip we entered. We tried another nearby zip, and those caches weren’t close either. Has anyone else experienced this? Our guest from Minnesota had the same thing when he entered his zip from back home. Seems odd that this is happening after yesterday’s site upgrade.
My trial Zip run looked OK!
Zip working for 54619
Just tried again-53105 and 53147 were not working at all.
OK-tried 53191 (Williams Bay) and it worked fine. This is messing with our
minds!Tried 53105 and got Wheatland, 53147 got Rochester. Are those correct?
.
53105 is Burlington and 53147 is Lake Geneva.
working fine for 54501
mine is showing lakewood WI (only one zip north when I type in Mountains zip)
Mine’s off…54153 opens up to the Abrams area, not Oconto. Weird 😯
Oconto...the birthplace of western civilization:)
Some work, some don’t for me. Most seem to be “in the neighborhood” of where I’m looking, though, if you’re thinking 20-25 miles as the neighborhood. 🙄
Maybe it’s all due to a shift in the space-time continuum. 😯
53140, 142, 143 all seem to be fine
@sandlanders wrote:
Maybe it’s all due to a shift in the space-time continuum. 😯
Perhaps some time traveling first-to-find hound was going back to nab a few and somehow warped it (the space-time continuum, that is).
So has anybody heard what’s going on with this? The issue is still active today and if it continues, I’m wondering how this might effect pocket queries. I run mine by zip codes.
Oconto...the birthplace of western civilization:)
I just ran my ZIP Code (54301) and the spot is well within said ZIP Code. I’m hoping the rest of Green Bay is experiencing the same accuracy.
-The Happy Hodag!
The buck stops here. . .and gets entered into Where's George.
Where's George? Stimulating the economy one EMS'ed dollar at a time.
You must be logged in to reply to this topic.