include the z-component
#127 discusses different routers. Currently
global_shortest seems to be state of the art. Heights aren't considered in the algorithm though which leads to unexpected behaviors like in the image below. Pedestrians inside the Alexanderplatz metro station take up to 14.4 additional meters in altitude and several stairs to save a few meters in xy-dimensions.
This minimum example demonstrates the issue:
Including z-dimensions when calculating the distance matrix would be a first step towards a more realistic representation of the tactical level.
Additionally there are studies on route choices of pedestrians, which conclude in relative cost factors for rooms according to their attributes. https://www.witpress.com/Secure/elibrary/papers/CR06/CR06001FU1.pdf I think it would make sense to take advantage of such studies and allow their usage. As a basic idea one could define factors related to the class attribute of subrooms like in the suggested inifile snippet below:
` <route_choice_models> <router router_id="1" description="ff_global_shortest"> <parameters> <factor class="stair" factor="1.5"> <factor class="escalator_up" factor="1.3"> <factor class="roofed" factor="0.9"> </parameters>--> </router> </route_choice_models>
Why would the enhancement be useful to most users
More realistic representation of the tactical level. Local characteristics could be considered.