Approximative locations reported with precision = 0 m

[gaialabs]

Hello,

I've a lot of inaccurate locations sometimes hundreds of kilometers away. It looks like that the problem is when my device doesn't get a precise GPS location and is using GSM/LTE network for this purpose. And the issue is that these locations have a precision of 0m, which means I can't exclude them.

Here's how it looks like in the owntracks web application:

The location where I was is in the red circle. And you can see a lot of points which seems located at the location of GSM/LTE antennas of my operator. We can also see that when the device has a precise GPS location, the issue doesn't occure.

Is there anything I can do ? Could it be a configuration error ?

Kind regards.

• App build number: 2.5.2
• Android version: 13
• Device: Samsung Galaxy A32 5G
• Installation source: Google Play

[growse]

Oof, that's rough. I've never seen a device post inaccurate locations with an accuracy of "0" before, that feels like a Samsung bug.

Tricky to know what to do with this one. A quick fix might be to add an advanced config item to filter out locations that come through with an accuracy of 0. The problem there is that if your device is delivering all non-GPS-derived locations with acc=0, that'll effectively mean that the only locations you'll get are where there's a GPS signal.

Would that help?

[gaialabs]

Thank you for your quick reply. Actually I was wrong. I took the altitude of 0 m for the accuracy. My bad.

So I can use the "inaccurate location" parameter which I set to 100 m and that would probably make it.

So, sorry for disturbing for nothing :-)

[growse]

No problem at all. Going to close for the time being, but feel free to re-open if you think there's an enhancement that'd be useful here.