When I've done GPS stuff with photos in houses, I've lopped off decimal digits until the circle which it represented was sufficiently large enough. I typically lop to one decimal digit to give "close enough, but not exact".
That's interesting... I didn't realize that it worked that way. For example, I just assumed that something like 32N, saved in an int, would be interpreted the same as 32.00000000N -- I didn't realize that the number of decimal places implied precision/significant digits. I suppose it's not surprising, and it makes sense, but I hadn't really thought much about it before. I also suppose there are probably systems out there that don't work with Decimal-Degrees and do assume 32 == 32.000 because the devs weren't aware. Thanks for sharing!
> Recently I came across this tweet containing the image below and it made me laugh … albeit not in the original way the tweet intended. The tweet was joking that “Anyone is able to open a GeoJSON file” and included the Microsoft Word screen shot seen below as a response to someone else tweeting that “Handing in a project as @GeoJSON. Let’s see if I get the usual “I can’t open this file” even though […]”. What was funny to me was seeing longitude and latitude coordinates stored with 15 decimal digits right of the decimal point.
