Allow more projections in `get_area_slices`
@djhoese is already working on this.
Since Jun 8, 2018.
- Dominant language
- Python
- Stars
- 385
- Forks
- 102
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 9
Description
Problem description
Right now the AreaDefinition.get_area_slices method only supports non-geos projections as the source if the target area is in the same projection. There is technically no reason we couldn't support other projections, but some projections may have unexpected results when we try to find the intersection between two different projections. This issue is for any discussion or at least as a reminder to decide whether or not to disable to if statement that is currently stopping other projections from being supported.
Additionally when this is changed the AreaDefBoundary class should be modified to check for 'geos' projections and compute the boundaries specially.
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.
Assessment
This issue has not been assessed yet.