Hey!
I have noticed that the "wrong" locations dont have a speed meaning there is no way to use maxSpeed. Can we use something else to filter them out?
2024-05-03 13:36:37 INFO: [T8f4383f7: huabao < 195.226.133.46] 7e0200003f0140733280780b470000000000080003030d876000674fb20029014d00d6240503213558010400000744e102007d02f>
2024-05-03 13:36:37 INFO: [T8f4383f7] id: 014073328078, time: 2024-05-03 13:35:58, lat: 51.21827, lon: 6.77061, speed: 18.0, course: 214.0
This a valid location
And this is a wrong one
2024-05-03 13:36:45 INFO: [T65acc213: huabao < 195.226.133.62] 7e0200005c0140733036000007000000000000000101590203000000000000000000002405032136440104000005ebe10200905d0>
2024-05-03 13:36:45 INFO: [T65acc213] id: 014073303600, time: 2024-05-03 13:36:44, lat: 22.61044, lon: 0.00000, course: 0.0
What would be the best way now to filter it?
If you read the documentation carefully, you'll know that maxSpeed filtering doesn't actually use speed value.
did you manage to fix your issue yet
Hey!
I have noticed that the "wrong" locations dont have a speed meaning there is no way to use maxSpeed. Can we use something else to filter them out?
This a valid location
And this is a wrong one
What would be the best way now to filter it?