Top takeaway being that it's not just versioned geo feature items, but versioned per-feature formats. Various popular GIS database formats are supported as the "checked-out" representation, analogous to a git local-filesystem tree. Maybe does conversions between standard GIS formats well -- wasn't obvious.
One question I'm left with is performance:
> Every database table row is stored in its own file. ...
https://docs.kartproject.org/en/latest/pages/development/tab...
Top takeaway being that it's not just versioned geo feature items, but versioned per-feature formats. Various popular GIS database formats are supported as the "checked-out" representation, analogous to a git local-filesystem tree. Maybe does conversions between standard GIS formats well -- wasn't obvious.
One question I'm left with is performance:
> Every database table row is stored in its own file. ...