Understanding coordinates.filter

[gpproton]

Hi @tananaev,

I've been having issues with jumping coordinate and i'm looking to use coordinates.filter but i don't clearly understand the conditions like after a tracking device lose power for a long time like days and was powered on later, i'd like to know how it will be handled.
because i feel that if it keeps filtering out the new positions because of the jump correct information will be lost because of this. please enlighten me.

[Abyss777]

I could try to clarify

coordinates.filter do not filter out new position, it can only replace coordinates in some cases.

There are two configurable parameters: coordinates.minError and coordinates.maxError both can be omitted and both are in meters.

minError - used for avoid jumping during a parking period
maxError - used for avoid jumping to (0,0) coordinates or other too far coordinates.

Lets set term distance.It is calculated distance (in meters) between new received position and last (previous) position.

If both parameters are configured and minError < distance < maxError new positions coordinates is leaved as is. Also coordinates leaved as is if last position is not valid.

If distance <= minError then new position coordinates will be replaced from last position. It helps to avoid jumping on parking.

If distance >= maxError and new position not valid then new position coordinates will be replaced from last position. It may happen if device send some wrong (0,0) coordinates after switching on before find satellites.

You should practically find optimal values for parameters, start minError from 50-100 meters and I think maxError should be in thousands kilometers (millions meters).

[gpproton]

Ok thanks bro, i'm testing it now.

[Phantomatz]

Hello Abyss,
currently I am only trying to filter my jumping entries of my TK5000 XL (Port 5032 - Wondex protocoll) Tracker with the filter options and currently trying to modify the FilterHandler.java.

However, where are the parameters located you are referring to ? coordinates.filter etc....

Maybe it would make sense to fix it in the wondex protocoll already ?

I have no idea what might be the better solution.

[tananaev]

Parameters can be added in the config file.

There is no issue with Wondex protocol, so there is nothing to fix on the server side.