Difference between revisions of "User talk:Dunstergirl"
imported>Cjk |
imported>Relet |
||
| Line 8: | Line 8: | ||
Usually it is hard to get even the 4th decimal correct. There are different schools of though how near you should be. My GPS in my phone says it has an accuracy of 1-2m but it lies and bounces around when I'm standing still. So I and many others just say within 10m is good enough. Remember not even google maps is exact down to more than 2m. Oh, and you can definitely claim a MNIMB-ribbon for getting the car stuck and hiking through that amount of snow. Look here [[2012-01-29_60_15]]. -- [[User:Cjk|Cjk]] 09:27, 5 March 2012 (EST) | Usually it is hard to get even the 4th decimal correct. There are different schools of though how near you should be. My GPS in my phone says it has an accuracy of 1-2m but it lies and bounces around when I'm standing still. So I and many others just say within 10m is good enough. Remember not even google maps is exact down to more than 2m. Oh, and you can definitely claim a MNIMB-ribbon for getting the car stuck and hiking through that amount of snow. Look here [[2012-01-29_60_15]]. -- [[User:Cjk|Cjk]] 09:27, 5 March 2012 (EST) | ||
| + | |||
| + | :Usually we say that you should be within 10m (a very rough estimate for how accurate a GPS can be even in suboptimal conditions), and you should be reasonably certain that the geohash can be on your side of any obstacles. It's all a game. If your GPS fails in the middle of an empty field close to the hash, you can still walk a big circle and claim you have been reasonably close. If it's on the other side of that canyon, while your GPS gives 20m, maybe settle for a consolation prize ribbon. Failing is part of the game. The important part is the adventure. :) -- [[User:relet|relet]] 09:33, 5 March 2012 (EST) | ||
Revision as of 14:33, 5 March 2012
Welcome to Geohashing. Don't worry too much about the accessibility: That's often an issue here in the Pacific NW. You get credit for trying to get there, and the stories are often just as good, if not better! Jiml 14:19, 4 March 2012 (EST)
- Thanks for fixing my spelling error in the Raush Valley. Is that your graticule? -Robyn 20:28, 4 March 2012 (EST)
Ah, not sure how to reply but yes, that is mine.
Usually it is hard to get even the 4th decimal correct. There are different schools of though how near you should be. My GPS in my phone says it has an accuracy of 1-2m but it lies and bounces around when I'm standing still. So I and many others just say within 10m is good enough. Remember not even google maps is exact down to more than 2m. Oh, and you can definitely claim a MNIMB-ribbon for getting the car stuck and hiking through that amount of snow. Look here 2012-01-29_60_15. -- Cjk 09:27, 5 March 2012 (EST)
- Usually we say that you should be within 10m (a very rough estimate for how accurate a GPS can be even in suboptimal conditions), and you should be reasonably certain that the geohash can be on your side of any obstacles. It's all a game. If your GPS fails in the middle of an empty field close to the hash, you can still walk a big circle and claim you have been reasonably close. If it's on the other side of that canyon, while your GPS gives 20m, maybe settle for a consolation prize ribbon. Failing is part of the game. The important part is the adventure. :) -- relet 09:33, 5 March 2012 (EST)
