GitHub user pierrejego created a discussion: Cartodiagram plugin: support 
dynamic perimeter masking and polygon boundary aggregation

## Feature request

This issue is only about the `plugin-chart-cartodiagram`.

I would like to improve how filtered polygon data is displayed in the 
cartodiagram plugin, especially when working with administrative boundaries at 
different levels.

## Use case 1: dynamic mask outside the selected area

When a filter is applied, I would like to have a dynamic mask on the map so 
that areas outside the selected perimeter are visually faded or hidden.

The goal is to make the active area easier to identify, whether:
- no filter is applied yet;
- one or more filters are active.

This would improve readability and make the current spatial focus clearer in 
dashboards.

## Use case 2: dynamic merge of polygon entities

Another use case is the dynamic merge of polygon entities on the fly.

My dashboard provides 3 filters based on different boundary levels. In some 
cases, when filtering at a higher level, I do not want to keep displaying all 
lower-level polygon boundaries.

For example:
- if the filter corresponds to a level 3 boundary,
- I do not want to continue seeing level 4 boundaries (for example commune/city 
boundaries),
- I only want to see the resulting outer perimeter corresponding to the 
selected level 3 area.

In other words, for polygon geometries, it would be useful to support a dynamic 
aggregation/dissolve behavior so that filtered entities are displayed as a 
single perimeter instead of multiple internal boundaries.

## Expected result

For the `plugin-chart-cartodiagram`, it would be useful to support:
- a dynamic mask around the currently relevant area;
- a dynamic dissolve/merge of filtered polygon entities to display only the 
outer perimeter.

## Additional context

I have already started working on these developments in our custom `terrestris` 
build based on Superset 5.0.0:
https://github.com/terrestris/superset/tree/5.0.0-custom

A PR will be proposed soon once the implementation is stabilized.

Please let me know whether I should open a dedicated issue for this in addition 
to this discussion.



GitHub link: https://github.com/apache/superset/discussions/38692

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to