Dead Dad Day

I’m not sure that I process death in the same way that “normal” people do. I blame my family.

WhatsApp chat: Sarah Huntley says "Happy dead dad day x" and Doreen Huntley replies "Shouldn't it be 'sad dead dad day'"?
My sisters and I have wished one another a “Happy Dead Dad Day” every 19 February since his death.

When my grandmother died in 2006 I was just in the process of packing up the car with Claire to try to get up to visit her before the inevitable happened. I received the phone call to advise me that she’d passed, and – ten emotional minutes later – Claire told me that she’d “never seen anybody go through the five stages of grief as fast as that before”. Apparently I was a textbook example of the Kübler-Ross model, only at speed. Perhaps I should volunteer to stand in front of introductory psychology classes and feel things, or something.

My sister explains what Dead Dad Day means to her, and I explain what it means to me: a celebration of the relationship we each got to have with our father.
I guess there isn’t actually a market for Happy Dead Dad Day greetings cards?

Since my dad’s death seven years ago, I’ve marked Dead Dad Day every 19 February a way that’s definitely “mine”: with a pint or three of Guinness (which my dad enjoyed… except if there were a cheaper Irish stout on draught because he never quite shook off his working-class roots) and some outdoors and ideally a hill, although Oxfordshire makes the latter a little difficult. On the second anniversary of my dad’s death, I commemorated his love of setting out and checking the map later by making my first geohashing expedition: it seemed appropriate that even without him, I could make a journey without either of us being sure of either the route… or the destination.

Dan and his dad have breakfast in the garden.
Eating cornflakes together in the garden was a tradition of my dad and I’s since at least 23 years before this photo was taken.

As I implied at his funeral, I’ve always been far more-interested in celebrating life than mourning death (that might be why I’m not always the best at supporting those in grief). I’m not saying that it isn’t sad that he went before his time: it is. What’s worst, I think, is when I remember how close-but-not-quite he came to getting to meet his grandchildren… who’d have doubtless called him “Grandpeter”.

We all get to live, and we’re all going to die, and I’d honestly be delighted if I thought that people might remember me with the same kind of smile (and just occasionally tear) that finds my face every Dead Dad Day.

× × ×

Geohashing expedition 2019-01-08 51 -1

This checkin to geohash 2019-01-08 51 -1 reflects a geohashing expedition. See more of Dan's hash logs.

Location

A34 near Peartree Interchange, Oxford.

Participants

  • Dan Q (whose birthday it is!)

Plans

It’s my birthday on YYYY-01-08 (Birthday geohash achievement, here I come!), and even though I have to go into work (boo!), I note that my graticule’s geohashpoint falls only about a kilometre and a half of a diversion from my usual cycle route to work. The A4260 and A34 are basically a deathtrap for cyclists, so depending on conditions and traffic I’ll probably divert via the Oxford Canal towpath from Kidlington to Peartree, park up near Peartree Services, and then finish on foot. And then go to work, I guess.

Expedition

Success! A relatively easy (but sometimes scary: the traffic’s a bit nuts on some of the major roads that provided the shortest route) journey to the hashpoint area, followed by a slightly-scary crossing of the road to the hashpoint, which turned out to be right by the crash barriers at the central reservation. The crash barriers provided a great place to tie a “The Internet Was Here” sign.

On my way away from the hashpoint, at 09:19, I hid a geocache: (“2019-01-08 51 -1, 09:19”, OK049E, GC827X6). The geocache is of the “puzzle” variety – the person looking for it is likely to discover geohashing (if they haven’t already) as part of their research into the secret location of the cache.

Achievements

Birthday Achievement
Dan Q earned the Birthday Geohash Achievement
by reaching the (51, -1) geohash on his 38th birthday, 2019-01-08.

Geohashing expedition 2019-01-08 51 -1 (video)

On the morning of my 38th birthday I set out on an expedition to the geohashpoint in my graticule as a diversion from my way to work: read my full hash log for details (or on the geohashing wiki). Inspired by a spot near the hashpoint, I also hid a geocache (“2019-01-08 51 -1, 09:19”, OK049E, GC827X6). You can download my tracklog [GPX] here.

Also available on YouTube and on QTube.

Geohashing expedition 2018-11-09 51 -3

