Closed ymoisan closed 4 days ago
That depends on your usecase. The goal with CityBuf is to have a very fast and memory-efficient format that allows for streaming reading/writing. Furthermore, CityBuf is aimed to be fully compatible with CityJSON which is somewhat difficult to achieve with a column based format like parquet, eg. the ability to store attributes per face in a 3D solid. Also geoparquet does not support all the geometry types that CityJSON does.
Considering geoparquet already supports 3D and more importantly considering parquet is a very performant file format already used by big "cloud" libraries (like Delta Lake or Iceberg), would it not make sense to store CityObjects in parquet ?