moominmolly: (Default)
moominmolly ([personal profile] moominmolly) wrote2009-06-11 11:06 am
Entry tags:

(no subject)

Last night, I was wandering through the woods and found a mysterious little box. It was not a geocache, but it did prompt [livejournal.com profile] vespid_interest to mention geocaching as something I in particular would get a kick out of, which several different people have done over the years. Anyway, it made me curious:

[Poll #1414358]

[identity profile] vespid-interest.livejournal.com 2009-06-11 07:04 pm (UTC)(link)
The iPhone 3G GPS usually has an accuracy of 56 feet for me, or 34 if I'm really lucky. (Nothing in between oddly.) I've had about a 50% success rate finding caches within 56-feet which is ok if I'm looking for one on a lark but if I just walked 20 minutes to find a cache it's frustrating to get stuck. It makes me not even want to try next time.
And in the forest where there is no reception it's almost useless.

[identity profile] cuthalion.livejournal.com 2009-06-11 10:02 pm (UTC)(link)
Aha! Okay the iPhone lacks WAAS it turns out. So it can be less accurate than other GPSes, contrary to what I said above.

I remember those numbers from my old Garmin eTrex Legend (which is what I used for geocaching). Those do have WAAS support, but they also aren't very sensitive, and my experience was similar to yours, except I thought it was more fun than you seem to have.

I think the discrete increments of distance is probably due to the discrete number of satellites it had fixes on.