3 ms·
Agree on both fronts! STAC is pretty complex. My attempt here was to make raw data access easy and fast, not to solve STAC, which I believe stac-geoparquet basi
by sid_tf 2y ago
Agree on both fronts!
STAC is pretty complex. My attempt here was to make raw data access easy and fast, not to solve STAC, which I believe stac-geoparquet basically makes an attempt to fix (makes it columnar and hence faster to query at scale).
And yes, having a parquet will add overhead of needing some form of catalog. But I believe we are very close to having Iceberg with native geo types being that catalog. at the same time, it opens another can of worms (databricks and other catalogs etc).
silver lining is that parquet (geoparquet) makes geo data closer to regular data.
- whinvik 2y agoNot sure I understand. The blog mentions adding columns to the Geoparquet so it's either an extension or a new standard. Not going to discourage what you are doing but just reading the blog, my immediate instinct is to not try to check out what you build.
- sid_tf 2y agoSure! Glad you shared your honest opinion. But I just want to reiterate that the blog and its subsequent library which will be released is not being done to create a new standard. All throughout the blog its been clearly stated that this is "a new approach", not "new standard" or "new format" or even "better standard".