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, the process and a template are in RFCs.
No. |
RFC |
Scope |
Targets |
Proposed by |
Status |
|---|---|---|---|---|---|
1 |
data model; storage format; implementations |
storage format 0.5; data model 1.1 or unchanged, to be decided |
Luca Marconato, Tomaz Vieira, Ajayrama Kumaraswamy (transformations refactoring) |
planned |
|
2 |
data model; storage format; Python |
data model 1.1; storage format 0.5 |
Luca Marconato; base by Yimin Zheng (Padua hackathon, April 2026); design contributions by Artür Manukyan (Venice hackathon) |
draft |
|
3 |
storage format; implementations |
storage format 0.5; data model 1.1, or unchanged if tiling stays a storage-side index |
Nicolas Fernandez (@cornhundred) |
idea |
|
4 |
data model; storage format |
data model 1.1; storage format 0.5 |
Luca Marconato |
idea |
Targets: the data model and storage format versions an RFC changes, as stated in its header; for RFCs not yet written, the proposed targets.
Statuses: planned (agreed to be written) · idea (a discussion, not yet written up) · draft · under review · accepted · rejected · withdrawn · implemented.