Detect existing LTNs
- Dominant language
- Rust
- Stars
- 21
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
We observed one auto-generated severance boundary has literally 0 shortcuts; it's all cul-de-sacs and is already an LTN. This brought up the idea that people might want to just assess existing conditions and find parts of the city that are already LTNs. Just a backlog idea to explore -- determining a cut-off for shortcuts present somewhere is unclear. v1 had some form of this, and the results weren't great.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue mentions a previous version (v1) had some form of this feature, but the results weren't great. Start by exploring the codebase for existing logic around generating severance boundaries and detecting shortcuts. Look for any legacy v1 code or documentation. The goal is to define a cut-off for shortcuts to identify existing LTNs, but the specific algorithm or threshold is undefined and needs design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100