Weather/climate data variable descriptions (for alternate model data use)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 402
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
It would be helpful to have a description of the details for the weather and climate data (in addition to the table here):
Detailed Description and Context
I am trying to use CESM data with atlite. I noticed that the development page discusses that at the moment capacity to build it out further beyond ERA5 is limited. I was hoping to see if more detail could be provided on the table shown above and what each of these variables is used for/a longer description of them? The reason for this is that CESM has different names. Specifically the ones I am trying to translate across that have unclear differences are:
- influx_direct could be a near IR direct solar flux or a visible direct solar flux
- influx_diffuse could be a near IR or a visible solar flux
- runoff could be a surface runoff or total liquid runoff
- height I am assuming to be the geopotential height in meters
- albedo could be a near IR or UV
- wnd100m I am using both U and V (zonal and meridional) winds
Additionally, how important is the time scale? I have some 3-hr, some 6-hr, and some daily data. My impression is that this will only influence the time scale for which I can get data output.
If you have any other advice on the attempt to use other weather data, I would certainly appreciate it, and am happy to discuss further!
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
The issue points to the weather and climate variable table on the development page; start there and compare its entries with the six CESM variables listed. Expand the documentation with the requested variable descriptions and explain how 3-hour, 6-hour, and daily inputs affect output. No specific file or test is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100