This plugin aims at extracting code from the main SDK related to tracking settings. These settings allow developers to track the user location and bearing changes. Atm a lot of boilerplate code is used to take these settings and this would cleanup the codepaths there though this plugin is going to be harder to extract.

We'd like to add a traffic plugin that lets you add a traffic layer to any Mapbox basemap. To do that, we could use runtime styling.

We'd also like to add a sample activity to the test app that lets you switch between a few basemaps, including a toggle to turn traffic on and off.

cc: @ericrwolfe

Every time CI has build successfully, the team is getting an email.
For other projects we have disabled this integration.

mapbox/mapbox-gl-native#9426 looks to add support for circle pitch alignment in runtime styling thus unlocking the ability to simplify the logic for the accuracy ring and animate it.

We are currently using a fill layer since it lays flat even when the maps tilted but with this property unlocked it should become a circle layer. Technically all the layer really could become a circle layer but for the customizability available as far as using drawable for the location icon, I'm thinking they should remain symbol layers.

cc: @tobrun @zugaldia

a separate activity for picking the location from the Mapbox map & return a latitude, longitude and an address(if exist the reverse geocoding services ) based on the location picked.
with options for a center of the map, zoom and search view for searching location by text.

Thanks for this plugin. One question: can we make it use with raster tiles?

Currently the projects gradle.properties file contains the version number for all the projects. This needs to be split up into the different module gradle.properties file.

cc: @Guardiola31337 @zugaldia

