In a deck.gl multiple layers I use a deck.gl scatterplot with a categorical color for the point color. It's working fine except that the categories color in legend is not the same as the point on the map.
How to reproduce the bug
- Create a deck.gl scatterplot chart
- Put something in "Point Color > Categorical Color" parameter
- Save chart
- Create a deck.gl Multple Layers chart
- Add previously created deck.gl scatterplot
- Run and see point color
Actual results
Expected results
Same color as the configured one in deck.gl scatterplot
Environment
(please complete the following information):
- browser type and version: Firefox 91.10 esr
- superset version: 1.5.0
Checklist
Make sure to follow these steps before submitting your issue - thank you! - [X] I have reproduced the issue with at least the latest released version of superset. - [X] I have checked the issue tracker for the same issue and I haven't found one similar.
Comment From: MrTrakez
Have you found a solution yet? I have the same problem!
Comment From: cphilibien
I have the same issue. There are a solution?
Comment From: BitBy73Bit
+1
Comment From: rusackas
Still an issue in Superset 3.x... but not a high priority issue. Anyone want to take a crack at opening a PR?
Comment From: rusackas
The above linked issue was closed as a duplicate, but has more context for anyone who wants to tackle this.
Comment From: rusackas
I wonder if our resident DeckGL guru @Mattc1221 would like to take a look here.
Comment From: rusackas
Seems like this thread has gone cold... maybe it's an edge case... maybe it's fixed in 4.1.2/5.0.0? Could use some fresh context and validation, but might be closed as 'not planned' unless anyone wants to investigate and open a PR.
Comment From: DarksChoise
- does anyone know if it has been resolved? @geido @dosu
Comment From: dosubot[bot]
Yes, this issue was present in Superset 4.1.2 through 5.0.0rc2, where Deck.GL scatterplot charts would show incorrect categorical colors in dashboards. The bug is fixed in the master branch after 5.0.0rc2—see the fix here: PR #33748. If you need a workaround, using version 4.1.1 avoids the problem, but upgrading to a version that includes this PR will resolve it permanently. More context and confirmation of the fix can be found in issue #32841.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
