Difference between revisions of "2013-05-27 48 -115"

From Geohashing
imported>Vaiman
m (Expedition)
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
<!-- If you did not specify these parameters in the template, please substitute appropriate values for IMAGE, LAT, LON, and DATE (YYYY-MM-DD format)
 
 
[[Image:{{{image|IMAGE}}}|thumb|left]]
 
 
Remove this section if you don't want an image at the top (left) of your report.  You should remove the "Image:" or "File:"
 
tag from your image file name, and replace the all upper-case word IMAGE in the above line.
 
 
And DON'T FORGET to add your expedition and the best photo you took to the gallery on the Main Page! We'd love to read your report, but that means we first have to discover it! :)
 
-->
 
 
{{meetup graticule  
 
{{meetup graticule  
 
| lat=48
 
| lat=48
Line 15: Line 5:
 
}}
 
}}
  
<!-- edit as necessary -->
 
 
__NOTOC__
 
__NOTOC__
 
== Location ==
 
== Location ==
The hash for this graticule was determined to be midway up a mountain slope adjacent to the East Fork of the Yaak River.
+
Midway up a mountain slope adjacent to the East Fork of the Yaak River.
  
 
== Participants ==
 
== Participants ==
Line 24: Line 13:
  
 
== Plans ==
 
== Plans ==
#Take Yaak 92 (NF-92) through the depths of banjo territory to the trailhead
+
#Take Yaak 92 (NF-92) to the trailhead
 
#Follow trail until a point on the opposite ridge of the has is reached
 
#Follow trail until a point on the opposite ridge of the has is reached
 
#Bushwhack across steep terrain covered in medium density forest (with at least a single water-crossing) until hash is accomplished
 
#Bushwhack across steep terrain covered in medium density forest (with at least a single water-crossing) until hash is accomplished
Line 30: Line 19:
  
 
== Expedition ==
 
== Expedition ==
After randomly being given an old GPS receiver last week, I was finally able to embark on my first geohashing excursion. With the advent of the Memorial Day holiday, all excuses were off. After consulting my spreads and topos, the hash coordinates were determined to be in a most opportune location. One must understand, the majority of hashes in my graticule are, quite literally, in the middle of nowhere. While I have no qualms with trekking more miles than I have fingers through mostly inhospitable, people devouring terrain...I figured this would make an easy first hash. The hash fell on a the opposite side of the drainage paralleled by an old-national-forest-road-turned-hiking-trail.
+
Having been randomly given an old GPS receiver last week, I was finally able to embark on my first geohashing excursion. With the advent of the Memorial Day holiday, all excuses were off. After consulting my spreads and topos, the hash coordinates were determined to be in a most opportune location. One must understand, the majority of hashes in my graticule are, quite literally, in the middle of nowhere. While I have no qualms with trekking more miles than is sane through mostly inhospitable, people devouring terrain...I figured this would make an easy first hash. The hash fell on a the opposite side of the drainage paralleled by an old-national-forest-road-turned-hiking-trail.
  
 
A leisurely morning and a quick pack later, I was on the road toward the trailhead. The paved portion of this journey took me through deep banjo territory and well into Grizzly Bear habitat. I feel it is worth noting, at this point, when planning to hike or geohash in Grizzly Bear country (basically my entire graticule) one should bring at least two of the following items: a large handgun, bear spray, or a slow companion.
 
A leisurely morning and a quick pack later, I was on the road toward the trailhead. The paved portion of this journey took me through deep banjo territory and well into Grizzly Bear habitat. I feel it is worth noting, at this point, when planning to hike or geohash in Grizzly Bear country (basically my entire graticule) one should bring at least two of the following items: a large handgun, bear spray, or a slow companion.
Line 36: Line 25:
 
Once the trailhead was attained, a quick survey of the area was made. There was a small campsite complete with hitching post nearby. A quick snapshot of the trail sign was snapped before the pack was donned and the real adventure commenced. Though it had been raining intermittently all morning, I left the umbrella within the conveyance since it would be dangerous (though comical) to traverse beyond the trail while wielding a GPS in one hand and umbrella in the other.
 
Once the trailhead was attained, a quick survey of the area was made. There was a small campsite complete with hitching post nearby. A quick snapshot of the trail sign was snapped before the pack was donned and the real adventure commenced. Though it had been raining intermittently all morning, I left the umbrella within the conveyance since it would be dangerous (though comical) to traverse beyond the trail while wielding a GPS in one hand and umbrella in the other.
  
