Re:Kansas couple sues IP mapping firm for turning their life...
by mnw21cam on Friday August 12, 2016 @06:07AM
(#12274387)
And of course, nobody has thought of the possibility of including an accuracy radius with the position, so instead of having a point saying "It's here", you have "It's anywhere within this area".
Re:Kansas couple sues IP mapping firm for turning their life...
by MichaelGG on Friday August 12, 2016 @07:21AM
(#12274679)
Anyone that's driving out to a farm without checking other data sources will probably just ignore the accuracy radius.
Re:Kansas couple sues IP mapping firm for turning their life...
by TeMPOraL on Friday August 12, 2016 @06:22AM
(#12274432)
It's the same with site metrics, or sensors in IoT - your measurement isn't X, it's X +/- Y, with some measurement error distribution.
Re:Kansas couple sues IP mapping firm for turning their life...
by sseveran on Friday August 12, 2016 @12:53PM
(#12277073)
I have not used MaxMind but with another geo data provider in addition to the centroid it returned the shape and the type of match it was (exact address, city, county, state, country,etc...). So you know whether the IP has an exact address match or not. But many application developers probably chose to ignore the complexity as that might be easier.
Re:Kansas couple sues IP mapping firm for turning their life...
by ghaff on Friday August 12, 2016 @08:42AM
(#12275100)
It may be a terrible approach in your view but it's essentially universal and is often the best one. If I ask just about any database for the Lat/Long of some city, it's going to return the location of some approximation for the center of the city--which may be a park, a house, or the middle of a river. It's not going to, nor should it, tell me "invalid question" because the city (or really any address within that city) isn't really represented by a single Lat/Long point.
Re:Kansas couple sues IP mapping firm for turning their life...
by ghshephard on Saturday August 13, 2016 @12:38AM
(#12280299)
I've worked on a number of applications, where we need to make a decision as to what the long/lat will be of "Unknown" - and we always pick something that is guaranteed to throw a flag for downstream consuming applications.
Recognizing how your data will be used, and taking some precaution to ensure that it doesn't result in scenarios described in the article is quite often fairly straightforward. (As evidences - The article itself made it clear that when they don't know the actual location, they have changed the long/lat to return a value in the middle of a lake to avoid this sort of problem in the future).
This makes it much easier for downstream application developers to filter out "Invalid" addresses, and simply eyeballing them on a map makes it clear what the "Invalid" value is.