This checkin to GC9EXXC Shady Seat on The Green reflects a geocaching.com log entry. See more of Dan's cache logs.
Quick check while I was passing, as nobody’s logged this cache during our stupidly-hot July or August (and I don’t blame them: it’s been horrible outdoors!). Anyway: the cache is fine and healthy and looking forward to its next visitor!
This checkin to GC9BHWG Watercress beds reflects a geocaching.com log entry. See more of Dan's cache logs.
Despite immediately honing in on exactly the right host, it still took me an embarrassingly long time to find this cache. This, despite having found – and even hidden – cache contsibers of exactly this type before!
My usual technique for lazily finding them, which involves swooping my phone through likely hiding spots with the camera in ‘selfie’ mode, as a mirror, somehow didn’t help me spot this one and it took until I bothered to crouch down (in the rain, in my already-wet trousers) and felt around free host before I reached it!
TFTC.
This checkin to GC8ZWZ3 Letcombe Bridges 1 reflects a geocaching.com log entry. See more of Dan's cache logs.
QEF while passing through the village on a circular walk. TFTC!
This checkin to GC4H2MB Church Micro 4008…Letcombe Regis reflects a geocaching.com log entry. See more of Dan's cache logs.
Found the grave, but this is now the second offset I’ve found here that’s asked me to double-back on my walk. Nope! I’m just going to save the calculated coordinates for the next time I’m in the area! Looking forward to returning!
This checkin to GC9F5YC GIs in Letcombe reflects a geocaching.com log entry. See more of Dan's cache logs.
Found the clues and solved the coordinates, but I’ve JUST walked past the final location a while ago and don’t feel like doubling back today!
A=How many letters in the word underneath Knoxville?
B=A*2
C=Number of letters in place where “Beckett” came from.
D=C+1
E=F Number of letters in the word underneath Knoxville divided by 2
I should have worked out the likely location before I set out. Given that A must be a single digit number that can be doubled (B) to get a single digit number and halved (E, F) to get a second, there’s only one possible value for those four clues! The other two C and D are related to one another as well, resulting in a grand total of only 9 possible pairs of coordinates at which this cache could live (of which I’ll bet the “right” one stands out as the most-likely, even without making assumptions about the length of place names!). So yeah, I’m kicking myself slightly for not solving this before I visited.
But I’m glad I visited anyway. The historical connection is interesting and I enjoyed learning about it.
Maybe I’ll come find the actual cache next time I’m in the area!
This checkin to GC9QWHD Plankton's cache reflects a geocaching.com log entry. See more of Dan's cache logs.
Like many before me, from the looks of things, I didn’t find the cache at the published coordinates but about 11 metres away at N 51° 34.086′, W 001° 26.441′. Possibly worth the CO checking if those coordinates work better for them, too, during their next maintenance visit. TFTC!
This checkin to GC93M2N Segsbury Fort reflects a geocaching.com log entry. See more of Dan's cache logs.
A challenging but worthwhile find during a walk along and around the Ridgeway.
My initial attempt to collect the coordinates was way off because I misinterpreted some of the instructions and it yielded a point almost 2km away! My second attempt looked better, giving a likely-looking spot… but the checksum was out by one!
I triple-checked all the sources and was still out! I was most-confident in my calculated latitude, so I permuted all possible one-point longitude changes that would satisfy the checksum. This yielded two candidates: one a tenth of a minute out from my original calculation, and one a thousandth of a minute out.
The one that was a tenth of a minute out from my calculation “felt wrong”, being way off the path, so I merely glanced its way as I walked past to the other. The one that was a thousandth of a minute – which equates to only around a metre! – looked better, and sure enough when I got there I found a multitude of likely hiding spots.
The hide itself was sneaky too: I had to go further from the path than I expected in order to “look back” and spot the cache – very tricky in the thickening undergrowth! But find it I did, and duly signed the log before returning it to its snug little spot.
TFTC! FP awarded for the adventure.
This checkin to GC46RY8 It really is about the (2 millionth) cache reflects a geocaching.com log entry. See more of Dan's cache logs.
This morning I came up to explore the Ridgeway and escape from thinking about Life Stuff for a bit. (Although escaping from the rain wasn’t a possibility! It was real wet up here today!)
I was wandering this path in a bit of a reverie when I spotted something unusual and thought it a good candidate for a geocache to hide, having momentarily forgotten that this was in fact the reason I was on this particular footpath in the first place! But my geosense was solid, because when I took my phone out to check I discovered that, sure enough, I’d stopped right alongside the hiding area.
The cache was an easy find and I appreciated the proper-sized container! The lid is slightly damaged and no longer makes a complete seal but so long as it’s properly returned to its hiding place it doesn’t need any urgent attention.
SL, TNLN, TFTC!
This checkin to GC39X1K GH #11 twisted tree reflects a geocaching.com log entry. See more of Dan's cache logs.
Found cache contents first, some of which I was only able to identify thanks to the photo in the previous log. Cache container, minus lid, was found a reasonable distance away, but this badly-damaged, nearly-destroyed cache is a goner, I feel.
It’s seen no owner maintenance in most of a decade and CO doesn’t seem to have even logged in to GCCOM for 6½ years ,and it’s clearly getting wrecked in between every single attempted find. It should probably be put to rest.
This checkin to GC39WVC G h # 10 reflects a geocaching.com log entry. See more of Dan's cache logs.
A few attempts at hacking through the brambles to get near the hint location had me thinking that perhaps this was a wintertime only cache… before I realised that there was a different route by which I might approach it. Soon I was directly atop the coordinates and immediately sighted what I was looking for.
Unfortunately the cache was in the open, wide open, with a damaged clasp for its lid and its contents strewn about. Possibly somebody had put something ill-advised into the container and an animal had torn it open? Or else muggles, maybe?
Reassembled everything as best I could and returned it to its hiding place, but the cache container and contents would enjoy some maintenance.
This checkin to GC4H2N6 Church Micro 4009 ... Letcombe Bassett reflects a geocaching.com log entry. See more of Dan's cache logs.
A quick diversion before a hike up Gramp’s Hill and along the Ridgeway. After collecting the required information I pressed on to the cache, meeting some friendly ponies and horses on the way.
The coordinates were spot on, which surprised me as the location didn’t seem to be accessible! But it is, just a little overgrown! TFTC!
This checkin to GCBX0JC Church Micro 12106...Standlake reflects a geocaching.com log entry. See more of Dan's cache logs.
After a walk out with the dog to claim the FTF on nearby GCBX0R7, I figured that I still had a little a few minutes on my hands before the code I’d been writing for my day job finished deploying and testing itself, so I thought I’d try to go two-for-two with this, a second FTF!
Coordinate components A through D were easy to collect, but E posed us a problem: from the way it’s put forward in the cache description, the answer I came up with didn’t make any sense! I double-checked A through D and, confident in them, mathematically inferred a range of possible values for E, but couldn’t find any way to conceivably get any of them!1
In any case: of the handful of possible values for E, only one made sense/pointed anywhere believable, and it fit the checksum so we set out. The cache was easy to find, and what an excellent container! Amazing work! The container alone would have been worth a favourite point, if only I hadn’t been completely unable to parse that fifth coordinate component.
Signed log and returned the cache to its hiding place. Hoping the next cacher doesn’t get as confused as I did! TFTC!
1 I’ll message the CO to get to the bottom of my confusion!
This checkin to GCBX0R7 War Memorial #???? ~ Standlake reflects a geocaching.com log entry. See more of Dan's cache logs.
After liaising with the CO to get the formula fixed following my previous effort, the geohound and I came out for a drizzly walk in-between the downpours to have a second attempt at the FTF. We’re living in Standlake temporarily while our house is repaired following a catastrophic flood earlier in the year, and while the dog – who doesn’t much enjoy rain – was initially hesitant about coming out with me, she warmed to the idea just in time for us to set out.
The cache was an easy find in the second place I looked (if I’d checked the hint it’d have been the first place I looked). SL and returned, before pressing on to attempt a second FTF, this time at GCBX0JC.
TFTC, and for the quick turnaround on correcting the calculation!
This checkin to GCBX0R7 War Memorial #???? ~ Standlake reflects a geocaching.com log entry. See more of Dan's cache logs.
Well I feel especially thick right now. Probably I’ve done something stupid, but I rushed down here between-meetings in hope of an FTF, collected all the numbers, did the maths, and got… the same coordinates I started with! Wot?
The checksum even works out with the original coordinates, too! Which of course can happen organically but might mean there’s been a muck-up sonewhere…
Now I’m just wondering: is it me that can’t follow simple instructions? (Could be!) Or is there a problem with this listing?
Guess I’ll have to wait and see, when some other cacher tries…
This checkin to GC448J6 EL TRESOR DEL POU DEL MON reflects a geocaching.com log entry. See more of Dan's cache logs.
When I visited two years ago I thought I’d solved the puzzle but couldn’t find the cache. I’m in the area again today and thought I’d make another attempt, but the recent ‘enabled’ seems to suggest that it isn’t actually available?
Maybe I can try again in 2028!