Difference between revisions of "2011-10-22 -37 147"

From Geohashing
imported>Stevage
imported>Stevage
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:2011-10-22_-37_147_09-53-20-777.jpg|thumb|left]]
 
[[Image:2011-10-22_-37_147_09-53-20-777.jpg|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=-37
 
| lat=-37

Revision as of 05:33, 24 October 2011

2011-10-22 -37 147 09-53-20-777.jpg
Sat 22 Oct 2011 in -37,147:
-37.9295437, 147.3459880
geohashing.info google osm bing/os kml crox


Success!

Oh wait, the geohash droid is giving incorrect readings. Blinded by science!

Oh wait, the geohash droid was right after all, and Carabiner had a bug. (well, sort of). Success!


Location

In a paddock, not far from the highway halfway between Bairnsdale and Sale.

Participants

Stevage, Talex, Felix Dance

Expedition

Steve, tAlex, Felix, and four others, were on a huge two-day bike ride from Bairnsdale to Melbourne. We had 160 km to cover on the Saturday, but still, plenty of time for a geohash right? We forgot to check it in the morning before setting out from Bairnsdale. After an hour or so, we suddenly realised, but couldn't exactly bring the expedition to a grinding halt just for a geohash. An uncomfortable feeling grew - what if the hash was right over there? What if it was a couple of kilometres behind us, rapidly receding into the distance?

Through the magic of telepathy, Alex and I concocted a plan: I called a snack halt, while 100m up the road Alex sneakily pulled out his phone, and brought up the geohashing app. The happy words were called out "It's just 9 kilometres north of here". Wow...we were heading almost due west, so for the point to be north meant we'd stopped at the ideal moment.

So, who would come with us to slay the dragon? It all depended on how much unsealed road there was. I squinted at the map, and provided the most accurate estimate available under the circumstances: "Somewhere between zero and nine kilometres of unsealed. Maybe more." This instantly split the group, much to our chagrin. They zoomed off into the distance. Meanwhile we doubled back a couple of hundred metres.

Amazingly, the unsealed road never materialised. Beautiful, narrow, untrafficed, high quality sealed roads were our red carpet. Sulphur-crested cockatoos were our choir. Slightly giddy, we soon found ourselves at a friendly looking paddock fence. No farm houses too near, just an old derelict temporary shelter from decades past. We strode through the wet grass, straight towards where the point was clearly located: in the middle of a dam. Without a word, it was understood we would strip down and dive into the muddy shallows without hesitation.

Sadly, the point turned out to be on dry land. But it was a nice spot, under a tree. Quick photos were quickly uploaded, then we jumped back on the bikes and caught up with our friends in Stratford.

From the geohash, we rode approximately 280 kilometres home. I wonder if that's any kind of record?

Tracklog

http://app.strava.com/rides/2080339

(The geohash is around the 47 km mark.)

Photos

Achievements