This checkin to geohash 2018-11-09 51 -3 reflects a geohashing expedition. See more of Dan's hash logs.

Location

Field near Whitefield Rocks, Langley Marsh. Google Maps says its a nowhere-place but OpenStreetMap suggests there’s a footpath right by the hashpoint.

Participants

Plans

Okay, I’m going for it! I’m driving from Oxford to Penzance this morning and having just watched the sun rise over Sedgemoor Services off the M5 I’ve determined that I’m ahead of schedule by enough that I can justify a diversion, so I’m going to try for this hashpoint as I “pass”. Typing from mobile, apologies for lack of formatting ans any spelling errors; I’ll fix them later.

Expedition

Driving from Oxford to Penzance in the world’s-smallest-rental-car isn’t a fun adventure. What is fun, though, is hitting up a graticule I’ve never hashed in before to see if I can find the day’s hashpoint while en-route.

Parking the awfulmobile in a country lane, I followed the road and then a country footpath towards the hashpoint. I say “footpath”, but the public right of way was in dire need of maintenance and the nettles and hedges were encroaching badly upon it. Which was troublesome, because the other side of the footpath was marked by an electric fence that I didn’t want to touch, and so I had to shuffle sideways-at-times through the first field. The second field was easier-going, and I got a great view of the distant storm beginning to roll in which would soak me later, as I hid adventure-game clues atop a cliff near Penzance. The third field appeared to be where the hashpoint would be, and it was crossed by the public right of way, but I was surprised to find that the electric fence returned and now barred my way. Luckily its owner had seen fit to put a length of plastic piping around the live wire so it was possible to jump over without burning my crotch, but this seemed a little not-the-done-thing regardless.

The hashpoint was right in the middle of the field and an easy find. Certainly easier than the short-but-exciting hike there and back.

Photos

Geohashing expedition 2018-10-16 52 -0

This checkin to geohash 2018-10-16 52 -0 reflects a geohashing expedition. See more of Dan's hash logs.

Location

Alongside a lane that runs through the Quinton Green Business Park, South of the village of Quinton.

Participants

Plans

I’ve got an exam in Milton Keynes in the afternoon, so it’d be only a minor diversion for me to come and try to visit this roadside hashpoint. I hope to be there about 10:30.

Expedition

Failed to turn on the tracklogger on my GPS, but I remembered to get photos at least. This was a quick and easy run, although I did get accosted by a local who saw me hanging around near the wind farm and putting up a sign… I think that after the controversy these epic windmills caused he might have thought that I was putting up a planning notice to erect some more or something. Once I explained what I was doing he seemed happy enough.

Used my new 360° full-panoramic camera to take a picture at the hashpoint; I’ll put a VR-ready version on my website and link it here when I get the chance.

Panoramic 360° VR-ready wraparound of the hashpoint

Photos

×

Geohashing near Winchester (2018-08-23 50 -1)

My original plan to divert to the 2018-08-23 51 -1 hashpoint during my planned journey North-to-South along almost the entire length of the 51 -1 graticule was ruined somewhat by the hashpoint turning out be farther North than my starting point! So I changed plans and overshot my destination in order to visit the 50 -1 hashpoint, instead (and find a couple of geocaches on the way). Here’s how that went.

Also available on YouTube and on QTube.

Geohashing expedition 2018-08-23 50 -1

This checkin to geohash 2018-08-23 50 -1 reflects a geohashing expedition. See more of Dan's hash logs.

Location

Hyden Wood, near Chidden. The woods look to be criss-crossed with footpaths, so this might be pretty achievable.

Participants

Plans

I’d originally planned on heading to 2018-08-23 51 -1 because I anticipated that it’d be on or near my route travelling South along almost the entire length of the 51 -1 graticule, but I didn’t bargain on such a Northerly hashpoint so I’ve changed plans and am now aiming to get to this one some time in the morning (I’m hoping to be in Winchester by lunch).

Expedition

