I share the same feelings, hence I along with OP, made this attempt of creating a library based on whatever seemed most performant and closest to regular data e

I share the same feelings, hence I along with OP, made this attempt of creating a library based on whatever seemed most performant and closest to regular data engineering world. 1. Geoparquet for metadata (iceberg catalog could be added later if scale is extremely large) 2. Cloud Optimized Geotiff (COG) for image data (which is what NASA and ESA have been pumping for last 5 years and still do) 3. and an efficient lightweight library that can quickly grab pieces of data from 100s or 1000s of raster files parallely. I did not want to attempt creating another format, coz I felt that we as geocommunity are at a stage where such tools and files put together forms a pretty good first level foundation to build on. No need for heavy legacy tools, closer to regular data (with parquet) and closer to duckdb world. I feel adoption may be good, if this is the thesis / guiding principles. Baby steps surely, but good steps I believe, and this is all thanks to the open source community.