Allow WKT in areas.yaml files and using CRS in parsing
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 385
- Forks
- 102
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 9
Description
See #332 for some related work and discussion.
The code in pyresample/area_config.py uses a lot of PROJ dictionaries where it may be able to use CRS objects. Additionally, we should allow users to provide WKT if they want. By using CRS objects internally accepting different inputs should be much simpler.
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 pyresample/area_config.py and the related work and discussion in issue #332. Trace how PROJ dictionaries are currently used while parsing areas.yaml, then define completion as accepting WKT inputs and using CRS objects internally for parsing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100