Re:Is it time to stop using sentinel values for null / “NA” ...
by jimktrains2 on Monday June 05, 2023 @07:22PM
(#36205733)
I was responding to the idea that it's good nothing is at null island because it's a default. I was showing that there are aome default locations that have people and there are consequences to that.
Re:Is it time to stop using sentinel values for null / “NA” ...
by LorenPechtel on Tuesday June 06, 2023 @08:25PM
(#36221057)
But your case isn't a null, but rather horribly poor accuracy.
Re:Is it time to stop using sentinel values for null / “NA” ...
by jimktrains2 on Wednesday June 07, 2023 @07:00AM
(#36225323)
(0,0) isn't null either.
All location fixes inherently have a precision component and that routinely gets ignored. There's one tower that can reach the phone, the phone must be somewhere within the footprint of the tower. If the phone didn't supply more detailed info that's the only thing you can determine. The true area is the footprint but it gets reduced to a location and a precision--which maps it to a dot and a circle. A one-tower location fix will give a circle of uncertainty that extends off the visible map in most cases and humans ignore it. (The center of the US problem is a bit different but it's the same basic concept.)
What I think they need to do is prohibit any system from showing the central dot (or any equivalent to that) when the precision is too low. Only render the zone of uncertainty and only at a map scale where you see the whole zone, attempting to zoom beyond that gets you a message that the location can't be determined more accurately, do not try to find the center of the zone.