Allow on-the-fly resolution computation for dynamic areas
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 385
- Forks
- 102
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 9
Description
Code Sample, a minimal, complete, and verifiable piece of code
europe:
description: Europe
projection:
ellps: WGS84
lon_0: 0
proj: stere
lat_ts: 60
lat_0: 90
# shape:
# height: 2048
# width: 2560
area_extent:
lower_left_xy: [-3780000.0, -7644000.0]
upper_right_xy: [3900000.0, -1500000.0]
units: m
Problem description
The current implementation of DynamicAreas doesn't allow both size and resolution missing.
However, using the input data for resampling, it is in theory possible to compute how many pixels to resample fall inside the designated area extent, and hence we could compute an approximate size in x and y that would fit the current data.
Expected Output
A frozen area with near-optimal resolution for the data at hand.
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 locating the DynamicAreas implementation and tracing how input data is used during resampling. Determine how missing size and resolution are currently rejected, then define and implement the calculation that produces a frozen area from the area extent and available data. Done means both values may be omitted and the result has near-optimal x and y resolution for the supplied data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100