eodash / eodash/eodash_catalog
Per-collection configurability via STAC
- Dominant language
- Python
- Stars
- 3
- Forks
- 3
- Avg merge
- 14m
- Merged PRs (30d)
- 5
Description
We could extend the catalog per-layer configurability by allowing generic passing of map, source and layer parameters directly via STAC item and collection metadata utilizing `eodash:` prefix.
A new functionality would be that arbitrary parameters can be passed in and will be only for experienced data administrators who need large flexibility (up to the level of everything that OL sources/layers support out of the box).
connected issue https://github.com/eodash/eodash/issues/347
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reading connected issue #347 and tracing how STAC item and collection metadata are consumed; done means arbitrary eodash-prefixed map, source, and layer parameters can be passed through with the intended collection-level configurability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100