Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deck.gl Multiple Layers - Does not work for Heatmap and Contour Layers #25922

Closed
3 tasks
Mattc1221 opened this issue Nov 9, 2023 · 0 comments · Fixed by #25923
Closed
3 tasks

Deck.gl Multiple Layers - Does not work for Heatmap and Contour Layers #25922

Mattc1221 opened this issue Nov 9, 2023 · 0 comments · Fixed by #25923

Comments

@Mattc1221
Copy link
Contributor

A clear and concise description of what the bug is.

How to reproduce the bug

  1. Navigate to the deck.gl Demo dashboard
  2. Add a new deck.gl Heatmap layer to the dashboard using the long_lat dataset
  3. Add a new deck.gl Contour layer to the dashboard using the long_lat dataset
  4. Click the add chart button on the deck.gl Demo dashboard
  5. Select the long_lat dataset and the deck.gl Multiple Layers Chart
  6. Note that you cannot add the Heatmap or Contour Layer to the Multiple Layers Chart

Expected results

I expect to be able to add the Contour and Heatmap layer to the Multiple Layers chart type.

Actual results

We are not able to select Heatmaps or Countour maps to add to the Multiple Layers Chart

Environment

(please complete the following information):

  • browser type and version: Chrome Version 115.0.5790.114 (Official Build) (arm64)
  • superset version: 0.0.0-dev - Noticed on commit ed87470
  • python version: Python 3.9.18
  • node.js version: v16.0.0
  • any feature flags active: no

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant