allow specification of oneways in road network
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 19
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Right now it's possible for probes to be incorrectly matched to known oneways when using the `bidirectionBearing` flag. It'd be preferable for us to allow individual roads to be flagged `oneway: true | false` so we never attach opposite bearings to a oneway.
With this feature, we could probably remove the `bidirectionalBearing` option - since you always (?) want it right now - and instead rely on one-way specification to prevent invalid reverse bearing matches.
Contributor guide
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 road-network matching entry point and tracing how the bidirectionBearing flag affects bearing matches. Determine how individual roads could carry oneway values and whether removing bidirectionBearing is in scope. Done means opposite bearings are not attached to roads marked oneway and the existing matching behavior remains valid for roads without that specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100