this happens when a cache goes from active to being archived.... it ends
up not getting crawled and the old data is still there until we move it
over into the archived section so it can get updated differently....
i think it should be correct now
jason
Koch, Dan wrote:
> Hello everyone,
>
> Has anyone else noticed that the stats on azgeocaching.com sometimes
> incorrectly calculating the number of in-state vs. out-of-state finds?
>
> For example, today I was admiring my new 100 find stats (thanks for the
> 'props' Hombres, RTW and CHUMP) and noticed that it was listed that I had 97
> in-state and 3 out-of-state finds. I know that I only have 2 out-of-state
> finds so I checked the details. For some reason, azgeocaching.com isn't
> counting the cache 'A Bridge To...' (GC4A46) as being in Arizona! That must
> really be a long bridge... Strange part, though, is that it does list 'A
> Bridge To...' correctly for everyone else that has found it.
>
> I've noticed this behavior before with other caches being considered
> out-of-state but just wanted to see if anyone else had.
>
> Team LazyK - Dan
> _______________________________________________
> Az-Geocaching mailing list
> listserv@azgeocaching.com
> http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching
>
> Arizona's Geocaching Resource
> http://www.azgeocaching.com
(text/plain)