Location not getting correctly. about mad-location-manager HOT 13 CLOSED

@Lezh1k about the (0,0) coordinates. I was getting those too. For me the reason was that i was using an emulator without sensors. So i was only getting sdi from onLocationChange and so the KalmanFilter was never "initialized" with a Sensor event. I fixed it as explained here #52 (comment)

from mad-location-manager.

Hello. :)

Please try to set geohash default precision to 6 and geohash default min point count to 2.

from mad-location-manager.

Ok. I'll do it. And I have an other doubt, From the documentation and sample I found that we can filter the obtained location using
m_geoHashRTFilter.filter(location);

And the filtered location from it by executing the following code.
` List routeFilteredWithGeoHash = new ArrayList<>(m_geoHashRTFilter.getGeoFilteredTrack().size());

    for (Location loc : new ArrayList<>(m_geoHashRTFilter.getGeoFilteredTrack())) {
        routeFilteredWithGeoHash.add(new LatLng(loc.getLatitude(), loc.getLongitude()));
    }`

And I'm expecting the last location that I fed for filtering will be available as the last entry in this list (list here: routeFilteredWithGeoHash ). Is that correct?

Or there is anything more to it?

from mad-location-manager.

So I had a trial run based on this code and assumption, and this is the result. I took the same route (one in the question)

from mad-location-manager.

As far as I can see, you are saving KalmanFiltered locations in locationChanged() method, not GeohashRTFilter filtered. So I don't think, that you are losing a lot of data because of geohash precision and geohash min point count parameters.

from mad-location-manager.

I have tried both of them, for geoHashing along with the above mentioned code I have updated my locationChanged() method as

@Override public void locationChanged(Location location) { if (location != null ) { m_geoHashRTFilter.filter(location); List<LatLng> filteredLocation = getFilteredLocation(); if (!filteredLocation.isEmpty()) { int len = filteredLocation.size(); DataManager.getInstance(LocationService.this) .saveDeviceTracking(filteredLocation.get(len - 1).getLatitude(), filteredLocation.get(len - 1).getLongitude()); } } }

` public List getFilteredLocation() {
List routeFilteredWithGeoHash = new ArrayList<>(m_geoHashRTFilter.getGeoFilteredTrack().size());

    for (Location loc : new ArrayList<>(m_geoHashRTFilter.getGeoFilteredTrack())) {
        routeFilteredWithGeoHash.add(new LatLng(loc.getLatitude(), loc.getLongitude()));
    }
    return routeFilteredWithGeoHash;
}`

where LatLng is a POJO that I have created.

But even though the result is not so trust worthy.

from mad-location-manager.

I still can't understand what's happening.
Do you receive some wrong coordinates (like on this https://user-images.githubusercontent.com/30405024/52267760-e7da8300-295f-11e9-95b9-448b402939fa.png screen) ?
Or you don't receive wrong coordinates, but the route contains small amount of coordinates ?

Sorry, can't get it.
Also have you tried our example application on this route?

from mad-location-manager.

At first without using geohash I got only a few but correct coordinates.

Later I have used geohashing with precision to 6 and min point count to 2.
It has few more correct points compared to the first one, but surprisingly I'm getting some points from wrong coordinates -one from Africa :(

from mad-location-manager.

Now I got it. )) Thanks.

from mad-location-manager.

Seems you've got (0, 0) coordinate? I'll look at this today :)
What about our demo application ?

from mad-location-manager.

No, it is not (0,0) coordinate. I couldn't test with your demo app, I'll check it anyway.

from mad-location-manager.

I mean that there is (0, 0) somewhere compensated by Kalman filter.
Can you share your project? I'll try to reproduce :)

from mad-location-manager.

Check your GPS frequency I bet it's 1Hz or bellow and you are not having enough points GEOHASH_DEFAULT_MIN_POINT_COUNT for the precision GEOHASH_DEFAULT_PREC.

Try walking instead of driving a car.... lol

from mad-location-manager.