Poor documentation about mad-location-manager HOT 5 CLOSED

Hello :)

1. Those parameters are used in R matrix as gain coefficients. If you know that your velocity (from gps receiver) is (let's say 2 times) more reliable than position you can set those parameters like 0.5 for velocity and 1.0 for position for example.

2. For geohash with precision 8 radius is ~±0.019km. Point count is used for point validation. For example if you have received points_count sequenced points with same geohash - this point is valid. If you have received less then points_count - this point isn't valid yet.

DistanceGeoFiltered - distance filtered with geohash filter.
DistanceAsIs - uses all received points.

HP suffix means high precision. That means that for distance between two points we use more accurate algorithm.

4. Seems like it's bug. It should return false when it isn't started :)

Thank you for your interest.

from mad-location-manager.

I have tested the GeohashRTFilter with different parameters, I think the radius of "merging area" (for hash length = 8) is much less than 19 m. In my app 2 points at a distance of 5 meters were not merged.

I have also tested the filter with parameters of 8-2 and 7-2 (hash length and min point count). Results are not acceptable, too many points were lost because of driving speed

from mad-location-manager.

#   km      
0   ± 2500
1   ± 630
2   ± 78
3   ± 20
4   ± 2.4
5   ± 0.61
6   ± 0.076
7   ± 0.019
8   ± 0.0024
9  ± 0.00060
10  ± 0.000074

We start from 0 because of fast geohash implementation.
For our solution I used prec, points = 6, 3 . It works fine for cars in town (with traffic jams) :)

from mad-location-manager.

Sorry. 7, 2 for cars.

from mad-location-manager.

Update is on the way.

from mad-location-manager.