villoren / kalmanlocationmanager Goto Github PK

Great work you have!
Could it have support for fused location ?

Curious about why this specific check exists here: https://github.com/villoren/KalmanLocationManager/blob/master/app/src/main/java/com/villoren/android/kalmanlocationmanager/lib/LooperThread.java#L219 :

        public void onLocationChanged(final Location location) {
            ...
            // Update last location
            if (location.getProvider().equals(LocationManager.GPS_PROVIDER)
                    || mLastLocation == null || mLastLocation.getProvider().equals(LocationManager.NETWORK_PROVIDER)) {

                mLastLocation = new Location(location);
            }
           ...
        }

Specifically, why we want to update the mLastLocation if the previous provider was NETWORK_PROVIDER? Is it because NETWORK_PROVIDER is less reliable and thus we want to make sure we're keeping up with the latest?

Thanks!

Hello, my name is Kritika Sharma and I am in the middle of making a project in which I have to implement a kalman filter. The application will take the GPS coordinates(lat,long) in set interval of time and will compute the predicted velocity and I am not able to write its code. Can you please help me, it'll be a great help. My email id is [email protected].

Great work on this!

Could you publish it as a library on jCenter? I know it's not necessary for use...

build.gradle:

dependencies {
    compile 'com.android.support:appcompat-v7:23.1.1'
    compile 'com.villoren:kalmanlocationmanager:1.0.0'
}

With a simplified import:

import com.villoren.kalmanlocationmanager.KalmanLocationManager;

Thank you!

Every time I call update function and predict function, I find that the value returned by getAccuracy is larger than previous, even new location's accuracy is stable. I don't know why, I tried to read all logics in Tracker1D.java but finally I failed.

Following is line 324 from Looper thread

location.setAccuracy((float) (mLatitudeTracker.getAccuracy() * DEG_TO_METER));

My question is why you are taking into account the latitude accuracy? why not both lat and lng?

Hi, thank you for sharing this wonderful work! I am new here. And I am still confused that how you specify the value of noise such as COORDINATE_NOISE and ALTITUDE_NOISE etc. Thank you.

Unfortunately, I will have to remove the google maps api key I shared in this repo:
AndroidManifest.xml#L62

You can still provide your own key if you want.
Ideally, I'd rather migrate to Open Street Maps, as to keep this example as open sourced as possible. But that's going to take time I don't have right now.

Sorry I can't do this run out-of-the-box anymore. At least not in the short term.

Here's the announcement I got in my mail:

Hi,

Today we are announcing important changes, including our new name - Google Maps Platform, a simplified product structure, pay as you go pricing for all, and more. Please take a few minutes to review the announcement to familiarize yourself with the upcoming changes.

We would like to highlight a few updates that may impact your implementation. Beginning June 11th, we are launching our new pricing plan and providing all users access to support. We’ll continue to offer a free tier — all developers will receive $200 of free monthly usage of our core products.

In addition, this change will require you to enable billing and associate it with all of your Google Maps Platform projects. Creating a billing account helps us better understand your usage so we can continue developing helpful products. It also allows you to scale easily with less downtime and fewer performance issues if your product grows beyond the $200 of free monthly usage. For additional visibility and control you can set daily quotas or billing alerts.

How does this affect your current projects?

Project: Kalman Location (642491349506)

Based on your project usage over the last 3 months and our new pricing plan, we estimate that your new cost will be less than $200 a month and will be covered by our $200 monthly free credit. This estimate does not include usage from other projects or keyless implementations.

We want to support you along the way. Please read our Guide for Existing Users to understand how these changes may impact your account and what steps you need to take.

Thank you for using Google Maps Platform.