2013-08-05 44 -110

From Geohashing
Mon 5 Aug 2013 in 44,-110:
44.6693250, -110.9701443
geohashing.info google osm bing/os kml crox


Near the West Entrance of Yellowstone National Park.



I started the day in Idaho Falls, scanning the hashpoints for inspiration, and the hashpoints said "GO NORTH!!!"

After a little knocking around in Northeastern Idaho, I crossed into Montana and then in the West Entrance to Yellowstone National Park. This required an entrance fee (Figure 1). The woman at the entrance booth had a long speech that she must give a thousand times a day about how my receipt would allow re-entrance for a week, yadda yadda yadda, and made to hand me a thick stack of park publications. "I don't really need any materials," I said. "I'm only going in for an hour or so." She pulled them back with an air of thinking that this was REALLY WEIRD and probably wrong, but not worth arguing over.

Now, the hashpoint was on the north bank of the Madison River, and I knew that near the entrance the Madison has a gently sloping, lightly forested bank (Figure 2). What I didn't know was that closer to the bridge that was my access to the north bank, the bank gets steeper. Much, much steeper. It is, in fact, about a 40 degree slope of loose scree, capped by a formidable stone palisade (Figure 3).

I was getting nervous, and warnings regarding unfamiliar bears didn't help (Figure 4). But, there was a nice little trail heading in the right direction... (Figure 5)

What followed was an object lesson in pursuing geohashing for the journey, not the destination. The trail only got me within 400 feet of the hashpoint, which was clearly up on top of the canyon. But, I thought I saw a break in the palisade, and decided to give climbing up the wall a shot.

Friends, climbing up a steep scree slope is kind of dumb, unless you are darn sure you can get back down. And the stupid thing I did was reach three separate decision points where I wasn't 100% confident I'd be able to get back down, and kept going up. It was only when I got to the palisade, and my fourth decision point, that I started to think things like "I could be out here with a broken leg for a hella long time with nobody noticing" and "For that matter, no one on the planet has the slightest idea where I am" and "Golly, Mrs.5000 sure would be glum if I copped it" and even "If I had to be airlifted out, it would be some nasty publicity for the Geohashing community."

In truth, I probably could have made it the rest of the way up, claimed the point, and handled the descent. But only probably. And, I'm not surprised I made it down without consequences, although it was tricky business and scary as hell. I could probably make that descent without consequences 99 times out of 100. But the 1 out of 100 would really take the fun out the enterprise. So I've resolved to, from here on out, take pride in my thwarted expeditions. After all, an expedition is only thwarted because I'm respecting somebody's fence, or because I'm smart enough not to push my luck in adverse conditions. From now on, my goal is to stay smart, and always come home.

After a short rest stop to get my blood pressure back to normal, I continued on to the gentler terrain of 2013-08-05 45 -110.



  • First ever attempt on the Yellowstone, Wyoming graticule. All those people having boring normal vacations....
by paying US$25.00 to access the (44, -110) geohash at Yellowstone National Park on 2013-08-05.
2013-08-05 44 -110 1.JPG
MNB Ribbon.jpg
Michael5000 earned the "Mother Nature's Bitch" Consolation Prize
by failing to reach the (44, -110) geohash on 2013-08-05.