The full story’s in vlog format, but here’s the summary:

  • Wasn’t originally planning to come to this graticule but instead was going to go to the 51 -1 graticule where I live ([2018-08-23 51 -1 see here]): I was going to be driving almost the entire length of 51 -1 on a journey from Oxford to Winchester anyway, so I figured it’d be easy to divert to any hashpoint. But when the Dow numbers came out, it turned out that the hashpoints in this quadrant of the Earth are all in the North-East corner, and so my journey would be in the opposite direction. Oh no! So instead I decided to “overshoot” and go for this graticule instead, and thus (if successful) expand my Minesweeper Achievement level.
  • Hashpoint deep in woodland in the beautiful South Downs National Park. Parked at The Sustainability Centre (and later made a donation via their website in thanks for the use of their car park despite not using their other facilities) and walked initially through woodland they manage and use for natural burials: this was really cool – I’ve always been a fan of body disposal in a low-environmental-impact, no-permanent-markers kind-of way, so I’m going to look more into what they offer. I was really interested to see that many families had left “named” bird nesting boxes in memory of their loved ones, which is awesome too.
  • Found geocache GC2X5BJ just outside the burial area and close to a point that gave me a great view across a valley towards the woods in which I believed I’d find the hashpoint.
  • Had to go some way off track to get to the hashpoint, but discovered a network of old, overgrown, long-abandoned (and not on any map I can find) trails in-between the thicket. In fact, the hashpoint eventually turned out to be on the edge of such a track, which I was able to follow to help me find my way back to a road.
  • Found a sign pointing to “Droxford”. Oxford is so-named because its location coincides with the most-downstream point on the Thames at which it’s possible to ford the river while driving cattle (i.e. “ox ford”) – incidentally, I’m told, the ford was at the point that Folly Bridge now stands. But what’s the etymology of Droxford, I wonder. What the hell is a drox???
  • On the way back, diverted by geocache GC5P5KN and found it: this was a great cache with the best-made variant of the particular kind of container it used that I’ve ever seen.

Update: A little research later, it seems that the “ox” in each of Oxford and Droxford have completely different etymological roots! Droxford is derived from an ancient name for the area from some time prior to the Middle Ages: Drocenesforda. “Drocen” means “dry”: the name means “dry ford”. The River Meon, which flows through the area, flows shallow over a chalky bed and is easily forded in many places, as these motorcyclists show. The things you learn!

Tracklog

Video

Photos

Geohashing expedition 2018-08-22 52 -1

This checkin to geohash 2018-08-22 52 -1 reflects a geohashing expedition. See more of Dan's hash logs.

Location

Field with public footpath, East Adderbury.

Participants

Plans

I’m keen to get to level 2 of the Minesweeper Geohash achievement, and this far-South-of-graticule hashpoint represents an opportunity to achieve that. I’ll be at work during the day, but – energy levels permitting after what’ll have been a long day! – I’ll find a way to get up here and see if I can get to the hashpoint, aiming to arrive probably around 18:30.

Expedition

It had been a long day at work, but it looked to be a beautiful evening and I promised myself a pub dinner if I made it to the hashpoint, so I set out by car and by foot to East Adderbury, the village nearest to the hashpoint. The village itself is stunning: lots of old stone buildings, a very traditional bridge, and beautiful green spaces. I spotted not one but two candidate pubs (The Red Lion and The Coach & Horses) as I passed through the village, which was a reassuring start, and then pressed on down a lane which quickly became a narrow trail, waving to some cows along the way (why do I always seem to meet cattle on my hashing adventures?).

The trail was full of blackberries so I wasn’t short of a snack, but it soon became clear that it wouldn’t get me any closer than 35m to the hashpoint. I returned to the entrance to the cows’ field and, hopping a stile, crossed it. The cows looked puzzled as I paced around, getting to ground zero, but didn’t object. After shooting the traditional silly grin, I turned tail and headed back into the village and to the Coach & Horses, which proved to be the very essence of a British village pub: a husband and wife couple running it, dogs everywhere, a jar of pickled onions behind the bar, and more beers than you can shake a stick at.

I did enjoy a rather unusual conversation at the bar, though –

 Me: Can I get a ham, egg, and chips please. And a pint of bitter shandy.
 Barman: One egg or two?
 Me: Oh! Two, please.
 Barman: (Pause) We haven't got any eggs.
 Me: Uhh. Okay; no eggs then.
 Barman's wife: We've got one egg.
 Barman: We've got one egg.
 Me: I'll have one egg, then.
 
 (I go and sit outside; after a while, my meal arrives. There are two eggs.)
 
 Barman's wife: I found another egg.
 Me: ...

A fuller description of the entire adventure can found in the vlog I made along the way.

