[Bug] Heatmap doesn't display correctly when using Maplibre Interleaved Overlay
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Description
Description
Aggregation seems to be broken since Deck 9.1.0 (luma 9.1?) when using MapboxOverlay "interleaved:true" option
https://jsfiddle.net/cg7mu9sv/25/
Flavors
- Script tag
- React
- Python/Jupyter notebook
- MapboxOverlay
- GoogleMapsOverlay
- CARTO
- ArcGIS
Expected Behavior
Correct heatmap aggregation
https://jsfiddle.net/cg7mu9sv/29/
Steps to Reproduce
Simple code using maplibre 5.6.0 and deck 9.1.12 (see jsfiddle)
Only change between the 2 fiddles is the interleaved:true/false
Tried to check the "GPU Parameters" from luma but can't find out what's wrong
Environment
- Framework version: deck 9.1.2 / maplibre-gl 5.6.0
- Browser: Chrome
- OS: Any
Logs
No console error
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked JSFiddle reproductions using deck 9.1.2 and MapLibre GL 5.6.0, comparing the interleaved:true and interleaved:false cases. Trace the MapboxOverlay interleaved rendering path and GPU parameters to identify why heatmap aggregation differs; done means the heatmap aggregates correctly with interleaving enabled and no console errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100