The trail itself was leisurely, with two water crossings; Bridge Creek and Lime Creek, according to my maps. Along the way, I picked up a small white rock (as yet unidentified, likely a type of Quartz) as a trinket from the hash journey. Before I knew it, the GPS indicated I was opposite the river from the hash point. It was time to get serious. As rain began to fall once again, I stepped off the trail into the unknown, descending about one-hundred feet in elevation to the water. This was when my trouble began. The density of the tree cover combined with moving downward into the valley was playing tricks on my receiver. A few small breaks in overhead tree cover allowed brief directional indication until I reached the East Fork. Once there, I lost all satellites except for those directly overhead--and only when I was hanging over the water. Three sat locks are useless when they happen to be directly above you. At this point, I began wandering along both sides of the river, crossing more times than I ever would have cared for, trying to get a lock on one satellite closer to the horizon so I could get a quick bearing. It was then my receiver decided to do magic and calculate my position using two sats directly overhead--accuracy 400+ feet. In addition to this, I made sure to crash through every gigantic spider web along the way. Yelling at satellite #10, I peeled web and arachnids from my body as I made my way back toward the trail to get a better signal.
+
The trail itself was easy, with two water crossings; Bridge Creek and Lime Creek, according to my maps. Along the way, I picked up a small white rock (as yet unidentified, likely a type of Quartz) as a trinket from the hash journey. Before I knew it, the GPS indicated I was opposite the river from the hash point. It was time to get serious. As rain began to fall once again, I stepped off the trail into the unknown, descending about one-hundred feet in elevation to the water. This was when my trouble began. The density of the tree cover combined with moving downward into the valley was playing tricks on my receiver. A few small breaks in overhead tree cover allowed brief directional indication until I reached the East Fork. Once there, I lost all satellites except for those directly overhead--and only when I was hanging over the water. Three sat locks are useless when they happen to be directly above you. At this point, I began wandering along both sides of the river, crossing more times than I ever would have cated for, trying to get a lock on one satellite closer to the horizon so I could get a quick bearing. It was then my receiver decided to do magic and calculate my position using two sats directly overhead--accuracy 400+ feet. In addition to this, I made sure to crash through every gigantic spider web along the way. Yelling at satellite #10, I peeled web and arachnids from my body as I made my way back toward the trail to get a better signal.
  
 
Satellite #10 must have heard me, because shortly thereafter I was able to get a fix on my location. Bearing rediscovered, I ran through trees, bushes and more spiders until I was at the same place I first met the river. After a brief pause to appreciate the irony of the situation, I continued eastward and crossed again. With the general area of the point in sight, I raced up the slope until I was within 18 feet. Slowly fanning around, I was able to get to 0.00 feet (~30ft accuracy) before the signal was lost and the unit became confused again. The display now reading that I was twenty feet off, I did a few circles before declaring the tree next to me as ##130527+48,-115.
 
Satellite #10 must have heard me, because shortly thereafter I was able to get a fix on my location. Bearing rediscovered, I ran through trees, bushes and more spiders until I was at the same place I first met the river. After a brief pause to appreciate the irony of the situation, I continued eastward and crossed again. With the general area of the point in sight, I raced up the slope until I was within 18 feet. Slowly fanning around, I was able to get to 0.00 feet (~30ft accuracy) before the signal was lost and the unit became confused again. The display now reading that I was twenty feet off, I did a few circles before declaring the tree next to me as ##130527+48,-115.
Line 44: Line 33:
 
Difficulty Rating 2/5
 
Difficulty Rating 2/5
 
Annoyance Rating 3/5
 
Annoyance Rating 3/5
 
+
Percentage of clothing soaked by rain ~75%
== Tracklog ==
 
<!-- if your GPS device keeps a log, you may post a link here -->
 
  
 
== Photos ==  
 
== Photos ==  
<!-- Insert pictures between the gallery tags using the following format:
 
Image:2012-##-## ## ## Alpha.jpg | Witty Comment
 
-->
 
 
<gallery perrow="5">
 
<gallery perrow="5">
 +
Image:130527-20.jpg | The sign at the trailhead.
 +
Image:130527-21.jpg | Hitching post at the trailhead.
 +
Image:130527-11.jpg | East Fork of Yaak River; crossed it more times than I have fingers.
 +
Image:130527-12.jpg | Fighting with satellites.
 +
Image:130527-19.jpg | Tree at hash point.
 +
Image:130527-18.jpg | Blurry confirmation shot of confused GPS.
 
</gallery>
 
</gallery>
  
== Achievements ==
 