Tracklog

Video

I filmed my adventure in a vloggy format, complete with doubling-back, talking to cows, and anecdotes about pub food. Watch it on YouTube or on QTube.

Photos

Achievements

Minesweeper geohash empty.png Minesweeper geohash flag.png Minesweeper geohash empty.png
Minesweeper geohash empty.png Minesweeper geohash 2.png Minesweeper geohash flag.png
Minesweeper geohash empty.png Minesweeper geohash empty.png Minesweeper geohash empty.png
Dan Q achieved level 2 of the Minesweeper Geohash achievement
by visiting coordinates in Swindon, United Kingdom and 2 of the surrounding graticules.

How Much of My Graticule is Covered With Water?

I’m a moderately-keen geohasher, as you might be aware if you follow my geohashing logs or you saw that video of me going ‘hashing earlier this month.

For those that don’t know, the skinny version is this: in May 2008 an XKCD comic was published proposing (or at least joking about) a new game with a name reminiscient of geocaching. To play the game, participants use a mathematical hashing function on the current date and the most recent Dow Jones Industrial Average opening value to generate sets of random coordinates around the globe and then try to find their way to them, hopefully experiencing adventures along the way. The nature of stock markets and hashing functions means that the coordinates for any given day are effectively random and impossible to predict (far) in advance, so it’s sometimes described as a spontaneous adventure generator.

XKCD comic #426, "Geohashing"
The XKCD comic that started it all.

Recently, I found myself wondering about how much of a disadvantage players are at if they live in very “wet” graticules. Residents of the Channel Islands graticule (49 -2), for example, are confined to two land masses surrounded entirely by water. And while it’s true that water hashpoints can be visited if you’re determined enough, it’s still got to be considered to be playing at a disadvantage compared to those of us lucky ones in landlocked graticules like mine (51 -1).

And because I’m me and so can’t comfortably leave a question unanswered, I wrote a program to try to answer it! It’s among the hackiest, dirtiest software solutions I’ve ever written, so if it works for you then it’s a flipping miracle. What it does is:

  1. Determines which OpenStreetMap tiles (the image files served to your browser when you use OpenStreetMap) cover the graticule in question, and downloads them.
  2. Extracts information about the colour of each pixel in each tile.
  3. Counts the proportion of “water blue” pixels to other pixels (this isn’t perfect, because it trips over things like ferry lines on the map as being “not water”, especially at low zoom-levels).
Extreme zoom-in on Worcester College Lake, on OpenStreetMap.
Some parts of Worcester College Lake are identified as “not water” on account of the text overlay.

I mentioned it was hacky, right?

You can try it for yourself, if you’d like. You’ll need NodeJS, wget, wc, and ImageMagick – all pretty standard or easy-to-get things on a typical Linux box. Run with node geohash-pcwater.js 51 -1, where 51 -1 is the identifier for the graticule you’re interested in. And in case you’re interested – the Swindon graticule (where I live) is about 0.68% water, but the Channel Islands graticule is closer to 93.13% water. That’s no small disadvantage: sorry, Channel Islands geohashers!

Update 2018-08-22: discovered some prior art that takes a somewhat-similar approach.

×

Geohashing expedition 2018-08-07 51 -1

This checkin to geohash 2018-08-07 51 -1 reflects a geohashing expedition. See more of Dan's hash logs.

Location

A field South of Oxford

Participants

Plans

My meeting this afternoon got cancelled and my nearest hashpoint is only 6.5km (4 miles) away from my office. I can get this!

Expedition

After a productive morning’s work, I was genuinely slightly disappointed that a meeting I was scheduled to have this afternoon had to be rescheduled. But on the other hand… that meant that I could get away with extending my lunch break slightly and getting out to the hashpoint! I’d initially worried that it’d be inaccessibly buried on private land when Google Maps and satellite photography showed it to be deep in a block of cornfields, but OpenStreetMap came to the rescue and showed a public footpath somewhere in the very close vicinity of the target coordinates. And so, jumping aboard my bike, I set out!

