MetOffice / MetOffice/edr_server
Radius queries not working
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Unit handling to build a buffered point of a certain specific radius is not working correctly with any combinations of units and projections. Ideally:
- If projection is WGS84 and units is m/km, translate the point to Mercator projection, buffer the point with a radius in m, and convert all the points in the buffered point geometry back to lat/lon
- If projection is WGS84 and units is degrees, this should already work (but doesn't?!)
- If projection is not WGS84, fail?
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 radius-query implementation and the code that handles units and projections. Reproduce queries for WGS84 with metres, kilometres, and degrees, then verify that non-WGS84 projections fail as requested. Done means buffered geometries have correct coordinates for supported combinations and unsupported projections are rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100