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

Custom connection settings are lost #3742

Open
namdre opened this issue Dec 21, 2017 · 1 comment

Comments

@namdre
Copy link
Contributor

commented Dec 21, 2017

some actions currently cause re-generation of a junction and custom connection data (link indices) when it isn't strictly necessary

  • when splitting an edge attached to a junction - nothing should be lost
  • when joining junctions, lane-to-lane connectivity should be preserved. If the junctions were part of a joined TLS, all custom link indices should be preserved.
  • when deleting a lane or connection, custom link indices should be preserved
  • when deleting an edge, custom link indices and connections should be preserved
  • when adding a lane or an edge, all existing connections and their custom link indices should be preserved and any new links should be added at the end of the state vector
@namdre namdre added the a:NETCONVERT label Jan 3, 2018
@namdre namdre self-assigned this Jan 3, 2018
namdre added a commit that referenced this issue Jan 3, 2018
namdre added a commit that referenced this issue Jan 3, 2018
namdre added a commit that referenced this issue Jan 3, 2018
namdre added a commit that referenced this issue Jan 3, 2018
namdre added a commit that referenced this issue Jan 4, 2018
namdre added a commit that referenced this issue Jan 4, 2018
namdre added a commit that referenced this issue Jan 4, 2018
@namdre namdre closed this Jan 4, 2018
namdre added a commit that referenced this issue Jan 4, 2018
@namdre

This comment has been minimized.

Copy link
Contributor Author

commented Feb 15, 2018

When adding edges, lanes or connections the whole logic is still reset.
There must be some way to configure whether recomputation or preservation is desired.

@namdre namdre reopened this Feb 16, 2018
@palvarezlopez palvarezlopez added this to the 1.0.0 milestone Feb 17, 2018
namdre added a commit that referenced this issue Feb 19, 2018
namdre added a commit that referenced this issue Feb 19, 2018
@namdre namdre modified the milestones: 1.0.0, 1.1.0 Aug 28, 2018
@behrisch behrisch modified the milestones: 1.1.0, 1.2.0 Dec 19, 2018
@behrisch behrisch removed this from the 1.2.0 milestone Jun 1, 2019
@palvarezlopez palvarezlopez added this to the 1.4.0 milestone Aug 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.