ImperialCollegeLondon / ImperialCollegeLondon/SWMManywhere
validate bounding box
Open
feature
- Dominant language
- Python
- Stars
- 51
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I know it should be easy, but in all my demos I seem to have to take like 3 tries at getting the bounding box right 😆
Things I manage to get wrong (so far):
- order obviously
- omitting a negative value
Contributor guide
Research direction
The issue does not name a file, test, or entry point; start by locating where the bounding box is accepted for demos or simulations. Done should mean invalid coordinate order and omitted negative values are detected clearly before processing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100