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

Provide means to model indirect left turns #4252

Closed
4 tasks done
leoluecken opened this issue Jun 19, 2018 · 1 comment
Closed
4 tasks done

Provide means to model indirect left turns #4252

leoluecken opened this issue Jun 19, 2018 · 1 comment

Comments

@leoluecken
Copy link
Contributor

@leoluecken leoluecken commented Jun 19, 2018

This primarily concerns the situation where left turning bikes are crossing the junction in a two step process.
This requires some modifications in the heuristics to determine the conflict matrices of junction if the turning lane's shape has certain characteristics.
Also note that there are two intersection points with other left turning vehicles from the opposite direction.
Refs #4024

open issues:

  • automatically computing connection shape for indirect turning
    • netedit connection mode button: indirect left-turn for selected
      • transform selected bicycle connections (shape, contPos)
      • transform bicycle connections for all selected junctions
  • assign another tlLinkIndex to the connection after the internal junction (new optional attribute linkIndex2, similar to crossings)
    • via xml input
    • with NETEDIT
@leoluecken
Copy link
Contributor Author

@leoluecken leoluecken commented Jun 26, 2018

An indirect left turning vehicle (bicycle) has to consider two green phases, one for the straight direction where its coming from and one (at the internal junction) for the straight direction of its destination.

Loading

namdre added a commit that referenced this issue Jun 28, 2018
namdre added a commit that referenced this issue Jul 25, 2018
… foe left turn does not have an internal junction. refs #4252
@palvarezlopez palvarezlopez added this to the 1.4.0 milestone Aug 14, 2019
@namdre namdre self-assigned this Dec 2, 2019
@palvarezlopez palvarezlopez removed this from the 1.5.0 milestone Feb 11, 2020
@palvarezlopez palvarezlopez added this to the 1.6.0 milestone Feb 11, 2020
@namdre namdre removed this from the 1.6.0 milestone Mar 9, 2020
@namdre namdre added this to the 1.7.0 milestone Mar 9, 2020
@palvarezlopez palvarezlopez removed this from the 1.7.0 milestone Sep 9, 2020
@palvarezlopez palvarezlopez added this to the 1.8.0 milestone Sep 9, 2020
@palvarezlopez palvarezlopez removed this from the 1.8.0 milestone Sep 9, 2020
@palvarezlopez palvarezlopez added this to the 1.9.0 milestone Sep 9, 2020
@palvarezlopez palvarezlopez removed this from the 1.9.0 milestone Apr 16, 2021
@palvarezlopez palvarezlopez added this to the 1.10.0 milestone Apr 16, 2021
namdre added a commit that referenced this issue Jun 20, 2021
namdre added a commit that referenced this issue Jun 20, 2021
namdre added a commit that referenced this issue Jun 21, 2021
namdre added a commit that referenced this issue Jun 21, 2021
namdre added a commit that referenced this issue Jun 21, 2021
namdre added a commit that referenced this issue Jun 21, 2021
namdre added a commit that referenced this issue Jun 21, 2021
namdre added a commit that referenced this issue Jun 21, 2021
namdre added a commit that referenced this issue Jun 21, 2021
namdre added a commit that referenced this issue Jun 21, 2021
namdre added a commit that referenced this issue Jun 21, 2021
@namdre namdre closed this Jun 29, 2021
namdre added a commit that referenced this issue Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants