We are getting this error in PBI Desktop with the latest (180219) release of the MapBox visualization. Running latest PBI Desktop version (2.55.5010.641). The machine is Windows 10 and has IE, Edge and latest Chrome installed.

How to troubleshoot this?

Hi,

Can someone tell me how can i save my features to update MapBox ? For now, i just try to change the descriptions in capabilities but when i create my package, it don't appear. I'm beginner with PowerBI and custom visual and i read a lot of documentation but i can't find a way to update this custom visual.

Thanks guys !

All color and size interpolation calculations should:

If data value is continuous/measure:

1. Calculate natural breaks domains with geoStats - http://www.intermezzo-coop.eu/mapping/geostats/. Domains should have 5-6 discrete breaks.
2. (if color) Calculate continuous color scales using the PowerBI Color palette selector UI and Chroma.js.
3. Create interpolate Mapboxgl expressions based on natural breaks domains to style color or size of data

If data value is discrete/dimension:

1. (if color) Calculate discrete color scale using PowerBI discrete color palettes.
2. Create match Mapboxgl expressions to style color, size of data features

• All setting color selections should use color scale selections if data is continuous/measure.
• All setting color selections should use discrete color picker selections if data is discrete/dimension.

#Example Currently, heatmap visualizations only allow the user to select a single color. The color selection changes the max density color used in the heatmap viz. This is confusing to the user, who wants to control the entire color ramp for the data in the viz.

cc @gyulalaszlo

Can you please post examples of valid values for Source Layer Name and Vector Property like is already done for Vector Tile URL? How do you find out these values, for, say: mapbox://mapbox.us_census_states_2015?

PowerBI custom visuals support Edge, IE11, and Safari. In order to launch on the Office Store, the custom visual has to work in all of these scenarios. The custom visual works great on Chrome and Firefox, leading me to believe that Edge, IE11, and Safari enforce different security policies for iframe sandboxes.

Filed issue in PowerBI Custom Viz repo: https://github.com/Microsoft/PowerBI-visuals/issues/299

@szilardhuber @petispaespea

In IE11:

• Added a startsWith js workaround modifier to get past a basic string manipulation here: https://github.com/mapbox/mapboxgl-powerbi/commit/06403df48b0fef9a3af8e054fefd21a68a217dd3#diff-2d05d529f687bddee587310550a7b0d0
• Get error when loading tiles in a map:

In Edge

DOMException: Code: 18, Security Error when trying to load tiles for map.

Safari

Unable to load blob from the worker. Map tiles do not load.

Next Steps

• [x] @anandthakker any ideas if this could be related to the remaining CSP's we require?

child-src blob: ;
img-src data: blob: ;

For the examples above I'm using the latest master build of mapbox-gl-js on 1/22.

Here's a minimal example to try: https://app.powerbi.com/view?r=eyJrIjoiOWEyMDJmOWQtOTgwMC00ZmYwLWI4NzYtYzQxMDBmNGJiZmUzIiwidCI6IjYyOWE3MGIyLTMyYjktNDEyNi05NTFlLTE3NjA0Y2Y0NTZlYyIsImMiOjF9

cc @lucaswoj

mapbox issue 183 repo.zip I've noticed an issue when using the Choropleth feature and setting Data Colors (based on a text/string field). When an external filter (e.g. a Slicer tile) changes the list of Data Colors, the visual sometimes "forgets" the settings.

The repo steps are a bit complicated - see attached. The scenario is 3 Status values for a set of Locations: Poor/Fair/Good, which should translate into Red/Yellow/Green.

Note when opened, the Indicator Slicer is set to C, which should show only Poor/Fair as Red/Yellow - instead it defaults to the 1st colors in the palette. Changing the Indicator Slicer to A, then B, then C, the colors show correctly. With the Slicer set to C, close, save and re-open - the preset colors disappear again, but come back when you cycle through the Indicator Slicer.

Once set for a text value, the colors need to stay locked, no matter the impact of external filters.

