I've created a multi-modal network data set with four main modes being Metro, BRT, Walking and Cycling.
I want to have travel time as and impedance with multiple modes. However, to get onto the metro takes more time than getting of the metro. That is why i made two transfer lines between the metro and the walk infrastructure. They are in digitized in opposite direction and both have a oneway restriction.
However, when solving a route from the metro infrastructure to somewhere else, it is impossible to get of the metro system. The analyst simply says there are no routes possible.
I have the feeling that i defined my oneway restrictions in the right way. However, when i removed the restriction from the network dataset attributes, it was possible to get of the metro infrastructure.
I added a picture in which the situation is explained. The metro transfer line has an arrow at the end to see in which direction it is digitized.
I hope one of you can help me out.
Hello Rogier. I am not sure what's wrong with your Oneway restriction in this case, but a Oneway restriction doesn't seem like the best way to model a difference in travel time between entering and exiting the metro.
When you set up your cost attribute's Evaluators, you have the option to calculate the travel time differently in the "From-To" direction and the "To-From" direction, which refers to the direction of digitization. So, you do NOT need two different line features. You just need one line feature, and you can determine the impedance differently depending on the direction of travel along that one line feature.
See my example below. In this example, I'm setting the impedance for Streets to a constant of 1 in the From-To direction and a constant of 2 in the To-From direction. You don't have to use a constant. You could use a Field or a Function evaluator or whatever. It works the same.