Difference between revisions of "2024-05-08 34 -118"

From Geohashing
(Add more expedition description)
Line 10: Line 10:
  
 
== Plans ==
 
== Plans ==
This morning, I ([[User:Jeremy|Jeremy]]) got a notification from my geohash-calculating [https://apps.apple.com/us/app/shortcuts/id915249334 shortcut] that the geohash was accessible. My best friend [[User:Lehonk|Ethan]] and I have been waiting for months for our first hash, so this is really exciting. Today happens to be a really good day, our schedules are clear and the weather is great. There are four geocaches nearby and the [https://maps.app.goo.gl/R5n6f7vYWuRfZ43v6 Iron Horse trailhead] is close, so we will try to take our bikes down to the trailhead and bike around.
+
This morning, I (Jeremy) got a notification from my geohash-calculating [https://apps.apple.com/us/app/shortcuts/id915249334 shortcut] that the geohash was accessible. My best friend Ethan and I have been waiting for months for our first hash, so this is really exciting. Today happens to be a really good day, our schedules are clear and the weather is great. There are four geocaches nearby and the Iron Horse trailhead is not far, so we will try to take our bikes down to the trailhead and bike around.
  
 
== Expedition ==
 
== Expedition ==
We loaded up our bikes and drove down to the Iron Horse trailhead. We set out on our bikes (you can see the moment in the tracklog where I realised "hey, I should record") and crossed some busy intersections. Thankfully, the buttons for telling the speeding Teslas to stop worked. We didn't realize from the map how big the new development is, the field the geohash was in looked way smaller from the sky. ...
+
We loaded up our bikes and drove down to the Iron Horse trailhead. Of course, Ethan set the mood with some rock on the way there. We prepared our bikes and set off for the geohash (you can see the start of the tracklog where I thought "hey, I should record"). We had to cross some busy intersections, but the buttons for telling the speedy Teslas (because California) to stop were functional, so all was well. As we were biking up Magic Mountain Parkway, we realised that the new development was a lot bigger than it looked on the map. Still, it wasn't very long before we arrived at the hashpoint's field.
 +
 
 +
There were some No Trespassing signs, but it was just a big dirt lot. We walked across to the hashpoint, took some pictures, and congratulated ourselves on our first geohash. Interestingly, the piles of dirt we saw on Street View from November weren't there anymore, and the hill across the street had many fancy under-construction houses. The stream that OSM showed as directly under the geohash was a tad east of there, as well. When we were satisfied, we got back on our bikes and set off for the nearby Five Points neighborhood in search of geocaches.
 +
 
 +
(Warning: spoilers for geocaches) The first geocache we looked for ([https://www.geocaching.com/geocache/GCAHWQ6 GCAHWQ6]) was in this cool little pump track right by the houses.  We spent 20 minutes looking around the area for this little hide-a-key rock. With the help of the hint ("Low & Under"), I (Jeremy) finally found the cheeky little cache cleverly hidden under the edge of one of the bumps (see pictures). The second geocache ([https://www.geocaching.com/geocache/GCAJR8K GCAJR8K]) was down the road at the local community center place. The page told us it was a little magnetic nano, close to the sign, though the hint never helped us. We spent another 20 minutes looking for this one, but couldn't find it. Eventually, it was too late, and we decided to head back.
 +
 
 +
The bike back to the car at the trailhead went smoothly, and we packed up our bikes, happy with our accomplishment. We did spend 10 minutes trying to start the car before we realized it was in park, however. This was a fun adventure, we hope to go for more hashes in the future.
  
 
== Tracklog ==
 
== Tracklog ==
I never paused the tracking, so you get to see us wandering around at the geohash and geocaches.
+
I never paused my recording, so you get to see us wandering around at the geohash and geocaches.
 
 
 
{{tracklog|2024-05-08 34 -118 Jeremy's watch.gpx}}
 
{{tracklog|2024-05-08 34 -118 Jeremy's watch.gpx}}
  

Revision as of 06:29, 10 May 2024


Wed 8 May 2024 in 34,-118:
34.4130363, -118.5996918
geohashing.info google osm bing/os kml crox


Location

The hash is in a dirt area off the road near Magic Mountain and the new Valencia development. Google's Street View from 6 months ago shows some piles of dirt and a freestanding gate we can walk past. Behind the hash is a ditch with a dry culvert that we could also walk down. (Apple's satellite imagery is quite old, showing actual construction that no longer appears to be there.)

Participants

Jeremy and Ethan

Plans

This morning, I (Jeremy) got a notification from my geohash-calculating shortcut that the geohash was accessible. My best friend Ethan and I have been waiting for months for our first hash, so this is really exciting. Today happens to be a really good day, our schedules are clear and the weather is great. There are four geocaches nearby and the Iron Horse trailhead is not far, so we will try to take our bikes down to the trailhead and bike around.

Expedition

We loaded up our bikes and drove down to the Iron Horse trailhead. Of course, Ethan set the mood with some rock on the way there. We prepared our bikes and set off for the geohash (you can see the start of the tracklog where I thought "hey, I should record"). We had to cross some busy intersections, but the buttons for telling the speedy Teslas (because California) to stop were functional, so all was well. As we were biking up Magic Mountain Parkway, we realised that the new development was a lot bigger than it looked on the map. Still, it wasn't very long before we arrived at the hashpoint's field.

There were some No Trespassing signs, but it was just a big dirt lot. We walked across to the hashpoint, took some pictures, and congratulated ourselves on our first geohash. Interestingly, the piles of dirt we saw on Street View from November weren't there anymore, and the hill across the street had many fancy under-construction houses. The stream that OSM showed as directly under the geohash was a tad east of there, as well. When we were satisfied, we got back on our bikes and set off for the nearby Five Points neighborhood in search of geocaches.

(Warning: spoilers for geocaches) The first geocache we looked for (GCAHWQ6) was in this cool little pump track right by the houses. We spent 20 minutes looking around the area for this little hide-a-key rock. With the help of the hint ("Low & Under"), I (Jeremy) finally found the cheeky little cache cleverly hidden under the edge of one of the bumps (see pictures). The second geocache (GCAJR8K) was down the road at the local community center place. The page told us it was a little magnetic nano, close to the sign, though the hint never helped us. We spent another 20 minutes looking for this one, but couldn't find it. Eventually, it was too late, and we decided to head back.

The bike back to the car at the trailhead went smoothly, and we packed up our bikes, happy with our accomplishment. We did spend 10 minutes trying to start the car before we realized it was in park, however. This was a fun adventure, we hope to go for more hashes in the future.

Tracklog

I never paused my recording, so you get to see us wandering around at the geohash and geocaches.


Photos

(better pictures and videos will be uploaded later today (2024-05-09))

Achievements

Landgeohash.png
Jeremy and Ethan earned the Land geohash achievement
by reaching the (34, -118) geohash on 2024-05-08.
Bikegeohash.png
Jeremy and Ethan earned the Bicycle geohash achievement
by cycling 7 miles to and from the (34, -118) geohash on 2024-05-08.
TwoToN.png
Jeremy and Ethan earned the Two to the N achievement
by attempting to reach 20 hashpoints on 2024-05-08 and is promoted to Level 0 (Expeditions).