RFCs#
RFCs (requests for comments) are written proposals for large features or big breaking changes of the SpatialData data model, the storage format, or several in-memory formats at once. When to write one and the process are in RFCs; new RFCs start from the RFC template.
No. |
RFC |
Type |
Authors |
Status |
Created |
|---|---|---|---|---|---|
1 |
data model; storage format |
Luca Marconato, Tomaz Vieira, Ajayrama Kumaraswamy (transformations refactoring) |
planned |
2026-10-23 |
|
2 |
data model; storage format |
Luca Marconato; base by Yimin Zheng (Padua hackathon, April 2026); design contributions by Artür Manukyan (Venice hackathon) |
draft |
2026-10-23 |
|
3 |
data model; storage format |
Luca Marconato (@LucaMarconato); input from Nicolas Fernandez (@cornhundred), Arne Defauw, Jonas Windhager, Ilan Gold, Ignatius Jenie, Mark Keller, Christian La France, Tim Treis |
draft |
2026-09-17 |
|
4 |
storage format |
Nicolas Fernandez (@cornhundred), Luca Marconato (@LucaMarconato); input from Ilan Gold, Marco Varrone, Mark Keller |
draft |
2026-10-27 |
|
5 |
data model; storage format |
Luca Marconato |
idea |
2026-09-11 |
Type: what the RFC changes, one or both of data model · storage format; discussion when it changes neither, e.g. an RFC about implementations.
Statuses: idea (not yet written up) · planned (agreed to be written) · draft (pull request open) · under review (on this page, discussed and revised) · accepted (design agreed) · specified (in the draft of the next version) · released (in a released version) · rejected · withdrawn (by its authors); the process, with a figure, is in RFCs.