dataset Ingest Request for ct-ch4-monthgrid-v2025 - #21
dataset Ingest Request for ct-ch4-monthgrid-v2025#21veda-github-actor[bot] wants to merge 4 commits into
Conversation
Workflow StatusStarting workflow... View action run Collection Publication Status➡️ ct-ch4-monthgrid-v2025 (Dataset): Successfully published ✅ |
| }, | ||
| "temporal_extent": { | ||
| "startdate": "1998-01-01T00:00:00Z", | ||
| "enddate": "2023-12-31T00:00:00Z" |
There was a problem hiding this comment.
| "enddate": "2023-12-31T00:00:00Z" | |
| "enddate": "2023-12-31T23:59:59Z" |
There was a problem hiding this comment.
Current STAC metadata has "2023-12-01T23:59:59Z" as the enddate
There was a problem hiding this comment.
Is the current STAC metadata correct? or can be the description be updated to be more accurate to say "near the end of 2023" meaning not all of 2023
There was a problem hiding this comment.
We have a terminal step in veda-backend/ingest-api that automatically updates the temporal range based on the current items in the database so the current data in STAC should be the correct range (https://github.com/NASA-IMPACT/veda-backend/blob/e146f9d82c149e1098cc3a3589f6d5a43f9b1865/ingest_api/runtime/src/vedaloader.py#L18)
There was a problem hiding this comment.
| { | ||
| "collection": "ct-ch4-monthgrid-v2025", | ||
| "title": "CarbonTracker-CH₄ Isotopic Methane Inverse Fluxes v2025", | ||
| "description": "Surface methane (CH₄) emissions are derived from atmospheric measurements of methane and its ¹³C carbon isotope content. Different sources of methane contain different ratios of the two stable isotopologues, ¹²CH₄ and ¹³CH₄. This makes normally indistinguishable collocated sources of methane, say from agriculture and oil and gas exploration, distinguishable. The National Oceanic and Atmospheric Administration (NOAA) collects whole air samples from its global cooperative network of flasks (https://gml.noaa.gov/ccgg/about.html), which are then analyzed for methane and other trace gases. A subset of those flasks are also analyzed for ¹³C of methane in collaboration with the Institute of Arctic and Alpine Research at the University of Colorado Boulder. Scientists at the National Aeronautics and Space Administration (NASA) and NOAA used those measurements of methane and ¹³C of methane in conjunction with a model of atmospheric circulation to estimate emissions of methane separated by three source types: microbial, fossil and pyrogenic. This dataset presents monthly methane emissions in units of grams of methane per square meter per year (g CH₄/m²/year) from microbial, fossil and pyrogenic sources, along with a layer of total methane emissions from all three sources combined, at 1° resolution from 1998 to 2023. The source data can be found at https://doi.org/10.25925/hxks-v755", |
There was a problem hiding this comment.
should this be in links?
There was a problem hiding this comment.
Here we have a "cite-as" link with the doi listed: https://stac.maap-project.org/collections/glad-global-forest-change-1.11 - it's not required, just an example (not all browser extensions interpret links in descriptions vs links in "links")
There was a problem hiding this comment.
I think it should be persisted in the description in case any downstream systems previously expected it there. We could consider repeating the info in links and adding the https://stac-extensions.github.io/scientific/v1.0.0/schema.json extension to use as an example for new collections
| "layer" | ||
| ], | ||
| "title": "Microbial CH₄ Emission", | ||
| "description": "Emission of methane from all microbial sources, such as wetlands, agriculture and termites." |
There was a problem hiding this comment.
"Emission of methane from all microbial sources, such as wetlands, ruminants, agriculture, and termites."
Question: what's the difference between the "discovery items" and "item assets"? Or I guess what's the purpose of each?
There was a problem hiding this comment.
discovery_items is the configuration used to launch the dataset creation pipeline in airflow
item_assets should be provided in STAC collection metadata to describe each asset that a user can expect to find in every item of the collection (title, type, etc). It looks like this collection does not produce a cog_default item asset and it may be included here to work around some legacy schema enforcement that mistakenly required all collections to have a cog_default asset.
There was a problem hiding this comment.
Question: what's the difference between the "discovery items" and "item assets"? Or I guess what's the purpose of each?
Great question, @smk0033 !
The difference is that discover items assets are used to find and assign files during an ingestion, whereas item assets is a STAC collection level metadata (part of the Item Assets extension) that indicates what assets consumers can expect on items for the collection.
There was a problem hiding this comment.
ah sorry I didn't realize @anayeaye already answered!
| }, | ||
| "temporal_extent": { | ||
| "startdate": "1998-01-01T00:00:00Z", | ||
| "enddate": "2023-12-31T00:00:00Z" |
There was a problem hiding this comment.
Current STAC metadata has "2023-12-01T23:59:59Z" as the enddate
4 participants
No description provided.