Currently we bundle the Navigation SDK for Android (https://github.com/mapbox/mapbox-navigation-android) with no explicit dependencies on the Map SDK. This makes the Navigation SDK light-weight, well-contained, and suitable of a wide range of applications.

However, there're some specific features that a navigation app would build on top of the Maps SDK (like route layers updated as the user navigate, or traffic #4). Let's bring this functionality as a navigation-focused plugin.

cc: @mapbox/navigation

A cool feature that was implemented as an example for extrusions is animating the FillExtrusion while zooming from @incanus. The iOS code for that is:

 func mapView(_ mapView: MGLMapView, didFinishLoading style: MGLStyle) {
        if  let composite       = style.source(withIdentifier: "composite"),
            let building        = style.layer(withIdentifier: "building") as? MGLFillStyleLayer,
            let building_line   = style.layer(withIdentifier: "building-line"),
            let airport_labels  = style.layer(withIdentifier: "airport-label") {
            building.isVisible = false
            building_line.isVisible = false
            let extrusions = MGLFillExtrusionStyleLayer(identifier: "extrusions", source: composite)
            extrusions.minimumZoomLevel = 15
            extrusions.sourceLayerIdentifier = "building"
            extrusions.fillExtrusionColor = building.fillColor
            extrusions.fillExtrusionOpacity = MGLStyleValue(rawValue: 0.75)
            extrusions.fillExtrusionHeight = MGLStyleValue(interpolationMode: .exponential,
                                                           compositeStops: [
                                                               15: [
                                                                   0: MGLStyleValue(rawValue: 0)
                                                               ],
                                                               16: [
                                                                   0:    MGLStyleValue(rawValue: 0),
                                                                   1000: MGLStyleValue(rawValue: 1000)
                                                               ]
                                                           ],
                                                           attributeName: "height",
                                                           options: nil)
            style.insertLayer(extrusions, above: airport_labels)
        }
    }

This is currenlty missing from the Building plugin and would be a nice to have.

Instead of offering android wear functionality inside the Maps SDK directly, we should use this plugin system for those looking to implement our maps inside wearables. This would give the added benefit of being able to use the Wear dependencies offered by Google.

We could make a reimplementation of the clustering algorithm found in Google maps utils library. The code for this is apache licensed. This plugin should automatically support clustering of Markers and MarkerViews.

Instead of animating the location layer icon to a new location far away from the origin, instantly moving or speeding up the animation might be necessary. Otherwise, it gives the appearance that the icon is missing from the map.

I want to create plugin for loading GeoJson file from assets, path or url. Add point, polyline and polygon of GeoJson on the map with item click listener.
@tobrun @langsmith

Once we're able to publish the plugins to Maven #3 and once we have the first plugin ready #4 (both are happening shortly) we'll want to make this repository available for anyone to use. For this to happen we have to document:

• the list of available plugins with descriptions
• information on how to install them via Maven/Gradle
• examples on how to use them (reference implementation is in the test app)
• information on how to contribute a plugin

Initially, we can use the README file in this repo but, ideally, we'll integrate this documentation with the rest of the Android docs (new Plugins tab in https://www.mapbox.com/android-docs?).

@langsmith Could you add to OP anything I might have missed and run point on this?

@ericrwolfe Do we have a similar ticket for iOS? Do we have any comms plans in the pipeline?

cc: @cammace @tobrun

Currently, when navigation pucks being used in the locationlayer plugin, no scaling is occurring on the icon causing it to become enormous when zoomed at low levels.

With mapbox/mapbox-gl-native#9013, we added binding integration for the GL style specification concept of Light. This API allows to change the global light source used for fill extrusion layers.

Instead of exposing the API cfr to the style spec:

• color
• intensity
• anchor
• position (radian coordinate, azimuth angle & polar angle)

We can expose some facility API around the concept of the placement of the Sun during the day.

light conditions in the morning, midday and evening?

cc @mapbox/android

This plugin would be a high level wrapper around offline API.
More information and context in mapbox/mapbox-gl-native#7289.

• download a region
  • show notification while downloading
    • cancel button
    • customisation configuration
  • handle multiple requests
    • hook into onStartCommand
  • allow binding/unbinding to forward any errors?
  • handle connection state change events
• bounds selection dialog
• list offline regions
• remove offline regions
• change name offline region
• update offline region content?
• navigation?
• searching for map data?
• only download on wifi configuration
• save maps only to SD card configuration?

Use an accelerate/decelerate animation only when the Location.getSpeed() is equal to 0. This way when a user's driving, the location icon will smoothly track the user.

Each plugin will have separate javadoc which needs to be generated with each plugin release. Note that release of plugins are independent of each other.

cc: @zugaldia @langsmith

With the 5.1.0 release we are introducing FillExtrusionLayer. One of the features possible with this, is showing buildings on top of the map by using OSM data. Atm, integrating this feature into your map requires developers to write boiler plate code. Similar to our Traffic plugin, I'm proposing to have a simple facility API so developers aren't required to hook into the runtime API and can show buildings on a map by just calling a single method.

Note that Google however exposes this functionality directly in their SDK. Since this feature for us would be a high level implementation on top of a low level implementation. I'm suggesting putting it into a plugin instead.

WIP can be followed in #26

cc @mapbox/android @pveugen @ericrwolfe

There's a flavor of TensorFlow for mobile (example code here). Additionally, it was announced during I/O a new effort, TensorFlow Lite, that's gonna improve the mobile experience further. I'd love to see a plugin that uses a pre-trained TensorFlow model to provide some additional functionality on top of the map or our services.

@mapbox/android please keep an eye open for interesting models out there that we could apply here.

**Platform:Android 6.0
**Mapbox SDK version:5.1.2

1.The accuracy part of LocationLayerPlugin doesn't shown, event changing to customized style;
2.If the accuracy part can be seen, will it change its shape along with the tilt?

We should have a plugin that automatically localizes map labels into the user’s preferred language. There’s already a robust implementation of this feature in Objective-C targeting the macOS SDK that could be ported to the Android SDK:

https://github.com/mapbox/mapbox-gl-native/blob/cc1ea759a681cadcfd06fd7bdda79ca6deb38c62/platform/macos/app/MapDocument.m#L346-L393
https://github.com/mapbox/mapbox-gl-native/blob/cc1ea759a681cadcfd06fd7bdda79ca6deb38c62/platform/macos/app/MGLVectorSource+MBXAdditions.m

/ref mapbox/mapbox-gl-native#7031
/cc @tobrun @langsmith @ericrwolfe

Once #1 gets merged, we need to add this project to Bitrise.

cc: @Guardiola31337 @tobrun

To allow scale on this repo, the CI build should be decoupled in having a CI build for each plugin. This allows us to have more finer grain control over builds/releases/testing and treats each plugin as its own project.

Been seeing some examples of data driven coloring of the height property

We could look into adding this as an option on the plugin.

Originally, the location layer supported adding text below the icon but while simplifying, I removed the code. We should add this back as an option.

These two common GPS files are widely used across the internet, often shared via email and social media. It would be excellent to have a plugin which parses the GPX or KML into GeoJSON so that it can be imported onto the map. The key reason for a plugin would be so the GPS file could be loaded onto the map quickly, without the need for an API request to an external server to convert the file (which would take a long time) and without the need of an internet connection.

Mapbox has the https://github.com/mapbox/togeojson library, it just needs to be ported here to a native plugin.

Once implemented the developer can use native OS functionality to launch his/her app via "Open with" when a GPS file is opened on a device.

Once implemented, the developer can implement the native "open with" for their app for GPX/KML file extensions. The app will load and run a function (sorry, I don't know what this is called in Android) to parse the file, which this plugin will parse/convert, then the GeoJSON data will be available to be loaded onto any layer after the map is setup.

Now that the first plugin has been created (traffic! 🎉) let's make it public for anyone to use.

For this to happen, we need to do the following:

• Add basic documentation #13 @langsmith
• Improve token integration #20 @Guardiola31337
• Make this repo public @zugaldia
• Release the artifacts to Maven @zugaldia
• Prepare comms @zugaldia @ericrwolfe

@mapbox/android please add to OP anything I might have missed.

We added a Traffic Plugin in #6, currently we hardcode the layerId which we use in addLayerBefore(layer, layedId). Ideally we use can use the source layer identifier to check for a road identifier instead.

Upstream feature ticket for source layer identifier in mapbox/mapbox-gl-native#8663

The README declares the gradle dependencies as com.mapbox.mapboxsdk:mapbox-android-traffic-plugin:0.1.0 but on Maven Central and Sonatype they are registered as com.mapbox.mapboxsdk:mapbox-android-plugin-traffic:0.1.0

To keep consistency across plugins we should change the traffic plugin to have setVisibility rather than toggle so it's easier on the developer to, for example, directly pass in a boolean setting into the params.

cc: @tobrun @danesfeder

The icon color should fade to gray when the user location hasn't been updated for x amount of time.

It seems that the scheduled release build is failing due to rotated AWS access:

+------------------------------------------------------------------------------+

| (1) Fetch GPG Secring For SDK Signing                                        |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-06-20T04:04:23Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
fatal error: An error occurred (403) when calling the HeadObject operation: Forbidden
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | Fetch GPG Secring For SDK Signing (exit code: 1)              | 1.15 sec |
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-script/issues             |
| Source: https://github.com/bitrise-io/steps-script                           |
+---+---------------------------------------------------------------+----------+

Additionally we weren't notified of the failure in slack. I'm proposing to add an@android_team mention in the slack message that is posted as part of our CI build.

cc @mapbox/android

This plugin would move all logic found related to MarkerView from the Mapbox GL native SDK to a separate plugin. This would allow us to have independent releases from the main sdk and limit the exposed api there. This change would result in a SemVer change in main SDK.

Once #1 gets merged, we need to add support for publishing artifacts to Maven (and daily snapshots to Sonatype).

cc: @Guardiola31337 @tobrun

Hello,
When I use custom location engine (GoogleLocationEngine) сrash occurs on Android.

Plugin version :
0.1.0
0.2.0-SNAPSHOT

Logcat:

F/libc    ( 3054): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 3054 (.reverllc.rever)
I/DEBUG   (13278): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   (13278): Build fingerprint: 'samsung/jflteuc/jflteatt:5.0.1/LRX22C/I337UCUGOK2:user/release-keys'
I/DEBUG   (13278): Revision: '10'
I/DEBUG   (13278): ABI: 'arm'
I/DEBUG   (13278): pid: 3054, tid: 3054, name: .reverllc.rever  >>> com.reverllc.rever <<<
I/DEBUG   (13278): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
I/DEBUG   (13278):     r0 00000000  r1 be8217b4  r2 be8217e0  r3 9c7d3179
I/DEBUG   (13278):     r4 be8217b4  r5 be8217b4  r6 a030f77c  r7 be821768
I/DEBUG   (13278):     r8 8e778b00  r9 be8217e0  sl be821880  fp b4f07800
I/DEBUG   (13278):     ip 9ca11cc4  sp be8216d8  lr 9c79a827  pc 9c7d3194  cpsr 800f0030
I/DEBUG   (13278): 
I/DEBUG   (13278): backtrace:
I/DEBUG   (13278):     #00 pc 00195194  /data/app/com.reverllc.rever-1/lib/arm/libmapbox-gl.so
I/DEBUG   (13278):     #01 pc 0015c825  /data/app/com.reverllc.rever-1/lib/arm/libmapbox-gl.so
I/DEBUG   (13278):     #02 pc 0015dc3f  /data/app/com.reverllc.rever-1/lib/arm/libmapbox-gl.so
I/DEBUG   (13278):     #03 pc 000c2beb  /data/app/com.reverllc.rever-1/lib/arm/libmapbox-gl.so
I/DEBUG   (13278):     #04 pc 000bd8b3  /data/app/com.reverllc.rever-1/lib/arm/libmapbox-gl.so
I/DEBUG   (13278):     #05 pc 000bfd5b  /data/app/com.reverllc.rever-1/lib/arm/libmapbox-gl.so
I/DEBUG   (13278):     #06 pc 000a2541  /system/lib/libart.so (art_quick_generic_jni_trampoline+32)
I/DEBUG   (13278):     #07 pc 00314694  /dev/ashmem/dalvik-alloc space (deleted)

To reproduce the bug, you need to zoom map. Sometimes a bug is reproduced immediately. Sometimes You need to quickly zoom (in-out) map. (by fingers)

I created sample app - https://github.com/giperwlad/mapboxLocationPluginSample
Bug was reproduced on real devices (for example Samsung S6,S4).
I very much hope that you can help solve this problem.
Thanks.

UPDATE
Crash is reproduced with LOST LocationEngine too!

UPDATE
Crash is reproduced when user location changes and marker moves

Plugin proposal to have an object oriented wrapper around symbol layers. These wrappers should be generated from the style specification. This allows to automatically include new style spec features when they land on the Android SDK.

A scale widget plugin allows to place a scalebar on a Mapbox map.

iOS is bringing this feature to their SDK in mapbox/mapbox-gl-native#7631. We could potentially implement this as a plugin instead. This fits in our to decouple our map SDK more into smaller pluggable components.

cc @zugaldia

Originally suggested by @tobrun, we should have each plugin have it's own readme file so that we can place more information about that specific plugin there and simply link to all the plugin readmes in the parent level directory README.

cc: @zugaldia @langsmith

With the merge of Location layer, we now offer an additional plugin. We also are close to merging to building plugin and the traffic plugin has been updated to 0.2.0. These changes need to be reflected in the readme file in this repo.

cc: @langsmith @zugaldia

Similar to https://github.com/mapbox/mapbox-java/blob/master/CONTRIBUTING.md this repo needs a contributing guide.

cc: @langsmith

Before this repo goes public, the hardcoded access token should be removed from the testapp and the gradle script for creating developer_config.xml file added.

cc: @zugaldia @Guardiola31337

The idea for this plugin is using Runtime Styling to replace current MyLocationView implementation. @cammace started of this work in mapbox/mapbox-gl-native#7516. Instead of merging it to the main SDK, we could also expose this as a plugin and let the SDK rely on it instead. With a SemVer release we could extract the implementation completely in a separate plugin.

This ticket tracks an idea about the language to write the plugin with rather than the actual purpose of the plugin. Considering plugins are well-contained, a plugin would be an ideal place to showcase how to interact with the Maps SDK using only Kotlin.

What do you think @mapbox/android ?

One issue restricting the traffic plugin from working on any platform is the fact that we are trying to add the traffic above "bridge-motorway" but this layer id doesn't exist in every style causing the traffic layers to not get added.

cc: @tobrun @zugaldia

Ticket as per the contribution guidelines. I'm not fully sure if the word static is the best word to use for this ticket.

The idea is either a setting on top of current NAVIGATION mode or another mode. Where the navigation icon would not move or rotate as it does today. Instead it would be centered and the map/camera would rotate and follow the user.

Iirc the TRACKING_FOLLOW at MyLocationView in Mapbox SDK did the following part but not always pointing upwards on the screen.

Similar to other navigation apps, as it's probably a simpler UI experience for navigation.

Feel free to close this issue. Looking forward for any input from @mapbox/android

I'm pretty sure we are interested in this mode, we currently have a small testing branch with a modified version of this master.

Exposing a callback for when the compass accuracy becomes low will allow developers to integrate their own UI (or possibly use ours) to alert the user to recalibrate the sensor.

The plugins repo seems to be missing a CHANGELOG.md file. Not sure if we want each plugin to have their own or a central log. In the documentation, we'd need to remove or come up with a better solution for the changelog link. See https://github.com/mapbox/android-docs/issues/172

cc: @langsmith @tobrun

Looks like the work in the offline PR accidentally got merged when the geojson plugin got merged. https://github.com/mapbox/mapbox-plugins-android/tree/master/plugins/offline/build

cc: @tobrun