Difference between revisions of "2024-05-20 38 152"

Latest revision as of 05:42, 27 May 2024

Location

A particularly nice bit of cloud over the Pacific Ocean.

Participants

Plans

Business was taking me on a flight over the Pacific Ocean, and realizing how many graticules I would be passing over (and seeking some entertainment over the 12 hour flight), I regularly checked Geohash Droid and followed along.

Expedition

After one close call, I thought the next pass (several graticules over) might get even closer. Turns out it did, and Geohash Droid reported a minimum of 140m, qualifying for an Air Geohash! The screenshot reports 140m, but looking at the picture and following the direction of travel (which was quite straight) it looks like the minimum distance to the hash was ~70m (not including HDOP).

Tracklog

I did not have a tracklog, but Flightaware luckily keeps a log of recent flight paths (to 4 decimal places, which should give an error of <10m, but... that does not account for HDOP): https://www.flightaware.com/live/flight/DAL167/history/20240519/1835Z/KSEA/RJTT

Plotting this flight path in Google Earth gives a minimum distance to the hashpoint of 570m, which is outside the 310m target. I'm assuming the HDOP of my device and the Flightaware report overlapped, and the real point was somewhere in between, which statistically speaking is: 570+70/2 = 320m, close enough. Future expeditions will have tracklog from my device which should clear things up in this situation :)

Photos

Within 140m for sure... How close is air geohash again?

Achievements

This user earned the Graticule Unlocked Achievement

by being the first to reach any hashpoint in the (38, 152) graticule, here, on 2024-05-20.

This user earned the Air geohash achievement

by reaching the (38, 152) geohash on 2024-05-20 by Airbus A330-900 (N402DX), attaining the rank of Passenger.

@@ 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
+    | lat=38
-[[Image:{{{image|IMAGE}}}|thumb|left]]
+    | lon=152
+    | date=2024-05-20
-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=38
-| lon=152
-| date=2024-05-20
-}}<!-- edit as necessary -->
 == Location ==
 <!-- where you've surveyed the hash to be -->
+A particularly nice bit of cloud over the Pacific Ocean.
 == 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:Ironeagl|Ironeagl]] ([[User talk:Ironeagl|talk]])
--->
 == Plans ==
 <!-- what were the original plans -->
+Business was taking me on a flight over the Pacific Ocean, and realizing how many graticules I would be passing over (and seeking some entertainment over the 12 hour flight), I regularly checked Geohash Droid and followed along.
 == Expedition ==
 <!-- how it all turned out. your narrative goes here. -->
+After one close call, I thought the next pass (several graticules over) might get even closer.  Turns out it did, and Geohash Droid reported a minimum of 140m, qualifying for an Air Geohash!  The screenshot reports 140m, but looking at the picture and following the direction of travel (which was quite straight) it looks like the minimum distance to the hash was ~70m (not including HDOP).
 == Tracklog ==
 <!-- if your GPS device keeps a log, you may use Template:Tracklog, post a link here, or both -->
+I did not have a tracklog, but Flightaware luckily keeps a log of recent flight paths (to 4 decimal places, which should give an error of <10m, but... that does not account for HDOP): https://www.flightaware.com/live/flight/DAL167/history/20240519/1835Z/KSEA/RJTT
+Plotting this flight path in Google Earth gives a minimum distance to the hashpoint of 570m, which is outside the 310m target.  I'm assuming the HDOP of my device and the Flightaware report overlapped, and the real point was somewhere in between, which statistically speaking is: 570+70/2 = 320m, close enough.  Future expeditions will have tracklog from my device which should clear things up in this situation :)
 == Photos ==
@@ Line 40: / Line 37: @@
 {{#vardefine:ribbonwidth|100%}}
 <!-- Add any achievement ribbons you earned below, or remove this section -->
+{{Graticule unlocked
+    | latitude=38
+    | longitude=152
+    | date=2024-05-20
+}}
+{{air geohash
+    | latitude=38
+    | longitude=152
+    | date=2024-05-20
+    | vehicle = Airbus A330-900 (N402DX)
+    | subcategory = Passenger
+}}
 __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]]
-<!-- 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]]
--->
-<!-- if you reached your coordinates:
 [[Category:Coordinates reached]]
+{{location|XI}}
---><!-- or if you did not reach the coordinates:
-[[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]]
-(Don't forget to delete this final close comment marker) -->


Mon 20 May 2024 in 38,152: 38.6193744, 152.2604976 geohashing.info google osm bing/os kml crox