Avoid jump position in a basement or filter by georeference, Suddenly position jump.

Hi All, I am wondering if is possible to avoid jump position or filter position when device is in a georeference please see the image below:

In this point device is in the basement and the position is fine:

But suddenly it jump to another incorrect position:

Could you advise for solution i would like to keep the location when device enter to georeference or avoid these jumps when car is parked.

I added some filters but it didn't work:

    <entry key='filter.enable'>true</entry>
    <entry key='filter.outdated'>true</entry>
    <entry key='filter.invalid'>true</entry>
    <entry key='filter.zero'>true</entry>
    <entry key='filter.distance'>10</entry>
    <entry key='filter.duplicate'>true</entry>
    <entry key='filter.accuracy'>100</entry>
    <entry key='filter.maxSpeed'>130</entry>
    <entry key='coordinates.filter'>true</entry>
    <entry key='coordinates.minError'>20</entry>
    <entry key='coordinates.maxError'>20</entry>
    <entry key='filter.future'>86400</entry>
    <entry key='status.timeout'>120</entry>
    <entry key='filter.skipAttributes.enable'>true</entry>
    <entry key='filter.skipAttributes'>alarm,ignition,result,status,command</entry> 

We don't have a geofence-based filtering.

<entry key='coordinates.maxError'>20</entry>

does not make sense. You would expect it to be in thousands of meters.

Hi track-trace whats is the recommended value?

There is no recommended value. It will depend on your specific situation. But you need to understand what that configuration does before you set it.

coordinates.filter config
Replaces coordinates with last known if change is less than a 'coordinates.minError' meters or more than a 'coordinates.maxError' meters. Helps to avoid coordinates jumps during parking period or jumps to zero coordinates.

coordinates.minError config
Distance in meters. Distances below this value gets handled like explained in 'coordinates.filter'.

coordinates.maxError config
Distance in meters. Distances above this value gets handled like explained in 'coordinates.filter', but only if Position is also marked as 'invalid'.

I would say with coordinates.maxError you cant expect the position to be very accurate (since this works for positions that are marked as invalid). Thus it would be based on LBS or Wifi (geolocation). So you could expect that the distance between these invalid positions would be much bigger compared to valid gps positions.

You could also ignore invalid positions (geolocation).
But if you would have a tracker that reports besides gps both lbs and wifi it could be fairly nice with geolocation (rather accurate).