Silicate file format - Githubissues

hypertidy / silicate

A general form for complex data

https://hypertidy.github.io/silicate/

54 stars 4 forks source link

Silicate file format #66

Closed mdsumner closed 4 years ago

mdsumner commented 6 years ago

Implement this on SQLite, it's obvious how to do it. It will clarify the silicore separation

mdsumner commented 6 years ago

It will also flush out code that isn't already compatible with back-ending.

mdsumner commented 6 years ago

Thoughts.

This family of formats could be very useful. We could define a SF format in SQLite based on silicore, write GDAL driver for it, and show how any DB can use the schema, and how it extends to more efficient and powerful forms that aren't SF. Finding out how GDAL would interact with it could be very interesting. The format and the data structures are the same, something also discussed here https://github.com/ropenscilabs/rivis/issues/2#issuecomment-312657431

mdsumner commented 6 years ago

Work in progress here: https://github.com/hypertidy/scdb

mdsumner commented 5 years ago

Geopackage extensions don't include a scheme for virtual geometry blobs.

write a geometry blob that includes a references to a vertex table rather than coord tuples, nested just like WKB
add the unique vertex pool
use extensions to declare that virtual geom, and link crs and units in the gpkg way

Do all this in R.

Write a GDAL reader/writer, so other tools don't see any difference.

Consider more complex forms

nested index-only geoms with predictable 2- or 3- structure
edge table (edge instance direction needs thought here)
triangle table