Talk:2013-05-08 61 23

I notice the category was changed to not reached because of the stamp on the photos. I'd just like to point out that the GeohashDroid app (which that stamp looks to be from) often puts grossly inaccurate locations on those stamps, even while showing a relatively accurate location to the user. I've personally seen differences of over 6 miles (9.7km) between the stamp on the photo and the display on the screen at the time when the photo was taken and/or uploaded. Also, I believe the stamp attempts to reflect the location from which it was uploaded, not necessarily the location where it was taken. I'm not saying that the change was definitely wrong, as no proof is offered to dispute the stamp on the photos. But I don't consider that stamp in and of itself to be proof of not reaching it, and his photos are consistent with the area within a couple hundred meters of the hash. Also, the claim to have found the geocache located about 600m from the hashpoint bodes well for him having been closer than most of the stamps on the photos indicate. --Eldin (talk) 04:52, 31 July 2013 (EDT)

Thanks for the reply. I haven't used the Droid app yet so I wasn't aware of the problems with the location stamps. Given that, I'm very happy to assume that the stamps are wrong and the hashpoint was indeed reached. I've changed the categories back again. — Benjw  _{talk} 05:32, 31 July 2013 (EDT)

Yeah, it's a bug I wish would get fixed. Sometimes the stamps on the pictures are accurate to within a few feet (to the location from which you uploaded the picture), other times they're wildly inaccurate, with no obvious rhyme or reason, except that photos uploaded close enough together in time and location will tend to have about the same error margin. --Eldin (talk) 10:52, 31 July 2013 (EDT)