Difference between revisions of "2023-10-17 47 -122"

Latest revision as of 14:20, 18 October 2023

Location

Between two properties in Alderwood

Participants

Thomcat

Plans

Expedition

I had morning errands on the way to work and totally forgot to check the hashpoint at 6:30 am.

Errands finished, I pulled up geohashdroid and found the point to be roughly a kilometer north east of my location. Not far from a road, worth driving by and possibly stopping. With no further research, I proceeded.

Parking, I could see some sort of garden or community P-patch. In later looking at google maps, this is a property between two properties. A brook runs along the road side and then south into the property, likely between me and the hashpoint. Thomcats are notoriously bad at crossing water.

Lining up the latitude left me 10 meters short of the actual point, not a success. A large tree was east of me, and the hashpoint was likely just east of that.

I backtracked and went through the garden plots. While there were a lot of blackberries and stickers, I was able to move close to the tree. While this would be much closer to the point, the greenery overhead was distorting the signal. Eventually it settled down to under 2 meters, a success!

I shot a final photo of my car through the garden patch, then my wet sneakers and I left the expedition and continued on to work.

Tracklog

Photos

North of point @47.8122,-122.2799
A stream runs through it @47.8122,-122.2801
Past that tree @47.8121,-122.2800
Geohasher @47.8121,-122.2798
Hashcar & P patch @47.8121,-122.2798

Achievements

@@ 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)
+{{meetup graticule
-[[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=47
 | lon=-122
 | date=2023-10-17
+| graticule_name=Seattle
+| graticule_link=Seattle, Washington
 }}<!-- edit as necessary -->
 == Location ==
-<!-- where you've surveyed the hash to be -->
+Between two properties in Alderwood
 == 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:Thomcat|Thomcat]]
--->
 == Plans ==
@@ Line 23: / Line 16: @@
 == Expedition ==
-<!-- how it all turned out. your narrative goes here. -->
+I had morning errands on the way to work and totally forgot to check the hashpoint at 6:30 am.
+Errands finished, I pulled up geohashdroid and found the point to be roughly a kilometer north east of my location. Not far from a road, worth driving by and possibly stopping. With no further research, I proceeded.
+Parking, I could see some sort of garden or community P-patch. In later looking at google maps, this is a property between two properties. A brook runs along the road side and then south into the property, likely between me and the hashpoint. Thomcats are notoriously bad at crossing water.
+Lining up the latitude left me 10 meters short of the actual point, not a success. A large tree was east of me, and the hashpoint was likely just east of that.
+I backtracked and went through the garden plots. While there were a lot of blackberries and stickers, I was able to move close to the tree. While this would be much closer to the point, the greenery overhead was distorting the signal. Eventually it settled down to under 2 meters, a success!
+I shot a final photo of my car through the garden patch, then my wet sneakers and I left the expedition and continued on to work.
 == Tracklog ==
@@ Line 49: / Line 52: @@
 <!-- Add any achievement ribbons you earned below, or remove this section -->
-__NOTOC__
-<!-- =============== 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. -->
-<!-- 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]]
+{{location|US|WA|SN}}
---><!-- 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) -->


Tue 17 Oct 2023 in Seattle: 47.8120758, -122.2798473 geohashing.info google osm bing/os kml crox