determine data correctness
Categories
(Location :: General, task, P3)
Tracking
(Not tracked)
People
(Reporter: willkg, Unassigned)
References
()
Details
MLS has a lot of data. Currently, we have no way of measuring the correctness of the data, correctness of geolocation query results, or whether the correctness is getting better or worse.
This bug covers determining data correctness.
|
Reporter | |
Comment 1•5 years ago
|
||
We've had a few discussions about "correctness". It means different things in different contexts.
In one context, "correctness" means "a geolocation query gets the same result between MLS and GLS". Determining correctness there probably involves running an experiment on a user population that queries MLS and GLS and reports back either a "they're the same/different" or a "they're off by x amount" or something like that.
If we want to do this, then I think it's pretty straight-forward experiment stuff. I was told to talk to Shell.
I don't know how much engineering and calendar time this entails. Maybe a month?
Another way of defining "correctness" is "how far off from reality is the geolocation query result?" We could run a different kind of experiment where Firefox determines the location from a geolocation query to MLS, shows a map (open street maps?), and asks the user where the user actually is. Then it reports back some kind of "they're the same/different" or "off by x amount" or something like that.
I'm not clear on the next step for this. It needs a user interface. It probably needs localized strings. This is probably a big project.
Are there other things we can do to determine data correctness or something that can act as a proxy for correctness?
|
||
Comment 2•5 years ago
|
||
Description
•