We went out caching in the Kannah Creek area last weekend to both grab three new caches (set by blueskiescindy) and do maintenance on some of our nearby IACG series (It’s A Cattle Guard.) While grabbing the three new ones we drove a different route than when we had placed our IACGs in the area last fall and found three new locations to set more.
We visited the TBs in hand to the caches as we found/maintained several, set (and published for review) the three new caches, and then found/maintained several more. During publication IACG 48 was inadvertently set up with an East coord rather than a West. This placed the cache in the middle of China - somewhere near the Gobi Desert! The reviewer caught it and we had to correct the coords before we could publish, which we did.
It never crossed our minds that this would affect the TB’s mileage – frankly, we had forgotten about it – but even so, we would have figured that the TB would move with the cache. IT DIDN’T! We first noted it when reviewing some of our TB statistics and noted that our own personal TB had gained nearly 13,000 miles overnight! Next thing we know, GCCO race officials are contacting us wanting to know what kind of shenanigans we are working to show such instant high mileage on the Race TBs involved! But yet the cache was showing up in Colorado! (GZ had changed from the log to when they actually saw it)
We are deleting all logs to the China GZ and re-logging back to the corrected coords. This will create a bit of a zig and zag in the map but should be pretty close to reality. To bad we can’t leave the log stand, really got your adrenalin (and interest!) up for a bit, didn’t it! Sorry for the false alarm. Great while it lasted! TEAM kekj
This entry was edited by kekj on Saturday, 28 February 2015 at 06:51:56 UTC.