Re: Issue in checker for GC9X5FV - caches outside county boundaries

The reviewer brought up a case of some of the older caches that had coordinates moved out into remote oceans.

Cache GC64BD was updated to move its coordinates in the far reaches of the ocean, though it is still listed as being in the state of Texas.

While it may have once been present someplace in Texas in this case, we don't currently know where it might have been, and should not associate with a non-county

While one approach to a solution would be an exclusion list, I don't know how many other caches fall into similar scenarios.

The other solution would be to check that the county associated with the cache is not null or empty, as that is how is shows in the results/debug output.

(
[cache_name] => - Fritz Ritz #1 - Camp Swift
[type] => Virtual Cache
[visitdate] => 2002-09-14
[country] => United States
[cache_id] => 25789
[hidden] => 2000-06-15
[region] => Texas
[owner_id] => 36216
[log_id] => 602872
[premium] => 0
[longitude] => -100.000000
[latitude] => 89.000000
[county] =>
[gccode] => GC64BD
)
User usmorrows is an exemplar of this case.

Normally a cache like this should be in the bookmark list of crazy caches.
(crazy_caches = PGC.GetBookmarklist("BMAFMJR", {} )

In this case I have excluded the cache in the config

Confirmed that cache is excluded.

Looking at that bookmark list, it seems most were traveling caches, or have "distant" coordinates. How does one suggest to HQ that a cache might be added to the list?

Just ask your reviewer to get in tough with HQ

Thanks. This can be marked as resolved