Skip to content

Conversation

@kevinkreiser
Copy link
Contributor

Use nav native 3.1.1 to do small forward prediction to counter-act location services lag. Let me know if we should make a constant for this and indeed where such constants would live!

Copy link
Contributor

@Guardiola31337 Guardiola31337 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome @kevinkreiser

I've left a minor comment after that we can :shipit:

Thanks 🙏


synchronized NavigationStatus retrieveStatus(Date date) {
// We ask for a point slightly in the future to account for lag in location services
date.setTime(date.getTime() + 1500);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about passing the lag as a parameter of retrieveStatus so it can be custom? And then we can add a new option in MapboxNavigationOptions with its corresponding default values (constant in NavigationConstants).

@Guardiola31337
Copy link
Contributor

Other than a couple of formatting nit picks was 💯 You got it!

Thanks @kevinkreiser looking forward to test it out!

Copy link
Contributor

@Guardiola31337 Guardiola31337 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Going ahead and merging here.

Thanks again @kevinkreiser

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

Successfully merging this pull request may close these issues.

2 participants