Difference between revisions of "2010-10-29 45 -122"

From Geohashing
imported>Jiml
(Massively thwarted expedition report)
 
imported>FippeBot
m (Location)
 
(2 intermediate revisions by one other user 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=45
 
| lat=45
Line 15: Line 5:
 
}}
 
}}
  
<!-- edit as necessary -->
+
 
 
__NOTOC__
 
__NOTOC__
 
== Location ==
 
== Location ==
<!-- where you've surveyed the hash to be -->
+
Near Hwy 500 east of Mill Plain, Washington
  
 
== Participants ==
 
== Participants ==
<!-- who attended -->
+
* [[User:Jiml|Jim]]
  
 
== Plans ==
 
== Plans ==
<!-- what were the original plans -->
+
Print a Google Map, program a GPS, run a quick errand.  Head
 +
out to the hashpoint, which was probably on private land.
  
 
== Expedition ==
 
== Expedition ==
<!-- how it all turned out. your narrative goes here. -->
 
  
== Tracklog ==
+
The template asks:  How did it all turn out?  Answer: Very badly.
<!-- if your GPS device keeps a log, you may post a link here -->
 
  
== Photos ==
+
This was one of those expeditions that really didn't seem to
<!-- Insert pictures between the gallery tags using the following format:
+
really have
Image:2010-##-## ## ## Alpha.jpg | Witty Comment
+
a chance.
-->
 
<gallery perrow="5">
 
</gallery>
 
  
== Achievements ==
+
I started by printing out the Google maps page with directions.
{{#vardefine:ribbonwidth|800px}}
+
I grabbed it and headed out the door, planning on programming the GPS on the way.
<!-- Add any achievement ribbons you earned below, or remove this section -->
 
  
 +
I got out the door when I noticed that for some reason Google Maps has
 +
stopped printing out the coordinates as the destination when you
 +
print out directions as well.  So I ran back and quickly popped up
 +
the Peeron page and told it to print.  I stuffed it into my bag
 +
and headed out to the car.  On the way, I attempted to get the
 +
coordinates on my organizer as a backup.
 +
It reported that it had no battery left.  It charges via the USB
 +
connection, so I couldn't just change the batteries. 
 +
 +
"No problem", I think.  "I've
 +
got the coordinates on the Peeron page.  I'll go with them."
 +
 +
I get to my quick errand and go to program the GPS before I hit
 +
the road.  Oops.  The printout of the Peeron page doesn't include
 +
the box in the lower right!
 +
 +
Okay - I've got a final fallback.  The browser on my cellphone will
 +
show me the coordinates if I hit the right page, which is painful,
 +
but possible.
 +
Except the browser won't show me any pages, let alone one
 +
with hashpoint data.  Apparently a recent power
 +
outage has broken things.  More work for me to do the next day.
 +
 +
Finally, I call APR and ask him to text me the coordinates.  Which
 +
he does.  Now I can put them into the GPS...the one with the low
 +
batteries...which die before I finish entering the coordinates.
 +
Luckily there are spare batteries in the camera case.
 +
 +
We hit the road...For a little while...Until I hit traffic.  And I
 +
wait, and move a little, and wait, and move a little.  And wait.
 +
 +
Finally, I realize that I've burned up so much time that
 +
at this rate I won't
 +
make it there and back close to in time for dinner.  I give up and
 +
take the next exit to head home, leaving the hashpoint for some future retro
 +
expedition, perhaps when we go to visit the very first geohashing expedition ever,
 +
which happens to be in that direction.
  
<!-- =============== 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:Coordinates not reached]]
[[Category:Expeditions with photos]]
 
[[Category:Expeditions with videos]]
 
[[Category:Expedition without GPS]]
 
-->
 
 
<!-- if you reached your coords:
 
[[Category:Coordinates reached]]
 
-->
 
  
<!-- or if you failed :(
+
[[Category:Not reached - Technology]]
[[Category:Coordinates not reached]]
+
[[Category:Not reached - Time constraints]]
-- and a reason --
+
{{location|US|WA|CR}}
[[Category:Not reached - Mother Nature]]    when there is a natural obstacle between you and the target
 
[[Category:Not reached - No public access]] when there is a man-made obstacle between you and the target
 
[[Category:Not reached - Technology]]       when you failed get your GPS, car, bike or such to work
 
[[Category:Not reached - Did not attempt]]  when you went to an alternate location, or decided early on to abort the expedition.
 
-->
 

Latest revision as of 04:24, 9 August 2019

Fri 29 Oct 2010 in 45,-122:
45.6381662, -122.4052664
geohashing.info google osm bing/os kml crox



Location

Near Hwy 500 east of Mill Plain, Washington

Participants

Plans

Print a Google Map, program a GPS, run a quick errand. Head out to the hashpoint, which was probably on private land.

Expedition

The template asks: How did it all turn out? Answer: Very badly.

This was one of those expeditions that really didn't seem to really have a chance.

I started by printing out the Google maps page with directions. I grabbed it and headed out the door, planning on programming the GPS on the way.

I got out the door when I noticed that for some reason Google Maps has stopped printing out the coordinates as the destination when you print out directions as well. So I ran back and quickly popped up the Peeron page and told it to print. I stuffed it into my bag and headed out to the car. On the way, I attempted to get the coordinates on my organizer as a backup. It reported that it had no battery left. It charges via the USB connection, so I couldn't just change the batteries.

"No problem", I think. "I've got the coordinates on the Peeron page. I'll go with them."

I get to my quick errand and go to program the GPS before I hit the road. Oops. The printout of the Peeron page doesn't include the box in the lower right!

Okay - I've got a final fallback. The browser on my cellphone will show me the coordinates if I hit the right page, which is painful, but possible. Except the browser won't show me any pages, let alone one with hashpoint data. Apparently a recent power outage has broken things. More work for me to do the next day.

Finally, I call APR and ask him to text me the coordinates. Which he does. Now I can put them into the GPS...the one with the low batteries...which die before I finish entering the coordinates. Luckily there are spare batteries in the camera case.

We hit the road...For a little while...Until I hit traffic. And I wait, and move a little, and wait, and move a little. And wait.

Finally, I realize that I've burned up so much time that at this rate I won't make it there and back close to in time for dinner. I give up and take the next exit to head home, leaving the hashpoint for some future retro expedition, perhaps when we go to visit the very first geohashing expedition ever, which happens to be in that direction.