eWaterCycle / eWaterCycle/ewatercycle
Add provenance to forcing metadata
Open
forcing
- Dominant language
- Python
- Stars
- 41
- Forks
- 6
- Avg merge
- 8d 23h
- Merged PRs (30d)
- 2
Description
When we store forcing objects with `ewatercycle.forcing.DefaultForcing.save`, it would be nice if that metadata file stored some provenance info as well, like
"Forcing generated with eWaterCycle/ESMValTool, ..." or "Forcing for WFlow imported from ..."
Contributor guide
Assessment
This issue has not been assessed yet.