questions on some logic used in code about mad-location-manager HOT 1 OPEN

@mkandulavm

Hello.

1. It means that we trust position measurement 10 times less than we trust velocity measurement. (as bigger value in R matrix as less we trust this measurment. and the oposite is right too).

It's not totally random but still very inaccurate value. I found somewhere that velocity received from GPS sattelite based on Doppler effect and it's ten times more accurate than coordinates. That's why I used this coefficient.

I'm not sure how to improve these values, sorry.

2. Accelerometer deviation can be found in 2 ways. First - you can get it from documentation to your particular accelerometer. Second - you can ask user and apply calibration step. I'm not sure if calibration step in this repo or not. But the princip is very simple. You need to log accelerometer measurements during 1 minute (or 30 seconds) when your phone/device is laying without movement. Expected measurement for Z axis is 9.81, and for X and Y - zeroes . SO the mean value for X and Y will be our accelerometer deviation. For Z axis you need to subtract mean value from 9.81 .

3. It's better to call predict every time you get measurements from sensor.

Thank you for interest. The library is outdated so I'd recommend to use it as base for your solution.

from mad-location-manager.