filter distance

When I remove the below config, the server does update position.

 <entry key='filter.distance'>50</entry> 

But when I add this filter the server does not update position.
Also I need this filter, because when I pull a route report, data of same position is uploaded too much if a car is parked off.
Im running lastest version 4.15

What is the question or problem? Are you saying that data is filtered incorrectly? If that's the case, we would need some evidence of that.

If I remove this config line
<entry key='filter.distance'>50</entry>

I get this in my route report if car is park. continuous location upload.
https://drive.google.com/file/d/1-UtWpBEN_do9Pewa568SxkeLseI-mL6n/view?usp=sharing

but if I add this <entry key='filter.distance'>50</entry>
my unit dont update.
I dont want continous update location when vehicle is parked.
any help will do.

Has something been filtered incorrectly?

If I add this distance filter as above, logs dont give latitude and longitude. Below screenshot of logs.

https://drive.google.com/file/d/1rD05_SYb2mqNExpLRLq6mc61bhMju7Ck/view?usp=drivesdk

No answer?

are we able to do a filter.distance as a server attribute

I suggest patch release for 4.15 is required as certain bugs on filter affecting and pushing us to downgrade to 4.14

When I upgrade to lastest version 4.15 , I have to remove this <entry key='filter.distance'>50</entry> , then only my units starts to respond with correct location. otherwise unit stays at last known location with no movement even though vehicle is in motion.
I rolled back to 4.13 and all is good. anybody else experiencing same issue.

I have this issue too.
My Test:
fresh “out of the box” server installation; standard config file;
import old mariadb data;
set Apache reverse https proxy,
All devices upload gps data and server update positions.

But Issue when I add to config:

<entry key='filter.distance'>50</entry>
<entry key='coordinates.filter'>true</entry>
<entry key='coordinates.minError'>50</entry>
<entry key='coordinates.maxError'>100</entry>

All devices are frozen in last known position.
In Log file there was nothin “strange”, only received gps coordinates are “locked” in exact last place.
Removing filter let server works fine.

Your coordinates.maxError is way too low.

Thanks Anton.
I’ll try something like 300/350….

I think you're misunderstanding this configuration option. It usually should be thousands.

Ah ok….
My goal is stop “jumping” while parking.
I think it’s wrong way….

That's what the coordinates.minError can be used for.