We should use the new locations feature
When I route I should get
| .... | locations |
| .... | a,b,c |
to verify the turn locations we omit in the guidance scenario.
Especially collapsing turns (collapse.feature, but also part of turn-lanes/turn-angles and other scenarios) should be checked for whether the location we emit actually is reasonable.
I expect many of these actually to be broken (so use caution on simply accepting the current output).
From the broken cases, we should then start improving/refactoring the post-processing for turn collapsing.
We should use the new locations feature
to verify the turn locations we omit in the guidance scenario.
Especially collapsing turns (collapse.feature, but also part of turn-lanes/turn-angles and other scenarios) should be checked for whether the location we emit actually is reasonable.
I expect many of these actually to be broken (so use caution on simply accepting the current output).
From the broken cases, we should then start improving/refactoring the post-processing for turn collapsing.