Difference between revisions of "2024-05-20 38 152"
([live picture]Within 140m for sure... How close is air geohash again?) |
(Actually filling out the report) |
||
| Line 1: | Line 1: | ||
| − | + | {{meetup graticule | |
| − | + | | lat=38 | |
| − | + | | lon=152 | |
| − | + | | date=2024-05-20 | |
| − | + | }} | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | | lat=38 | ||
| − | | lon=152 | ||
| − | | date=2024-05-20 | ||
| − | }} | ||
== Location == | == Location == | ||
<!-- where you've surveyed the hash to be --> | <!-- where you've surveyed the hash to be --> | ||
| + | A particularly nice bit of cloud over the Pacific Ocean. | ||
== Participants == | == Participants == | ||
| − | + | [[User:Ironeagl|Ironeagl]] ([[User talk:Ironeagl|talk]]) | |
| − | |||
== Plans == | == Plans == | ||
<!-- what were the original 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 == | == Expedition == | ||
<!-- how it all turned out. your narrative goes here. --> | <!-- 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 == | == Tracklog == | ||
<!-- if your GPS device keeps a log, you may use Template:Tracklog, post a link here, or both --> | <!-- 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 == | == Photos == | ||
| Line 40: | Line 37: | ||
{{#vardefine:ribbonwidth|100%}} | {{#vardefine:ribbonwidth|100%}} | ||
<!-- Add any achievement ribbons you earned below, or remove this section --> | <!-- 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__ | __NOTOC__ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Expeditions]] | [[Category:Expeditions]] | ||
| − | |||
[[Category:Expeditions with photos]] | [[Category:Expeditions with photos]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Coordinates reached]] | [[Category:Coordinates reached]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 04:51, 27 May 2024
| Mon 20 May 2024 in 38,152: 38.6193744, 152.2604976 geohashing.info google osm bing/os kml crox |
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
|
 |
This user earned the Air geohash achievement
|
