Support CIMP / CORDEX data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 402
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
Hi, @euronion, I have several questions regarding the documentation of Atlite with Cordex dataset, which I think maybe suitable to put here.
Do you have any example/document of Atlite (the current version V0.0.2 or the upcoming V0.2) working with the Cordex data?
It seems that I should download all the 9 variables (influx, outflux, etc...) and store them into 9 folders in the same directory?
Do the variable "CWT" mean "compute working team"? I cannot find this variable in the Cordex output variable list.
Is it possible to prepare a cutout with only a subset of the 9 variables with Cordex?
Thank you in advance!
Originally posted by @fang1103 in https://github.com/PyPSA/atlite/issues/57#issuecomment-609999454
Contributor guide
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
No files or tests are identified in the issue. Start by reviewing the existing Atlite documentation for cutouts and dataset inputs, then determine how CIMP/CORDEX variables map to the documented workflow. Done means answering the variable, folder, subset, and example-usage questions with verified documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100