Results worse after filtering with kalman. about mad-location-manager HOT 8 OPEN

Approach is definitely correct.
But need more info about your setup and filter settings.

from mad-location-manager.

I use only the kalman filter implementation from this repo. So basicaly i initialized filter with first point data, then I predict with acceleration, and update with gps data.
No additional settings.
Maybe the problem is, I use wrong standard deviation for acceleration and position.
Or the accelerometer is not calibrated?

from mad-location-manager.

Maybe you use uncalibrated accelerometer.
There are 2 variants of using filter here :
Use speed readings from GPS receiver or not use.

Also this sensor bosch bno055 - did you calibrate it? I mean it uses magnetometer and when you use magnetometer you should compensate soft and hard iron distortions there .

from mad-location-manager.

That's why I asked about your setup :)

from mad-location-manager.

I'm using variant with speed from GPS. The magnetometer is calibrated according to my mechanical compass.
Maybe frequency is the issue? It's only 5hz.

from mad-location-manager.

No, it should not be an issue.

from mad-location-manager.

So here is what i found, looking at the path.

On the image above we can clearly see that the path is not correct, it should by along a street.
And when the filter is updated with correct gps data, it's ignored and getting even worse.
So the filter is not filtering at all. Prediction works, but updating not.
Any ideas ? :D

from mad-location-manager.

Sensor is bosch bno055 it has a drawback, it cannot accurately maintain orientation during prolonged accelerations and vibrations, these are problems of its fusion algorithm, it may be worth trying a more reliable sensor.

from mad-location-manager.