Forum Discussion
Legend with dynamic data in Shape MAP
- 11 months ago
kushanNa
Okay, it seems that i'd created my own problem.
The original thing, as described in this topic and with above measures, does do the trick.For some reason, the issue had experienced was due to the fact that I'd checked Show items with no data for the origin. (I had that checked from an earlier version where I'd tried to give a color to the "empty" shapes)
I do not understand why, but unchecking this setting does the trick and shows me what i need!
Thanks for your help!
tjalleph Filter the locations in your main table that are coming up as blank and check if there are any blank values, errors, spaces or unusual formats ?
kushanNa No, they're not empty.
See the two figures side-by-side. Both are unfiltered, meaning that all shapes have (multiple) datapoints of travel time. I can't find a pattern in this behavior neither: shapes stay empty that have - in the table - all datapoints of the same "traveltime_category" [e.g. "<15min"], or when there are different traveltime_categories for an origin.
see also example below of the filtered dataset.
- kushanNa11 months agoSuper User
tjalleph it seems like shapemap has a datapoint limit 1500 https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-data-points maybe this can be a reason
- tjalleph11 months agoFrequent Visitor
kushanNa Hmm, this could play a role. However, how would that explain the difference between the left- and right-handed map?
In the underlying table, there are ca 12k records, with only 1k distinct origins.
- kushanNa11 months agoSuper User
That I'm not entirely sure, actually. What I would suggest is that you start with a fresh report to make sure there are no hidden filters. Then, try applying some filters on the Power Query side and create a small table including 9,883 location . If you can see the 9,883 location records on both sides, we can assume this might be a data point limit issue. However, if you still cannot see the 9,883 records even after creating a very small table, then it could be a different issue