Difference between revisions of "2014-02-04 47 -122"
From Geohashing
imported>Thomcat (Correct calculation & accuracy) |
imported>FippeBot m (Location) |
||
| Line 37: | Line 37: | ||
[[Category:Coordinates not reached]] | [[Category:Coordinates not reached]] | ||
[[Category:Not reached - No public access]] | [[Category:Not reached - No public access]] | ||
| + | {{location|US|WA|KN}} | ||
Latest revision as of 05:25, 14 August 2019
| Tue 4 Feb 2014 in Seattle: 47.7476221, -122.3417716 geohashing.info google osm bing/os kml crox |
Location
The backyard of 16341 Interlake Ave North in Shoreline.
Participants
Plans
Check it out on the way to work - roughly 7:40 am.
Expedition
Swung by, took a photo of the front of the house, then looped around to park near the house, the better to validate re-calibration of Geohash Android. House is not for sale, geohash point is in the back yard by the shed, expedition ends there (unless the owner reads this website today and claims couch potato).
Calibration
Assuming Google Maps and Bing Maps are able to reflect a Latitude/Longitude near Seattle correctly:
- The number posted on the photo was highly accurate, showing where I was parked on the street.
- The number posted to the webpage was inaccurate - resulting in the corner of the house.
- Update - this is the best accuracy for only 4 digits after the decimal point, so they essentially match. 4 digits gets us roughly 8 meters; 5 digits gets us to within 8/10ths of a meter, according to Wikipedia (Decimal Degrees of Accuracy).
