Bindu-yadav8 opened a new issue, #30264:
URL: https://github.com/apache/superset/issues/30264

   I'm experiencing an issue with the Deck.gl 3D Hexagon Layer in Apache 
Superset. The map visualization is being rendered as a 2D flat map instead of 
3D, despite making the necessary configuration changes. Here are the details:
   
   Issue Details:
   Superset Version: Superset 2.1.3
   Deck.gl Layer: 3D Hexagon Layer
   Map Style: Mapbox
   
   
   Steps to Reproduce:
   Set up a Deck.gl 3D Hexagon Layer in Superset.
   In the chart configuration, enable the following:
   Extruded: True
   Elevation Scale: > 0 (e.g., 50)
   Verified that a valid Mapbox API token is provided.
   Ensured data contains proper lat/lon fields and elevation-related metrics.
   Saved the configuration and refreshed the dashboard.
   
   
   
   Expected Behavior:
   The map should render in 3D with the hexagons extruded according to the 
elevation values in the dataset.
   
   Actual Behavior:
   The map is displayed as a 2D flat chart, with no 3D effects visible.
   
   Troubleshooting Steps Already Taken:
   Checked that the Mapbox token is correct.
   Confirmed WebGL is supported and enabled in the browser.
   Validated all Deck.gl layer settings (extruded: true, elevation scale, and 
color schemes).
   Increased the zoom level to check if 3D effects appear.
   Restarted Superset and reloaded the page multiple times.
   
   Environment:
   Browser: Google Chrome
   Operating System: Windows
   
   <img width="956" alt="image" 
src="https://github.com/user-attachments/assets/123646fe-3bec-4306-96ed-0a3fff950428";>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to