600m from the coordinates I ran out of road and switched to the footpath, which I was pleased to discover was in reasonably-good condition: many underused local footpaths are not being very well-maintained at the moment and are often overgrown, but I was even able to bring my bike along this one and into the first field, although I had to push it rather than ride and I soon learned the error of my ways when the terrain got even rougher and I reached a narrow bridge – too narrow for my bike – spanning a dyke and entering the second field. Both fields had recently been cleared of corn, and whatever route the official footpath was supposed to take became rapidly unclear, but that’s probably for the best because I’m pretty sure I wasn’t on it by the time I reached the edge of the next field.

The hashpoint seemed to be along the fence somewhere so I followed it along – waving to some nearby cows – until my phone told me that I was under 3m from the spot. Hurrah! I snapped a panorama photo and started heading back, pausing a few times when I realised that I really, really couldn’t find where I’d left my bike. On the cycle home I passed a Gasometer which, because I’m told they’re super-rare in the USA, I thought I’d snap a picture of for those of you who ‘hash on the other side of the pond to oggle at.

Video

I actually remembered to shoot video of this expedition (well, all within a kilometre of the hashpoint and mostly within the last 350 metres!). It’s mostly just me rambling as I ramble, although there’s (brief) explanation of the Surprise Gasometer for those of you who live in countries where you don’t routinely see these interesting structures:

Photos

Geohashing expedition 2018-08-04 51 -1

This checkin to geohash 2018-08-04 51 -1 reflects a geohashing expedition. See more of Dan's hash logs.

Location

Looks to be deep in the bushes alongside the unnamed road that connects Kidlington Road (to Islip), the sliproad exiting the A34 Southbound, and Bicester Road (in Kidlington).

Participants

Plans

The nearest road is about 10 minutes cycle from my (Dan Q) house, so I plan to zip out there either overnight (perhaps aiming for a Midnight Geohash?) or early in the morning. If you happen to plan to hit this hashpoint too, though, let me know and I can try to synchronise plans (but I ought to be spending the day studying, so I might not be able to!).

Expedition

At 2018-08-03 23:02 (BST – local time) I started packing a bag and set out to the hashpoint. Suddenly it didn’t seem like such a good idea as it had in the warm sunlight, earlier: a dark and moonless night isn’t the best time to be cycling along unlit roads. But fully-equipped with lights and supplies, I set out nonetheless. I’d left longer than I needed and had about a quarter of an hour sitting by the side of the road before midnight came and I was able to visit the hashpoint (thereby gaining my Midnight Achievement).

Photos

Geohashing expedition 2014-07-12 51 -0

This checkin to geohash 2014-07-12 51 -0 reflects a geohashing expedition. See more of Dan's hash logs.

Location

On the edge of a field near the village of Ford, outside Aylesbury.

Participants

Plans

I’m out in Aylesbury today, so I’ll probably swing by the hashpoint late-morning/early afternoon, by car. Hopefully it’s possible to get to it without climbing through any hedges!

Expedition

Geohashpoint 2014-07-12 51 -0I was in Aylesbury this morning for an interview, and I’d discovered last night that a hashpoint had appeared pretty-much right between my home and the place I was visiting. It was off the major roads by a little way, but the day was beautiful and I relished the opportunity to go for an explore, by ZipCar and on foot. And that’s exactly what I got.

After driving through the village of Ford, I came to the end of a road and the beginning of a private driveway, and found a place to park. The locals looked at me strangely as I found my bearings and set off up a bridleway. Suddenly, I realised that the hashpoint was off to my right somewhere, so I hacked my way through some trees to get closer to it. The hashpoint turned out to be pretty-much exactly on the spot of a tree, at the edge of a field. Sadly, the tree was on the otherside of a barbed wire fence, covered in vines, but I was (with some effort) able to lean far over to “touch” the hashpoint-tree, as shown in the photos.

Later, I got stuck in traffic and almost delivered the ZipCar back late, but just barely made it, vacating the car just as the (very prompt) next occupiers turned up. Phew!

Photos

Dan Q found GLE5095Y Pointless Pathway

This checkin to GLE5095Y Pointless Pathway reflects a geocaching.com log entry. See more of Dan's cache logs.

What a wonderful little secret place buried away so close to civilization. Funny: I cycled right past the end of this pathway on my first ever geoHASHING expedition, almost three months ago, and never thought to look for caches on my way. It’s only now, having arrived earlier than expected for a medical appointment, that I got to come find this cache.

Log’s plastic bag is torn; log beginning to get damp.

TFTC!