Proposal
Topic of the session
MLT in the deck.gl ecosystem: Why it exists and why it matters
Type of the session
Estimated duration of the session
30 minutes incl discussion (open to shortening or having more in-depth discussions)
Date and Time of the session
Level
Pre-requisite knowledge
Basic familiarity with vector tiles (e.g. MVT) and GPU-based rendering (e.g. deck.gl) is helpful.
Describe the session
MLT (MapLibre Tile format) is emerging within the broader WebGL mapping ecosystem and is indirectly available to deck.gl users through its MapLibre integration.
This session focuses on what that means in practice and why it’s worth paying attention to now.
We will cover:
- What MLT is and how it differs from MVT in practice
- Why the MapLibre ecosystem is investing in a new tile format
- How MLT shows up in the deck.gl ecosystem today (and its current limitations)
- What advantages it offers (data layout, decoding cost, scalability, size)
- Where MLT is heading (MLT v2 and beyond), including open design questions
The goal is not to introduce a completely new tool, but to make deck.gl/vis.gl developers aware of an emerging format in their maps' ecosystem, explain its implications, and invite early feedback.
Session facilitator(s), Github handle(s) and timezone(s)
Frank Elsinga (@CommanderStorm) – CEST
Meeting notes and Virtual Meeting Link
Follow-up / Set-up sessions (if any)
Additional context (optional)
We are in the vis.gl ecosystem, but only as a (larger) dependency.
Proposal
Topic of the session
MLT in the deck.gl ecosystem: Why it exists and why it matters
Type of the session
Estimated duration of the session
30 minutes incl discussion (open to shortening or having more in-depth discussions)
Date and Time of the session
Level
Pre-requisite knowledge
Basic familiarity with vector tiles (e.g. MVT) and GPU-based rendering (e.g. deck.gl) is helpful.
Describe the session
MLT (MapLibre Tile format) is emerging within the broader WebGL mapping ecosystem and is indirectly available to deck.gl users through its MapLibre integration.
This session focuses on what that means in practice and why it’s worth paying attention to now.
We will cover:
The goal is not to introduce a completely new tool, but to make deck.gl/vis.gl developers aware of an emerging format in their maps' ecosystem, explain its implications, and invite early feedback.
Session facilitator(s), Github handle(s) and timezone(s)
Frank Elsinga (@CommanderStorm) – CEST
Meeting notes and Virtual Meeting Link
Follow-up / Set-up sessions (if any)
Additional context (optional)
We are in the vis.gl ecosystem, but only as a (larger) dependency.