Invalid intersection of trainlines #1
Labels
No Label
Bug
Feature
Improvement
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: markus/lifo-dijkstraserv#1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I don't think it's the following, but I've seen some weird behavior in regard to this...
Let there be the following scenario.
Trainline A and Trainline B visually cross at point A. Now, exactly (aka rounded to) this point, we intersect Trainline A with an access layer. -> New point created here.
Problem: For some reason, I have now seen a path going directly from Trainline A to Trainline B to the access layer...
RN, it can be seen with CFE and E1 from 264,116 to 813,2998.
Hmm might there actually be an invalid "upgrade" of a trainline to an access path due to a bugged intersect/split?
Nope, I just literally forgot to exclude intersecting trainlines with each other...
See: https://git.notsyncing.net:8080/markus/lifo-dijkstraserv/src/master/src/dijkstragraph.c#L317
Fixed in
50c39a52bb
.