NASA-IMPACT / NASA-IMPACT/veda-data
Decide what to do with custom ingest collections
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9
- Forks
- 1
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 1
Description
There's a pull request to include discovery items configs https://github.com/NASA-IMPACT/veda-data/pull/92 that includes all collections in collection dir.
However I've left the HLS and Landsat ones blank since they have custom ingestion transformations similar to this.
The collections include:
landsat-c2l2-*
hls-l30-002-ej-reprocessed
hls-s30-002-ej-reprocessed
HLSL30
Originally posted by @smohiudd in https://github.com/NASA-IMPACT/veda-architecture/issues/311#issuecomment-1863505833
- Decided and documented (here) how we treat the collections that were created using a different ingestion mechanism
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 by reviewing PR #92, the ingestion-data/collections directory, and transformation-scripts/landsat-lakes-discovery. Compare the listed Landsat and HLS collections with their custom ingestion transformations and the discussion linked from veda-architecture#311. Done means the treatment of each collection is decided and documented in this issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100