{{#vardefine:ribbonwidth|800px}}
 
<!-- Add any achievement ribbons you earned below, or remove this section -->
 
 
 
<!-- =============== USEFUL CATEGORIES FOLLOW ================
 
Delete the next line ONLY if you have chosen the appropriate categories below. If you are unsure, don't worry. People will read your report and help you with the classification. -->
 
[[Category:New report]]
 
 
<!-- Potential categories. Please include all the ones appropriate to your expedition -->
 
<!-- If this is a planning page:
 
[[Category:Expedition planning]]
 
-->
 
 
<!-- An actual expedition:
 
 
[[Category:Expeditions]]
 
[[Category:Expeditions]]
-- and one or more of --
 
 
[[Category:Expeditions with photos]]
 
[[Category:Expeditions with photos]]
[[Category:Expeditions with videos]]
 
[[Category:Expedition without GPS]]
 
-->
 
 
<!-- if you reached your coords:
 
 
[[Category:Coordinates reached]]
 
[[Category:Coordinates reached]]
  
 
+
== Achievements ==
--><!-- or if you failed :(
+
{{#vardefine:ribbonwidth|800px}}
[[Category:Coordinates not reached]]
+
<!-- Add any achievement ribbons you earned below, or remove this section -->
-- and a reason --
+
{{land geohash
When there is a natural obstacle between you and the target:
+
| latitude = 48
[[Category:Not reached - Mother Nature]]
+
| longitude = -115
 
+
| date = 2013-05-27
When there is a man-made obstacle between you and the target:
+
| name = vaiman
[[Category:Not reached - No public access]]
+
}}
 
+
{{Graticule unlocked
When you failed get your GPS, car, bike or such to work:
+
| latitude = 48
[[Category:Not reached - Technology]]
+
| longitude = -115
   
+
| date = 2013-05-27
When you went to an alternate location, or decided early on to abort the expedition:
+
| name = vaiman
[[Category:Not reached - Did not attempt]]
+
}}
 
+
{{location|US|MT|LN}}
(Don't forget to delete this final close comment marker) -->
 

Latest revision as of 05:24, 20 March 2024

Mon 27 May 2013 in 48,-115:
48.9264759, -115.4123964
geohashing.info google osm bing/os kml crox


Location

Midway up a mountain slope adjacent to the East Fork of the Yaak River.

Participants

Vaiman

Plans

  1. Take Yaak 92 (NF-92) to the trailhead
  2. Follow trail until a point on the opposite ridge of the has is reached
  3. Bushwhack across steep terrain covered in medium density forest (with at least a single water-crossing) until hash is accomplished
  4. Complete previous steps in reverse order

Expedition

Having been randomly given an old GPS receiver last week, I was finally able to embark on my first geohashing excursion. With the advent of the Memorial Day holiday, all excuses were off. After consulting my spreads and topos, the hash coordinates were determined to be in a most opportune location. One must understand, the majority of hashes in my graticule are, quite literally, in the middle of nowhere. While I have no qualms with trekking more miles than is sane through mostly inhospitable, people devouring terrain...I figured this would make an easy first hash. The hash fell on a the opposite side of the drainage paralleled by an old-national-forest-road-turned-hiking-trail.

A leisurely morning and a quick pack later, I was on the road toward the trailhead. The paved portion of this journey took me through deep banjo territory and well into Grizzly Bear habitat. I feel it is worth noting, at this point, when planning to hike or geohash in Grizzly Bear country (basically my entire graticule) one should bring at least two of the following items: a large handgun, bear spray, or a slow companion.

Once the trailhead was attained, a quick survey of the area was made. There was a small campsite complete with hitching post nearby. A quick snapshot of the trail sign was snapped before the pack was donned and the real adventure commenced. Though it had been raining intermittently all morning, I left the umbrella within the conveyance since it would be dangerous (though comical) to traverse beyond the trail while wielding a GPS in one hand and umbrella in the other.

The trail itself was easy, with two water crossings; Bridge Creek and Lime Creek, according to my maps. Along the way, I picked up a small white rock (as yet unidentified, likely a type of Quartz) as a trinket from the hash journey. Before I knew it, the GPS indicated I was opposite the river from the hash point. It was time to get serious. As rain began to fall once again, I stepped off the trail into the unknown, descending about one-hundred feet in elevation to the water. This was when my trouble began. The density of the tree cover combined with moving downward into the valley was playing tricks on my receiver. A few small breaks in overhead tree cover allowed brief directional indication until I reached the East Fork. Once there, I lost all satellites except for those directly overhead--and only when I was hanging over the water. Three sat locks are useless when they happen to be directly above you. At this point, I began wandering along both sides of the river, crossing more times than I ever would have cated for, trying to get a lock on one satellite closer to the horizon so I could get a quick bearing. It was then my receiver decided to do magic and calculate my position using two sats directly overhead--accuracy 400+ feet. In addition to this, I made sure to crash through every gigantic spider web along the way. Yelling at satellite #10, I peeled web and arachnids from my body as I made my way back toward the trail to get a better signal.

Satellite #10 must have heard me, because shortly thereafter I was able to get a fix on my location. Bearing rediscovered, I ran through trees, bushes and more spiders until I was at the same place I first met the river. After a brief pause to appreciate the irony of the situation, I continued eastward and crossed again. With the general area of the point in sight, I raced up the slope until I was within 18 feet. Slowly fanning around, I was able to get to 0.00 feet (~30ft accuracy) before the signal was lost and the unit became confused again. The display now reading that I was twenty feet off, I did a few circles before declaring the tree next to me as ##130527+48,-115.

Since it was pouring rain by this time, I did not unpack my main camera body and tripod for a goofy photo. Instead, I opted to take a blurry screen photo of the GPS before heading back.

Difficulty Rating 2/5 Annoyance Rating 3/5 Percentage of clothing soaked by rain ~75%

Photos

Achievements

Landgeohash.png
vaiman earned the Land geohash achievement
by reaching the (48, -115) geohash on 2013-05-27.
Graticule unlocked.png
vaiman earned the Graticule Unlocked Achievement
by being the first to reach any hashpoint in the (48, -115) graticule, here, on 2013-05-27.