Traccar map showing wrong position

Anton Tananaev8 years ago

So you don't want to do it yourself and you are expecting me to do it for you?

freebie8 years ago

I don't mean that. I have gone through the logs and I can't differentiate the messages at any time starting from midnight so I don't know how to pinpoint the message you require. Should I be looking for any anomaly in particular?

Anton Tananaev8 years ago

You need to find a message with matching coordinates and speed value. Also, minutes would probably match as well. Simple text search through the log might help.

freebie8 years ago

Found it. It was from the previous day. Speed doesn't match but the coordinates are similar.

2017-03-16 16:45:02 DEBUG: [4D0AF84C: 5017 < 105.58.129.144] HEX: 24504f532c333531313330313135332c3136343435392e3030302c562c303035392e373430312c532c30333730342e383632302c452c34362e35372c3230342e31342c3137303331372c2c2c412f30303030302c30303030302f302c302c302c302f32333730302f2f0d0a
2017-03-16 16:45:02  INFO: [4D0AF84C] id: 3511301153, time: 2017-03-17 16:44:59, lat: -0.99567, lon: 37.08103, speed: 46.6, course: 204.1
Anton Tananaev8 years ago

Similar? As far as I can see, nothing matches.

freebie8 years ago

Is there a way to set as invalid, any position data from the tracker that shows a future date and time?

Anton Tananaev8 years ago

It's possible to enable filtering to ignore locations with future time.

freebie8 years ago

Ok. Please guide me on how to do that. I think that would solve my issue.

Anton Tananaev8 years ago

Read documentation and search on forum and GitHub. It has been discussed before.

freebie8 years ago

I have searched around and have come up with this:

I have added the following lines to default.xml

<entry key='filter.enable'>true</entry>
<entry key='filter.future'>true</entry>

Is this the correct implementation of future.filter.

I ask coz I'm a newbie at this.

Anton Tananaev8 years ago

No, it's not. Where did you find it?

freebie8 years ago

I used an old forum post where you mentioned:

"You can enable filtering in the config file:"

<entry key='filter.enable'>true</entry>
<entry key='filter.duplicate'>true</entry>

I figured that the same applies to filter.future.

Please advise.

freebie8 years ago

In another post you mentioned:

"There will be a change in filter.future. Currently it's just a boolean flag (true or false). In the next version it will take a number."

Has it changed to a number?

Anton Tananaev8 years ago

Yes, it has.

freebie8 years ago

Ok. How do I use it? I cant find any description in documentation.