developmentseed / developmentseed/lonboard

HeatmapLayer rendering severely wrong in interleaved Maplibre rendering

Open
#1,033 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
964
Forks
54
Avg merge
5m
Merged PRs (30d)
1

Description

Editing from the duckdb example: https://github.com/developmentseed/lonboard/blob/fe4e1f7c34f0dcda347156212d683688675b1e85/examples/duckdb.ipynb

```py
basemap = MaplibreBasemap(mode="interleaved", style=CartoStyle.Positron)
layer = HeatmapLayer.from_duckdb(con.table("rides"), con, before_id="watername_ocean")
m = Map(layer, height=700, basemap=basemap)
m
```

https://github.com/user-attachments/assets/9f9d36f1-e38d-42a6-8f9c-a47193c0f5cc

Everything looks fine in overlaid mode:
```
m = Map(layer, height=700, basemap=MaplibreBasemap(mode="overlaid", style=CartoStyle.Positron))
m
```

Image

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with examples/duckdb.ipynb and run the supplied HeatmapLayer example using MaplibreBasemap in interleaved mode, then compare it with overlaid mode. Investigate the rendering path involved in interleaved Maplibre integration; done means the heatmap renders correctly in interleaved mode without regressing the overlaid example.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter, python
Domain
data-visualization, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.