Filter future positions doesn't seem to work

Hello Anton,

Yesterday I had a strange behavior, my config have <entry key='filter.enable'>true</entry> and <entry key='filter.future'>300</entry> and a position with fix time in 2035 and wrong position data has been recorded.

Do you know why ?

It only works for new data, not old.

Yes but this setting is activated since maybe one year :/

This parameter didn't exist one year ago. What version of Traccar are you using? If not latest, that's your problem.

Sorry, maybe not year but months for sure.
I'm using traccar 3.17 because I'm afraid of this for updating to Traccar 4.0 : "The drawback is that is caused vast code changes for all protocols and might not be as stable at first."

Future filtering should work on 3.17. If it doesn't, it means that you misconfigured something.

Can I show you my other settings so you can check if I misconfigured something ?

Here is my filter configuration

<entry key='filter.enable'>true</entry>
<entry key='filter.invalid'>true</entry>
<entry key='filter.zero'>true</entry>
<entry key='filter.future'>300</entry>
<entry key='filter.skipAttributes.enable'>true</entry>
<entry key='filter.skipAttributes'>alarm</entry>

Maybe an alarm in the future has come ?

Possibly.