The new route planner follows the pedestrian area:
The area is tagged with area=yes.
So far so good - in order to fix the test, I attempted to add an access restriction so that ways with area=yes can not be accessed anymore (in most cases, they give truly weird routeplanning). However, when debugging, the area-tag is not passed to the profile, but it seems to disappear mysteriously.
While debugging the test bench, I got this case:
The new route planner follows the pedestrian area:
The area is tagged with
area=yes.So far so good - in order to fix the test, I attempted to add an access restriction so that ways with
area=yescan not be accessed anymore (in most cases, they give truly weird routeplanning). However, when debugging, thearea-tag is not passed to the profile, but it seems to disappear mysteriously.