search

US-GHG-Center / ghgc-docs

https://us-ghg-center.github.io/ghgc-docs/
3 stars 2 forks source link

Fixing nodata values in COGs #84

Closed SwordSaintLancelot closed 1 month ago

SwordSaintLancelot commented 4 months ago

Description

This PR is created to resolve the issue mentioned and consists of following steps:

  1. Fetching the COGs from the S3 bucket.
  2. Analyzing the nodata values in the COGs, if not present, update the COG with nodata values.
  3. Update the COGs in the S3 bucket.
  4. Update the transformation scripts as well to add the nodata value when creating the COGs.

List of collections to be updated:

review-notebook-app[bot] commented 4 months ago

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.

Powered by ReviewNB

github-actions[bot] commented 4 months ago

PR Preview Action v1.4.7 :---: :rocket: Deployed preview to https://US-GHG-Center.github.io/ghgc-docs/pr-preview/pr-84/ on branch gh-pages at 2024-05-22 15:54 UTC

SwordSaintLancelot commented 3 months ago

The casaGFED data is now provided by the data provider so they will need to update the nodata values when they send us the COGs in future.

SwordSaintLancelot commented 3 months ago

Using the /cog/info endpoint in the raster API, I validated a few files that it does show nodata values as -9999.

SwordSaintLancelot commented 3 months ago

MiCASA dataset is currently withheld from changing the nodata values. Some discussions are to be held with the POCs to finalize the values.