NASA-IMPACT / NASA-IMPACT/veda-data
Audit lis-global-da-gpp-trend [Gross Primary Productivity Trend - LIS 10km Global DA]
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9
- Forks
- 1
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 1
Description
What
Recent automated ingests may have added older/deprecated versions of items to the Gross Primary Productivity Trend - LIS 10km Global DA collection id lis-global-da-gpp-trend. Time permitting, determine which assets are valid and update catalog as needed.
Refs
in staging stac:https://staging-stac.delta-backend.com/collections/lis-global-da-gpp-trend/items
in dashboard: https://www.earthdata.nasa.gov/dashboard/data-catalog/lis-global-da-trends/explore?projection=mercator%7C%7C&basemapid=satellite&datetime=2003-01-01T00%3A00%3A00.000Z
items & hrefs
curl -X 'GET' \
'https://staging-stac.delta-backend.com/collections/lis-global-da-gpp-trend/items?limit=10' \
-H 'accept: application/geo+json' | jq -r '.features[].id'
DAGPP_STL_based_trend_v3_2003_2021.cog
DAGPP_STL_based_trendv2_2003_2021.cog
DAGPP_STL_based_trend.cog
curl -X 'GET' \
'https://staging-stac.delta-backend.com/collections/lis-global-da-gpp-trend/items?limit=10' \
-H 'accept: application/geo+json' | jq -r '.features[].assets.cog_default.href'
s3://veda-data-store-staging/EIS/COG/LIS_GLOBAL_DA/DA_Trends/DAGPP_STL_based_trend_v3_2003_2021.cog.tif
s3://veda-data-store-staging/EIS/COG/LIS_GLOBAL_DA/DA_Trends/DAGPP_STL_based_trendv2_2003_2021.cog.tif
s3://veda-data-store-staging/EIS/COG/LIS_GLOBAL_DA/DA_Trends/DAGPP_STL_based_trend.cog.tif
AC
- outdated versions of data removed from stac catalog and ingestion_data/production/discovery-config OR this issue closed with note that all versions of this file are valid and expected to exist in
lis-global-da-gpp-trend
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the staging STAC collection endpoint and the provided curl commands to compare the three item IDs and their cog_default.href values. Determine which versions are valid, then inspect ingestion_data/production/discovery-config and update the STAC catalog as needed. Done means outdated versions are removed, or the issue is closed with a note that all versions are valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100