Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid junction priority (trac #1689) #1689

Closed
behrisch opened this issue Mar 18, 2015 · 3 comments

Comments

@behrisch
Copy link
Contributor

commented Mar 18, 2015

straight connections should have priority over left-turning connections if all edge priorities, speeds and lane numbers are the same.

Migrated from http://sumo.dlr.de/ticket/1689

{
    "status": "closed", 
    "changetime": "2015-03-20T09:44:10Z", 
    "description": "straight connections should have priority over left-turning connections if all edge priorities, speeds and lane numbers are the same.", 
    "reporter": "namdre", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1426844650336042", 
    "component": "net building (NETGEN, NETCONVERT)", 
    "summary": "invalid junction priority", 
    "priority": "major", 
    "keywords": "", 
    "time": "2015-03-18T14:39:23Z", 
    "milestone": "0.23.0", 
    "owner": "namdre", 
    "type": "defect"
}
@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Mar 18, 2015

@namdre commented:

the problem is seen at edges with sharp turns as the function NBEdge::getTotalAngle() is used.

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Mar 18, 2015

@namdre commented:

it would be better to use getStartAngle() / getEndAngle() since these return the angle at the node in a robust way

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Mar 18, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.