Difference between revisions of "2022-06-23 51 4"

Latest revision as of 21:17, 13 December 2022

Location

This hash is located on a railway line between Schiedam and Delft, The Netherlands. It is on the northbound track right on the left rail. About 10 passenger trains pass this hash every hour.

Participants

Blauwe BIC

Plans

Blauwe BIC

I had no plans and quite frankly, did not check the location of the hash the evening before (as I usually do) because I was working late. This almost never happens but it of course did happen the day the hash was located exactly on my daily morning commute to work. Therefore, this expedition does not count on the basis of lack of evidence, and earned me the Curse of Unawareness consolation prize.

Expedition

Blauwe BIC

I took the 6:05 AM train from Rotterdam Central to The Hague Central and passed the hash at around 6:14 AM, cursefully unaware. I was even in a seat on the left side of the train, hovering above the left rail where the hash exactly was.

My work and evening plans did not allow enough time for a revisit the same day, by taking the same train line again.

Tracklog

Photos

Blauwe BIC

Passing by the geohash later that evening, on the southbound (wrong) track.

Achievements

Blauwe BIC earned the Curse of Unawareness Consolation Prize

by reaching the (51, 4) geohash on 2022-06-23 without knowing it was there.

@@ Line 36: / Line 36: @@
 === Blauwe BIC ===
-If only I could provide photos of the lovely misty landscape I was enjoying. Sorry folks.
 <!-- Insert pictures between the gallery tags using the following format:
 Image:2020-##-## ## ## Alpha.jpg | Witty Comment
 -->
 <gallery perrow="5">
+Image:2022-06-23 51 4 On the wrong track.jpg|thumb|Passing by the geohash later that evening, on the southbound (wrong) track.
 </gallery>
@@ Line 54: / Line 53: @@
 }}
-<!-- =============== USEFUL CATEGORIES FOLLOW ================
+[[Category:Coordinates reached - Did not attempt]]
-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. -->
+{{location|NL|ZH}}
-[[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. -->
-<!-- Potential categories. Please include all the ones appropriate to your expedition -->
-<!-- If this is a planning page:
-[[Category:Expedition planning]]
--->
-<!-- If all those plans are never acted upon, change [[Category:Expedition planning]] to [[Category:Not reached - Did not attempt]]. -->
-<!-- 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]]
-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 - Attended alternate location]]
-(Don't forget to delete this final close comment marker) -->


Thu 23 Jun 2022 in 51,4: 51.9707100, 4.3756767 geohashing.info google osm bing/os kml crox