You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.
In Mapbox Studio one can assign properties such as Fill Color based on data conditions:
It would be nice to be able to surface these up as a optional tileset legend (separate from the PBI data legend), where the author would select whether to feature any of the tileset's data-driven criteria (e.g. building color or pattern by type, traffic condition colors).
The text was updated successfully, but these errors were encountered:
Agree, this would be a powerful feature - thanks for the request @otravers . It hits on a larger category of feature requests involving "using map layers as data sources" in Power BI.
"Using map layers as data sources in Power BI": YES! (Related: #72)
For further illustration purposes, and in an unsuccessful attempt to crash Mapbox/PBI, here's a map with:
Data-driven choropleth done in Mapbox Studio, since Mapbox in Power BI won't combine the Choropleth data with other data series. (This comment should earn me passive aggressive points.)
Data-driven, color-coded 3D buildings. Incidentally the underlying data seems way less qualified than POIs, but I guess that's OpenStreetMap's problem.
Color-coded traffic congestion.
Satellite + streets background layers, because at this point, why not?
Power BI data layer with Circles, which is the only one that can be explained to the end user via a legend.
In Mapbox Studio one can assign properties such as Fill Color based on data conditions:
It would be nice to be able to surface these up as a optional tileset legend (separate from the PBI data legend), where the author would select whether to feature any of the tileset's data-driven criteria (e.g. building color or pattern by type, traffic condition colors).
The text was updated successfully, but these errors were encountered: