Difference between revisions of "2015-04-27 39 -89"

From Geohashing
imported>Mystrsyko
(Plans)
imported>FippeBot
m (Location)
 
(3 intermediate revisions by one other user not shown)
Line 17: Line 17:
  
 
== Expedition ==
 
== Expedition ==
<!-- how it all turned out. your narrative goes here. -->
+
[[File:2015-04-27 39 -89 frown.jpg|200px|thumb|left|Stupid frown]]
 +
For once there is a point close to home, but alas, it seemed to be in someone's yard. However, it seemed there was no fence around the yard and that the point may be near enough a sidewalk that I could get within my GPS margin of error, so off I went.
 +
 
 +
Convieniently, the neighborhood the point lay in happened to be right off the bike trail near my house. So I hopped on it, and despite forgetting exactly where I needed to leave the trail, I was able to find the 4 lane road called Bradfordton that ran past the point. To my surprise, Bradfordton begins at the bike trail (no car access) and ends just a quarter mile or so farther north at a farm field (with no car access), so why they felt the need to make it four lanes is not known to me.
 +
 
 +
I approached the hash from the west side on Bradfordton and discovered why Google Maps is not a reliable tool for planning geohashing expeditions. It would seem that sometime between the satellite image on Google and the present, the owners of the house had erected a privacy fence on their property. Even without the fence, however, the point was still well outside my margin of error, which due to the clear sunny skies and lack of tall buildings or trees, was extremely small. I decided to go around and approach the point from the front of the homes, but again, was denied by the surprisingly small margin, and with no cars in either of the home's driveways (a universal sign of nobody being home in the suburbs) I decided to call it a day and head home.
 +
 
 +
On the way back, I discovered that I had forgotten to turn my GPS tracking app back on after I shut it off near the hash point, so my track log is missing some distance in there.
  
 
== Tracklog ==
 
== Tracklog ==
<!-- if your GPS device keeps a log, you may post a link here -->
+
https://www.strava.com/activities/293686440
  
 
== Photos ==  
 
== Photos ==  
<!-- Insert pictures between the gallery tags using the following format:
+
 
Image:2012-##-## ## ## Alpha.jpg | Witty Comment
+
<gallery perrow="4">
-->
+
Image:2015-04-27 39 -89 fence.jpg|Fence that Google said wasn't there
<gallery perrow="5">
+
Image:2015-04-27 39 -89 hash.jpg|It's right there! Darn!
 +
Image:2015-04-27 39 -89 screenshot1.png|Proof Google doesn't know everything
 +
Image:2015-04-27 39 -89 screenshot2.png|As close as I could get without tresspassing
 
</gallery>
 
</gallery>
  
 
== Achievements ==
 
== Achievements ==
 
{{#vardefine:ribbonwidth|800px}}
 
{{#vardefine:ribbonwidth|800px}}
<!-- Add any achievement ribbons you earned below, or remove this section -->
+
{{No trespassing
 
 
 
 
<!-- =============== 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]]
 
  
<!-- ==REQUEST FOR TWITTER BOT== Please leave either the New report or the Expedition planning category in as long as you work on it. This helps the twitter bot a lot with announcing the right outcome at the right moment. -->
+
    | latitude = 39
 +
    | longitude = -89
 +
    | date = 2015-04-27
 +
    | name = Mystrsyko 
 +
    | distance = 60ft
  
<!-- 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]]
 
 
 
--><!-- or if you failed :(
 
 
[[Category:Coordinates not reached]]
 
[[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]]
 
[[Category:Not reached - No public access]]
 
+
{{location|US|IL|SM}}
When you failed get your GPS, car, bike or such to work:
 
[[Category:Not reached - Technology]]
 
   
 
When you went to an alternate location instead of the actual geohash:
 
[[Category:Not reached - Did not attempt]]
 
 
 
(Don't forget to delete this final close comment marker) -->
 

Latest revision as of 03:28, 15 August 2019

Mon 27 Apr 2015 in 39,-89:
39.7763553, -89.7457213
geohashing.info google osm bing/os kml crox


Location

In a yard on the west side of Springfield.

Participants

Mystrsyko

Plans

Going to head there and see if I can get within my margin of error. - Mystrsyko (talk)

Expedition

Stupid frown

For once there is a point close to home, but alas, it seemed to be in someone's yard. However, it seemed there was no fence around the yard and that the point may be near enough a sidewalk that I could get within my GPS margin of error, so off I went.

Convieniently, the neighborhood the point lay in happened to be right off the bike trail near my house. So I hopped on it, and despite forgetting exactly where I needed to leave the trail, I was able to find the 4 lane road called Bradfordton that ran past the point. To my surprise, Bradfordton begins at the bike trail (no car access) and ends just a quarter mile or so farther north at a farm field (with no car access), so why they felt the need to make it four lanes is not known to me.

I approached the hash from the west side on Bradfordton and discovered why Google Maps is not a reliable tool for planning geohashing expeditions. It would seem that sometime between the satellite image on Google and the present, the owners of the house had erected a privacy fence on their property. Even without the fence, however, the point was still well outside my margin of error, which due to the clear sunny skies and lack of tall buildings or trees, was extremely small. I decided to go around and approach the point from the front of the homes, but again, was denied by the surprisingly small margin, and with no cars in either of the home's driveways (a universal sign of nobody being home in the suburbs) I decided to call it a day and head home.

On the way back, I discovered that I had forgotten to turn my GPS tracking app back on after I shut it off near the hash point, so my track log is missing some distance in there.

Tracklog

https://www.strava.com/activities/293686440

Photos

Achievements

Notrespassing.gif
Mystrsyko earned the No trespassing consolation prize
by almost (60ft) reaching the (39, -89) geohash on 2015-04-27.