Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Allow setting of custom Location Engine #8668

Closed
cammace opened this issue Apr 6, 2017 · 2 comments
Closed

Allow setting of custom Location Engine #8668

cammace opened this issue Apr 6, 2017 · 2 comments
Assignees
Labels
Android Mapbox Maps SDK for Android

Comments

@cammace
Copy link
Contributor

cammace commented Apr 6, 2017

Currently, it doesn't appear to be a way to use a custom location engine rather then the Lost location provider.

cc: @mapbox/android

@cammace cammace added the Android Mapbox Maps SDK for Android label Apr 6, 2017
@cammace cammace added this to the android-v5.1.0 milestone Apr 6, 2017
@Guardiola31337 Guardiola31337 self-assigned this Apr 7, 2017
@Etienne-io
Copy link

Is this issue mean that it will be possible to use MyLocationView without activate the LocationEngine ?

@zugaldia
Copy link
Member

@emerciercontexeo It means that you can provide your own LocationEngine implementation, which can use another location provider, or do nothing at all, depending on your app needs.

You can see two examples in this test app. GoogleLocationEngine.java uses Google Play Services, while MockLocationEngine.java simply mocks locations and doesn't do any real location tracking.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Android Mapbox Maps SDK for Android
Projects
None yet
Development

No branches or pull requests

4 participants