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

density in meandata for edges has wrong upper bound #4904

Closed
kschrab opened this issue Dec 11, 2018 · 2 comments

Comments

@kschrab
Copy link

commented Dec 11, 2018

If I have an edge with 2+ lanes, and traffic congestion on this edge, the calculation of the density in the meandata for edges is wrong (<edgeData .../>). Actually, it outputs a wrong upper bound.

If the length of the vehicles is 5m, the maximum density given in the meandata is 200 (1000m/5m). This upper bound is, however, only valid for one single lane. If there's more than one lane, the maximum bound should increase lineary (e.g. 600 veh/km for an edge with 3 lanes).

@namdre namdre self-assigned this Dec 12, 2018

@namdre namdre added the regression label Dec 12, 2018

@namdre namdre added this to the 1.1.0 milestone Dec 12, 2018

@namdre

This comment has been minimized.

Copy link
Contributor

commented Dec 12, 2018

was broken in a806854 refs #3265.
Thank you for reporting!

@namdre namdre closed this in 864fba6 Dec 12, 2018

namdre added a commit that referenced this issue Dec 12, 2018
@namdre

This comment has been minimized.

Copy link
Contributor

commented Dec 12, 2018

Maybe not really a regression since the value was far to high before the commit which introduced an invalid upper bound.

@namdre namdre removed the regression label Dec 12, 2018

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.