Difference between revisions of "2017-12-26 45 -122"
imported>Jiml (Add some details) |
imported>FippeBot m (Location) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 15: | Line 15: | ||
== Participants == | == Participants == | ||
| − | * [[User:Jiml| | + | * [[User:Jiml|Jim]] |
== Plans == | == Plans == | ||
| Line 54: | Line 54: | ||
[[Category:Expeditions with photos]] | [[Category:Expeditions with photos]] | ||
[[Category:Coordinates reached]] | [[Category:Coordinates reached]] | ||
| + | {{location|US|OR|WI}} | ||
Latest revision as of 03:14, 16 August 2019
| Tue 26 Dec 2017 in 45,-122: 45.5277625, -122.8090818 geohashing.info google osm bing/os kml crox |
Location
On a short cul-de-sac in Beaverton
Participants
Plans
Go by in the evening on my way home
Expedition
I was thinking I would head there after work, but the frozen and icy conditions rendered going to work not a clever choice, so I worked from home - luckily I had my computer at home from last week.
In the evening I went off to run some errands before it got too cold and icy. I got the tasks done, but decided to be a little adventurous and tried a new route, using my GPS to help guide me. Unfortunately, I missed the first 7 in the coordinates when I entered them and the GPS was sending me to someplace up in the hills 3 miles from the hashpoint. I kept trying to loop back towards where I knew the hashpoint was, but it kept pulling me off. Finally, I stopped and recheck the programming and fixed the problem. Then the GPS told me "3 feet", because I had stopped on the hashpoint!
It turns out that I knew exactly where the hashpoint was when I saw it on Google Maps because a group I'm part of used to meet near here a few years ago, and I'd sometimes drive through this driveway to get there. So this probably counts as a Deja Vu.
I took a picture of the GPS, but it was dark out, so nothing else was going to work.
Photos
Achievements
- Land Geohash
- Deja Vu
