--clip-containing-box
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to clip out a section of a tileset (as opposed to clipping a bounding box around a tileset).
I tried inverting the box by swapping min and max values with --clip-bounding-box=60,60,-30,30, but I only get "Did not read any valid geometries".
Can we have a --clip-containing-box? Or can --clip-bounding-box be 'fixed' to handle this mild abuse of it's functionality?
Contributor guide
Research direction
Start by locating the --clip-bounding-box command-line option and the clipping behavior it invokes. Determine whether completion should add --clip-containing-box or extend the existing option to accept inverted bounds, then verify that a tileset section can be clipped without producing "Did not read any valid geometries".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100