Coordinates Filter

nickthesloth7 years ago

Hi,

I have the following in my config on 3.8, but when parked, my tracker is still jumping around slightly:

        <entry key='filter.enable'>true</entry>
        <entry key='coordinates.filter'>true</entry>
        <entry key='coordinates.error'>50</entry>

Do I need to change anything else to get this working?

Thanks

Anton Tananaev7 years ago

Yes, you don't even need "filter.enable".

nickthesloth7 years ago

Okay, removed that and restarted, but its still moving about.

Anton Tananaev7 years ago

Is movement more than 50 meters?

nickthesloth7 years ago

Well, unless the scale of the map is really out, it really shouldn't be. I can try making the value higher and see if that changes things.

Will I see the coordinates being filtered in the log file? I suppose I can just watch them in the DB for a bit and see if they stay the same otherwise?

Anton Tananaev7 years ago

Yes, you can check database. Have you restarted service after changing config?

nickthesloth7 years ago

Yes, restarted after each change.

nickthesloth7 years ago

Okay, set it to 500, but it's still moving slightly.

Anton Tananaev7 years ago

Sorry, there were changes to coordinates filtering in 3.8. You need to set "coordinates.minError" parameter instead of "coordinates.error".

nickthesloth7 years ago

Aha, sorted!

Thanks! :)

gustavofarias7 years ago

What's the difference between "coordinates.filter" and "filter.distance"?

Anton Tananaev7 years ago
gustavofarias7 years ago

Of course I read that. Still not clear.

"Replaces position coordinates if it changes less than..."
Replaces with what? Is this a filter or a replacer?

Also, after you answered this with "yes" I got more confused, because the documentation for coordinates filter also mentions parking:
"Helps to avoid coordinates jumps during parking period."

Anton Tananaev7 years ago

coordinates.filter - replaces coordinates with last known
filter.distance - filters out the whole record

gustavofarias7 years ago

I would put these 3 words "with last known" in the documentation.