Execution of the work described in stac-utils/titiler-pgstac#97, specifically stac-utils/titiler-pgstac#97 (comment), copying most content that discussion.
Description
We would like to compare performance of tiling the same dataset using titiler-pgstac (COGs) and titiler-xarray (Zarr)
We believe this is the best approximation of comparing tiling between the two approaches because of the following methodology:
- Assume you are starting with a known collection
- Metadata read step
a. For COG: you register a query with pgstac for the collection id, variable and time step of interest
b. For Zarr: You read consolidated metadata and "lazily load" the variable and time step (slice) of interest
c. For now - I'm going to store both of these metadata components (pgstac and kerchunk reference) locally, but it might be of interest to move pgSTAC and kerchunk to the cloud...
- Generate tiles
a. COG: use mosaic ID to read chunks from COGs on S3
b. Zarr: Use zarr metadata to read chunks from NetCDFs or Zarrs on S3
There is a public archive of COGs generated for CMIP6 for a VEDA related dashboard, using NetCDFs we have stored in S3 as well. There is a public archive is here: https://nex-gddp-cmip6-cog.s3.us-west-2.amazonaws.com/ and we have the original NetCDFs in S3 as well. So we can:
For titiler-pgstac:
For titiler-xarray
For both:
Execution of the work described in stac-utils/titiler-pgstac#97, specifically stac-utils/titiler-pgstac#97 (comment), copying most content that discussion.
Description
We would like to compare performance of tiling the same dataset using titiler-pgstac (COGs) and titiler-xarray (Zarr)
We believe this is the best approximation of comparing tiling between the two approaches because of the following methodology:
a. For COG: you register a query with pgstac for the collection id, variable and time step of interest
b. For Zarr: You read consolidated metadata and "lazily load" the variable and time step (slice) of interest
c. For now - I'm going to store both of these metadata components (pgstac and kerchunk reference) locally, but it might be of interest to move pgSTAC and kerchunk to the cloud...
a. COG: use mosaic ID to read chunks from COGs on S3
b. Zarr: Use zarr metadata to read chunks from NetCDFs or Zarrs on S3
There is a public archive of COGs generated for CMIP6 for a VEDA related dashboard, using NetCDFs we have stored in S3 as well. There is a public archive is here: https://nex-gddp-cmip6-cog.s3.us-west-2.amazonaws.com/ and we have the original NetCDFs in S3 as well. So we can:
For titiler-pgstac:
For titiler-xarray
For both: