Invalid coordinates not being filtered

Andy6 years ago

Hi,

I have the following lines in my config in relation to coordinate filtering, however I am still seeing positions marked as "NO" in the "valid" column when running reports & coordinates caused by GPS drift. Can anyone help me work out what I'm doing wrong? I have restarted traccar server after the config change.

<entry key='filter.enable'>true</entry>
<entry key='filter.invalid'>true</entry>
<entry key='filter.zero'>true</entry>
<entry key='filter.duplicate'>true</entry>
<entry key='filter.maxSpeed'>25000</entry>
<entry key='filter.skipLimit'>28800</entry>
<entry key='coordinates.filter'>true</entry>
<entry key='coordinates.minError'>5</entry>
<entry key='event.motion.speedThreshold'>0.11</entry>
Anton Tananaev6 years ago

Filtering will only work for new data. You can still see invalid positions in the report from the time before you added filtering.

Andy6 years ago

Hi Anton, thanks for your reply. I appear to still be getting coordinates logged that have "No" in the valid field in the reports section, the most recent were logged this morning, several days after filtering was configured & the server restarted. Do you know why this might be?Is there something wrong with the config above?

Thanks,

Andy

Anton Tananaev6 years ago

Have you checked logs? Is anything filtered?

Andy6 years ago

I'm seeing lots of filtered messages, actually looking at the reports for the devices I have in at the minute, all that is making it through are ones wrongly reporting altitude & marked as invalid. I guess these don't meet any if the filter parameters?

Anton Tananaev6 years ago

OK, please provide log fragment example (where message is filtered) and then report showing same message.

Andy6 years ago

Hi Anton,

Here is the snippet from the log, it doesn't flag it as filtered and treats it as normal but in the report section in the web itnerface it says "NO" in the valid column. 

2018-06-27 07:50:56  INFO: [087083C9] connected
2018-06-27 07:51:08 DEBUG: [087083C9: 5093 < XX.XXX.XXX.XX] HEX: 
<removed>
2018-06-27 07:51:08  INFO: [087083C9] id: 9051103205, time: 2018-06-27 07:51:07, lat: XX.XXXXX, lon: -X.XXXXX, course: 0.0

The HEX decoded is (i have blanked my coordinates):

[SG*9051103205*00B0*UD,270618,065107,V,XX.XXXXXX,N,X.XXXXXX,W,X.XXXX,000,99,00,20,100,0,50,00000000,6,1,234,30,2302,4398,127,2302,253,124,2302,4395,123,2302,37958,122,2302,15170,122,2302,4727,120,,00]

Here is the screenshot from reports, these 2 are from today. Everything marked as invalid in reports that is making it through is reporting an altitude of 99, the coordinates are correct.

Image