Open cwienands1 opened 10 months ago
Just found another routing problem, a missing turn:
Segment Bridge sprint to beach road (watopia-bambino-fondo-001-after-after-after-after-before-after
is missing a left turn at its Southern end onto that newish shortcut segment Italian villas loop 3 (watopia-beach-island-loop-004
).
I've reproduced issue 1 and the funny thing is that the end points of those two segments are just far enough apart for the algo to discard it 🤷
Issue 1 is fixed:
Great!
Describe the issue While configuring a route, I discovered two problems with the existing route segment and turn configurations.
Fyi, this is (so far) only a builder issue, not a runner issue. I wasn't able to remove the label.
Application details:
Additional info Issue 1
unknown
, which is probably why the direction shows up incorrectly in the UI. My guess is this: The segments Zwift KOM Bypass and Zwift KOM 2 touch on both ends. Theturns-watopia.json
file doesn't contain information about whether a turn connects to points A or B of a segment, so in this specific case the routing logic doesn't know which end of Zwift KOM 2 to connect to, and in which direction the segment should be ridden. If my guess is correct, a simple fix might be to split the Zwift KOM 2 into two segments so that the direction is always unambiguous to the routing logic. I also took a quick look over the map, and I think this is probably the only occurrence where two segments touch each other on both ends.roadcaptain-route-test1.json
Edited by @sandermvanvliet:
Issue 2
See #127