Difference between revisions of "2013-03-28 -37 143"

Latest revision as of 12:34, 1 August 2020

Location

Up a spooky bush track in navigators (in the middle of the night!)

Participants

Snaplatitude (talk)
Mcdonalds employee

Expedition

Seemed pretty straightforward, there were several roads leading to the hashsite according to the android app and google maps. Oh how google maps was wrong. The first attempt, to come at the road the hash is on from the West, let us see that there was in fact NO ROAD (or it was some ethereal ghost-road), all we found was a cliff with trees on it, inaccessible by vehicle and too spooky to go through on foot at night. So we doubled back, up around North and back down to access it from the East, just off Yankee Flat Road, once again, this must be some ghost road, because it was almost unfindable. First we were taken to a river, not a road at all, then a driveway heading in the entirely wrong direction, and then finally after 20 mintues of faffing about we found the road we were looking for, very poorly signed (if at all) the only way we knew that was it is because we showed as on it on Google Maps. After heading about 500 metres down this road we found a house, so it was someones driveway. Of course country folk don't like lights being shone in their windows at midnight so we had to get out of there, but the track continued on past the house... into the dark, creepy bush, it got narrower and narrower and we decided to just let it go. Fail.

@@ 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
 | lat=-37
@@ Line 15: / Line 5: @@
 }}
-<!-- edit as necessary -->
 __NOTOC__
 == Location ==
-<!-- where you've surveyed the hash to be -->
+Up a spooky bush track in navigators (in the middle of the night!)
 == Participants ==
-<!-- who attended: If you link to your wiki user name in this section, your expedition will be picked up by the various statistics generated for geohashing. You may use three tildes ~ as a shortcut to automatically insert the user signature of the account you are editing with.
+*[[User:Snaplatitude|Snaplatitude]] ([[User talk:Snaplatitude|talk]])
--->
+*Mcdonalds employee
-== Plans ==
-<!-- what were the original plans -->
 == Expedition ==
-<!-- how it all turned out. your narrative goes here. -->
+Seemed pretty straightforward, there were several roads leading to the hashsite according to the android app and google maps. Oh how google maps was wrong. The first attempt, to come at the road the hash is on from the West, let us see that there was in fact NO ROAD (or it was some ethereal ghost-road), all we found was a cliff with trees on it, inaccessible by vehicle and too spooky to go through on foot at night. So we doubled back, up around North and back down to access it from the East, just off Yankee Flat Road, once again, this must be some ghost road, because it was almost unfindable. First we were taken to a river, not a road at all, then a driveway heading in the entirely wrong direction, and then finally after 20 mintues of faffing about we found the road we were looking for, very poorly signed (if at all) the only way we knew that was it is because we showed as on it on Google Maps. After heading about 500 metres down this road we found a house, so it was someones driveway. Of course country folk don't like lights being shone in their windows at midnight so we had to get out of there, but the track continued on past the house... into the dark, creepy bush, it got narrower and narrower and we decided to just let it go. Fail.
-== Tracklog ==
-<!-- if your GPS device keeps a log, you may post a link here -->
-== Photos ==
-<!-- Insert pictures between the gallery tags using the following format:
-Image:2012-##-## ## ## Alpha.jpg | Witty Comment
--->
-<gallery perrow="5">
-</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]]
--- and one or more of --
-[[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:Coordinates not reached]]
--- and a reason --
-When there is a natural obstacle between you and the target:
-[[Category:Not reached - Mother Nature]]
-When there is a man-made obstacle between you and the target:
 [[Category:Not reached - No public access]]
+{{location|AU|VIC|MO}}
-When you failed get your GPS, car, bike or such to work:
-[[Category:Not reached - Technology]]
-When you went to an alternate location, or decided early on to abort the expedition:
-[[Category:Not reached - Did not attempt]]
-(Don't forget to delete this final close comment marker) -->


Thu 28 Mar 2013 in -37,143: -37.6003682, 143.9046992 geohashing.info google osm bing/os kml crox