When using a filter to select a "zone" in the map, the autozoom go back to show the full extend of the underlaying vector layer.

To test, simply use the US States choropleth and a list of states as filter. Select a state in the list and the maps zoom full out. It should be zooming in or pan to show the selected state in the same fashion it do when we are using lat/long to filter points.

By the way, good work with this visual!

Proposed copy for the Choropleth layer documentation cc/ @colleenmcginnis

Mapbox Visual for Power BI -Choropleth

1. Download and use the latest version of the Mapbox Visual PBIVIZ file (https://github.com/mapbox/mapboxgl-powerbi/raw/master/dist/mapboxGLMap.pbiviz)
2. Prepare the shapes you want to include in your visualization as a Choropleth layer. If you need Countries, US States, or US Postcodes - no need to do this work, those shapes are included in the visual!
3. Produce a Geojson or Shapefile of the boundaries you want to use. The boundaries should contain one uniquely-identifying property key that matches to your data. Common examples are a FIPS code, Postal Code, ISO code, or a unique name string.
4. If your shapes have a lot of detail (>10 mb of geojson is a good rule of thumb), simplify the boundaries before uploading to Mapbox using www.mapshaper.org. Export your simplified boundaries as geojson.
5. Upload your boundaries to Mapbox as a tileset
6. Once your tileset finishes processing, click on the tileset to get the details from it to use in your Power BI visual.
   1. Map ID (mapbox://rsbaumann.6ftg6wl3)
   2. Layername (losa_crime_joined)
   3. Property name (LSOA11CD)
      • 
7. Configure the data for your Choropleth layer a. Drag the field from your Power BI data source that matches the property values in your shapes to the Location field. Drag the metric you want to style the shapes by to the Color field. b. Turn off all layers except the Choropleth layer from the Format pannel * c. Select Custom from the Data dropdown in the Choropleth layer settings. Enter the map ID of your shapes into your Vector Tile URL (always include mapbox:// in front of your map ID), layername into the Vector Tile Layername field, and property into the Vector Property field. d. Your Tileset should show up in your Mapbox Visual container

Troubleshooting

1. When I put my vector tile URL, source layer, and vector property in, I dont see any shapes on my map.
2. Do the values in your Power BI Location data field match the data type (string vs. numeric) and exact data values in your vector tiles you uploaded to your Mapbox account?
3. Does your Vector Tile URL field begin with mapbox://? A correct tileset URL should look like mapbox://rsbaumann.my-tileset-id.
4. My layer does not show up but I’m sure all the settings are correct.
5. Try toggling the Choropleth layer on and off again in your visual.
6. Can I use a Choropleth layer with other Circle, Heatmap, or Cluster layers?
7. No. This feature is on our roadmap but not currently available.

This ticket captures the entire scope of Choropleth layer support in the Mapbox Visual for Power BI. cc @szilardhuber @petispaespea @endre-jenei @baspeti

Features

• [x] Support polygon shape data from a Vector Tile source as a mapbox:// URL.
  • Should work seamlessly with user-created Mapobox Tilesets.
  • Mapbox tilesets support drag-and-drop conversions to Vector Tiles from Shapefile, KML, and Geojson data formats.
• [x] The user interface for selecting a Vector-Tile source layer and Property Name should auto-populate the available fields in a dropdown list.
  • The default value should be the first available layer name and property value in the drop-down.
  • A user should not have to copy more than the Map ID of a tileset from their Mapbox Tileset URL and paste it into the Vector Tile URL in Mapbox.
  • 
  • To get the list for the drop-down, request the tileJSON for the tileset using the Maps API (exmaple URL here) and parse out the list of values for properties and vector layernames.
  • 
• [x] The Choropleth layer should support the following style options in the Format panel:
  • A min, med, and max fill-color value selector (or continuous color palette, when available in Power BI custom visuals) for a measure data color value
    • Color values for continuous palettes should default to quantile domain stops for color value calculations.
  • A categorical fill-color value selector for a grouping/dimension data color value (see the circle viz for implementation)
  • A min and max zoom (between 0 and 22) slider for layer visibility
  • A fill-opacity slider
  • An outline color dropdown, outline-width counter, and outline-opacity input selector.
    • This outline style should be rendered as a line layer placed one layer above the fill layer. Do not use a fill layer with fill-outline-color, for maximum flexibility
• [x] The Choropleth layer should support tooltips.
  • Tooltip values should update on mouse-move using the debounce function.
  • Tooltip values should display all values from the location, color, and tooltip fields used int he Power BI viz
  • The tooltip values should map from the data in Power BI to the property match in the vector tiles (such as postcode, or country) using a Map lookup data object, with the Map key being the unique property value to join between Power BI and the Vector Tile source.
• [ ] The Choropleth layer should support rendering multiple layers in the same map.
  • The current beta restricts the Choropleth to be the only viz type used if it is selected. This is because of concerns around grouping and aggregation when a user includes a highly grouped dimension (location) and a unique dimension per data value (longitude/latitude) in the same data response from the Power BI data api.
  • The Choropleth layer should properly display the data in Power BI grouped and aggregated by only the data in the location field, not the data in the longitude/latitude fields.
  • The Choropleth layer should render by default as the lowest visual layer order in the visual layer stack (below clusters, heatmaps, and circles).
• [x] The Choropleth layer should present the user with an errors
  • Error with suggested actions to fix if a location dimension is not used in the viz data fields.
• [ ] The layer should have tests validating that layer works with
  • Multiple layers
  • A sample tileset and data set
• [x] Start work from the branch beta 1.1.0

Users should be able to select a feature or set of features from the map using a bounding box selector. Features in the selected region should be passed as a filter to other dashboard visualizaitons. See this for an example: https://www.mapbox.com/mapbox-gl-js/example/using-box-queryrenderedfeatures/

Add functionality where users can make 3d Chroropleth Extrusions as a standard feature.

Sample Code

Needed features:

• Create a new height field within the Fields Panel
• Within the Choropleth Format Panel, there needs to be settings for base, and a height multiplier. In case there are different levels, users should be able to adjust how far the extrusions are able to "pop out"
• If the "Height" field is filled in, while choropleths are enabled, the extrusion should be automatically applied to the map.
• Should support drilling between choropleth layers, as well as custom polygons and shapes.

Fileds added to the tooltip do not appear in the order of the location instead they appear in the order of fields, this happens when hovering over a group of locations to view their information together.

it's probably infeasible to be able to specify a position for the legend box, but i would love to be able to at least assign it to a different corner--top left instead of bottom right, for example.

currently, cloropleth maps allow you to assign a color to minimum & maximum values. null values seem to be assigned to the minimum value color. it would be more helpful to have null values map to their own unique color (like the 'highlight' color). thanks!

Hi ,

in the plugin main page it says "Mapbox supports up to the maximum allowed by Power BI, 30,000 rows"

what does that mean ? is this talking about number of objects actually displayed on the map (I.e 30k circles , clusters ,or polygons) ? or it actually means that that my dataset should have less than 30k rows. because my dataset could have 100k row and only maps to 100 object, if this is the case will the data still be samples? wont I get the correct numbers/aggregates/stats ?

thanks

Hi there, our underwriters fly all over Canada to do property inspections, so I upload the addresses that need inspections into a Mapbox Map in Power BI, publish, and share the weblink with them. But there’s no point in them looking at the map at the weblink address or in the power BI app because both maps are so tiny on the screen that I might as well just send them the google maps link with the trip planned.

It would be great if the map filled almost the whole screen.

Second, is there any way to plan a trip based on how I lassoo them on the screen? Currently, I can lasso the points, but it doesn’t do anything, just highlights them.

It would be great if I could lasso a bunch of points I think he should inspect, then get a screen that downloads the data for JUST those points. Or maybe it would create a table with just those points’ data. That would be amazing. Then what would be even more amazing if it I could plan a trip for him that gave me driving times and directions. 😊😊

Thank-you.