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

allow specifying symbolic stop lane #5443

Closed
namdre opened this issue Apr 9, 2019 · 2 comments
Closed

allow specifying symbolic stop lane #5443

namdre opened this issue Apr 9, 2019 · 2 comments

Comments

@namdre
Copy link
Contributor

namdre commented Apr 9, 2019

either via lane="EDGE_first" (ugly)
or via edge="EDGE" lane="first" (also ugly)
or something else. see #5115

@namdre
Copy link
Contributor Author

namdre commented Sep 24, 2020

I think the second version is ok.
As long as the symbolic names have no underscore, we also don't run the risk of name collision between symbolic names and lane ids. In contrast, to #7584 we can always interpret the stop lane in the context of a know vehicle so "first" can always be interpreted in regard to a vClass. (similar to departLane).

The advantage of allowing stop attribute 'edge' (with lane then optional) is also a much cleaner definition of person stops.

@namdre namdre added this to the 1.8.0 milestone Sep 24, 2020
@namdre namdre self-assigned this Nov 20, 2020
@namdre
Copy link
Contributor Author

namdre commented Nov 20, 2020

added tests in [5e773e5]

fixed in [781b057]

setting attribute edge instead of lane now uses the rightmost allowed lane.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant