2019-06-28 43 -122

Fri 28 Jun 2019 in 43,-122: 43.9619016, -122.6771085 geohashing.info google osm bing/os kml crox

Location

In the woods near Fall Creek Lake, northeast of Lowell.

Participants

• Michael5000 -- Expedition #218

Expedition

In 1828, Jedediah Smith led an expedition north from Mission San Jose, in the California territory of Mexico, in hopes of finding an overland route to Fort Vancouver, on the Columbia near Portland would eventually be built. Daunted by the Siskiyou Mountains to the north of the Sacramento Valley, he decided to make for the coast, where the beaches might make travel a little easier. After a grueling crossing of the Coast Range, the party reached the Klamath River and shortly afterwards celebrated when they caught climbed a hill and saw that they were in sight of the ocean. But between the terrain and the thick rainforest vegetation, it would take them 16 more days to get to the beach.

Sixteen. More. Days.

Well, that's what our forests can be like in the rainy parts of the Northwest. Especially in areas where trees have been felled by recent storms -- in the last dozen years, say -- the vegetation can be almost too thick to move through. Also, the footing can be really treacherous, and places that look like forest floor can actually be just a thin layer of soil trapped between two logs, or something that looks like a nice sturdy log actually can be so rotten that your leg will go right through it. If you then throw in the tough, thorny Himalayan blackberry bushes that have made themselves at home in most western Oregon forests -- and ol' Jed Smith didn't have to deal with those -- it can be really hard to get to your hashpoint.

Nor did Jedediah suffer the way I do with a GPS in this kind of environment. The problem is that since you can only go a few halting steps at a time, your GPS doesn't have the continuous movement it needs to project your distance of travel. So, you know how far you are from the hashpoint, but you don't get reliable feedback about what direction it's in. And then, if you're in a gully under a thick forest canopy, the signal gets poor enough that even a good GPS unit loses some of its resolution.

So anyway, if I'd known it was going to be this kind of environment, I wouldn't have driven 107 miles to get there, but having driven 107 miles to get there, I was under a certain amount of pressure to complete the expedition. From where I parked the car, 150 feet from the hashpoint -- that's about 50 meters -- I first tried walking down the road a bit and approaching from the east to avoid a steep slope. That approach soon bogged down in briars and fallen logs, so I went back to the car and tried again, coming in steeply downhill from the northwest. It wasn't pretty, and it wasn't much fun, but I eventually made it down to a point where it seemed that I could cross over the creek on a log and be right at the hashpoint, or possibly fall off the log down into the creekbed, break both legs, and die horribly, alone in the woods with no one to hear my gradually weakening screams.

As I contemplated this risk management scenario, I happened to notice that the app on my phone was congratulating me on reaching the hashpoint. Then I noticed that my GPS was telling me that I was four feet from the hashpoint. Excitedly, I waved it around, and it said I was two feet from the hashpoint. And, as I spun around, it gave me distances from two to 22 feet. Well, that would be the poor signal under the forest canopy, I guess.

Since this was a new graticule for me, I do wish it had been a slightly "cleaner" win, the kind where your GPS gets to zero and you can tell that you're standing on the same manhole cover you say on the satellite image. But despite that, I feel like I've got a good data-supported success out of this one.

On the way out, once I'd climbed most of the way back up the slope, I stopped for breath and leaned against a tree maybe 8 inches in diameter. That's what, more than 20 centimeters. It was completely rotted through, and immediately collapsed the the forest floor with a resounding crash. I was glad to get back to the road.

Photos

• 

  Getting to this point was well over 99% of the distance, but that part went pretty smoothly.

• 

  And getting to THIS point was over 99% of the remaining distance, and that part, too, was still pretty chill.

• 

  Uh-oh.

• 

  This is the view up towards where the car was parked, from the hashpoint.

• 

  Sweaty and dirty, but undaunted.

Achievements

This was my first-ever expedition to the Oakridge, Oregon graticule.

Since Oakridge was a "donut hole" on my graticule map, this expedition causes a real flurry on the Minesweeper front.

Michael5000 completed the Minesweeper Geohash achievement by visiting coordinates in [[Oakridge, Oregon]] and all of the surrounding graticules.

Michael5000 completed the Minesweeper Geohash achievement by visiting coordinates in [[Bend, Oregon]] and all of the surrounding graticules.

Michael5000 completed the Minesweeper Geohash achievement by visiting coordinates in [[La Pine, Oregon]] and all of the surrounding graticules.

Michael5000 completed the Minesweeper Geohash achievement by visiting coordinates in [[Springfield, Oregon]] and all of the surrounding graticules.

Michael5000 achieved level 7 of the Minesweeper Geohash achievement by visiting coordinates in [[Eugene, Oregon]] and 7 of the surrounding graticules.

Michael5000 achieved level 7 of the Minesweeper Geohash achievement by visiting coordinates in [[Roseburg, Oregon]] and 7 of the surrounding graticules.

Michael5000 achieved level 5 of the Minesweeper Geohash achievement by visiting coordinates in [[Grants Pass, Oregon]] and 5 of the surrounding graticules.

Michael5000 achieved level 5 of the Minesweeper Geohash achievement by visiting coordinates in [[Medford, Oregon]] and 5 of the surrounding graticules.

Michael5000 achieved level 5 of the Minesweeper Geohash achievement by visiting coordinates in [[Klamath Falls, Oregon]] and 5 of the surrounding graticules.