Releases: maplibre/maplibre-navigation-android
Releases · maplibre/maplibre-navigation-android
4.0.0
3.0.1
What's Changed
- Improve contribution docs + clean up AndroidManifest.xml by @ianthetechie in #97
- SDK Checks and waypointIndices by @Archdoog in #99
- Fix snap-to-route crash by @Fabi755 in #106
- Update dependencies by @Fabi755 in #109
- Making TurnLaneViewData Public by @Younes-Charfaoui in #113
- Make some navigation classes and methods public for extended usability by @BackPackerDz in #112
- Fix leaking MapView due to annotations plugin by @ahmedre in #115
- Example that communicates directly with a Valhalla backend by @eikes in #119
- Add sponsor link to the repo by @ramyaragupathy in #121
- Fix NullPointerException in ManeuverView by @juschmitt in #123
- Prepare release 3.0.1 by @Fabi755 in #124
New Contributors
- @ianthetechie made their first contribution in #97
- @Archdoog made their first contribution in #99
- @Younes-Charfaoui made their first contribution in #113
- @BackPackerDz made their first contribution in #112
- @ahmedre made their first contribution in #115
- @eikes made their first contribution in #119
- @ramyaragupathy made their first contribution in #121
- @juschmitt made their first contribution in #123
Full Changelog: 3.0.0...3.0.1
3.0.0
What's Changed
- BREAKING CHANGES:
- The navigation models DirectionsResponse and the classes used within this class have been moved the Maplibre-Java to the navigation-core. So the core does not need a dependency to the outdated Maplibre-Java dependency anymore.
- When you pass a DirectionsResponse or DirectionsRoute to the navigation-core, please be aware that you convert it to the local model first. If you are using Mapbox or the GraphHopper navigation endpoint, you can simply use fromJson for parsing.
- You could use something like this:
com.mapbox.services.android.navigation.v5.models.DirectionsResponse.fromJson(JSON_STRING_FROM_API_RESPONSE);
- You could use something like this:
RouteFetcher
has been split toRouteFetcher
andMapboxRouteFetcher
. The latter is in the ui module now.NavigationRoute
has been moved to the ui module.RouteProcessorBackgroundThread.Listener#onCheckFasterRoute
was removed as this relied on parts of the RouteFetcher that don't work anymore in the core. If you need this feature, you implement this in the UI code.- This resulted in some smaller API changes that don't require the RouteFetcher as parameter anymore.
- Support multiple legs by snap to route engine #77
- Mark unused option
maximumDistanceOffRoute
as deprecated #65 - Fix move-away-from-maneuver logic of
OffRouteDetector
#65 - Sample app: Moved all configurations to a central place #57
Note
Please delete your existingapp/main/res/values/developer-config.xml
to generate the new one or copy following content to your existing file:<?xml version="1.0" encoding="utf-8"?> <resources> <!-- Your navigation base url (example: https://api.mapbox.com) (--> <string name="base_url" translatable="false">https://api.mapbox.com</string> <!-- Your Mapbox access token (example: pk.abc...) --> <string name="mapbox_access_token" translatable="false">YOUR_MAPBOX_ACCESS_TOKEN_GOES_HERE</string> <!-- Map tile provider for light design (example: https://api.maptiler.com/maps/basic-v2/style.json?key=...) --> <string name="map_style_light" translatable="false"></string> <!-- Map tile provider for dark design (example: "https://api.maptiler.com/maps/basic-v2-dark/style.json?key=...) --> <string name="map_style_dark" translatable="false"></string> </resources>
- Fix memory leak in Navigation Service
- Only progress the user along the step / route if the user is close to the route (currently 1km), #75
- Compatibility fixes for API 34 #90
- When setting a new route or advancing to the next leg, we reset the
currentLegAnnotation
inNavigationRouteProcessor
, fixes legs don't reset on rerouting. - Make sure step distance remaining is set correctly before first routeProgress is calculated, only calculate maneuverCompletion when routeProgress is set. This fixes annotation Index set to wrong values
New Contributors
- @birkskyum made their first contribution in #60
- @Fabi755 made their first contribution in #57
- @tallongsun made their first contribution in #80
- @joshhood made their first contribution in #90
Full Changelog: 2.0.0...3.0.0
2.0.0
- Initial release of Navigation UI package.
- We adapted Navigation module (mostly
RouteFetcher
) to be aligned with the implementation we need in the Navigation-UI package. - Move Style-Url, Routing-Url and Access-Token to NavigationSettings in sample app.
- Remove unused code (mostly Mapbox Speech Service related classes).
- Updated Maplibre version to v10.0.2.
- Incremented minSdk version from 15 to 21 to work same as maplibre implementation.
- Created custom classes for
GoogleLocationEngineImpl
,Utils
,LocationEngineProvider
which were removed from default implementation maplibre to provide working with GSM location. - Corrected resource calls due to renamed res files in maplibre (from
mapbox_
tomaplibre_
). - All changes are included in this pull request 49
- Updated dependencies of used libs and build tools
- Removed AccessToken usage
- Fixed Jitpack Build
- Use the navigation options instead of constants in ToleranceUtils (used in the offroute detection), if you haven't modified rerouting values in the navigation options, nothing should change
1.2.0
1.1.1
1.0.9
1.0.7
1.0.6
Merge pull request #9 from flitsmeister/develop Merge the latest changes into master