Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of kCLLocationAccuracyBestForNavigation #12

Closed
jeffbailey opened this issue Jan 23, 2018 · 1 comment
Closed

Use of kCLLocationAccuracyBestForNavigation #12

jeffbailey opened this issue Jan 23, 2018 · 1 comment

Comments

@jeffbailey
Copy link

First of all, thanks very much for sharing this with the world. It works great an allows to smooth workout routes. However, I noticed the locations it creates uses kCLLocationAccuracyBestForNavigation for horizontal and vertical accuracy. That actually makes the location invalid since it has a value of -2 and Apple considers anything less than zero to be invalid. I changed it to the following:

let kalmanCLLocation = CLLocation(coordinate: CLLocationCoordinate2D(latitude: lat,longitude: lon), altitude: altitude, horizontalAccuracy: self.previousLocation.horizontalAccuracy, verticalAccuracy: self.previousLocation.verticalAccuracy, timestamp: previousMeasureTime)

@Hypercubesoft
Copy link
Owner

Hi @jeffbailey
Thank you for contacting us, we have found the problem and we have fixed it. Please pull the latest version and let us know if you have some problems again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants