MetOffice / MetOffice/edr_server
Corridor and Trajectory queries
Open
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Corridor and Trajectory queries are some of the few query types not yet supported by the EDR Server. I think they need to exactly follow the pattern used by Radius and Position queries - they should inherit from the Area query type and be able to return either FeatureCollection or Domain type JSON responses.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the existing Radius and Position query implementations with the Area query type. Add Corridor and Trajectory query support following those patterns, including FeatureCollection and Domain JSON responses, then verify both query types against the existing response behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100