I am having an issue of my route directions taking me on the wrong side of a one way street divided by a small island.
Is there a certain way I should structure the road network to allow for one way streets ?
1 SolutionI discovered the issue.
Roads Along VB Script should be False, meaning that there are no travel restrictions for correctly digitized road along one-way road segments.
Case "N", "TF", "T": restricted = False
Roads Along VB Script should have included the missing "T" designated as one-way roads.
This is restricting travel against digitized road segments.
Deactivated User 05-10-2019 11:23 AMhave you set up the direction of travel in your network restrictions?
New Contributor III 05-10-2019 11:57 AMInteresting, I have never worked with setting network restrictions. I thought that if I digitized the street section correctly it is all I need.
I will have to look into your provided links.
Deactivated User 05-10-2019 12:52 PM
Think of this way. a two-way street is only digitized in one direction, so how does it become two-way?
New Contributor III 05-10-2019 01:35 PMAfter looking at the network attributes, it does have oneway restriction evaluators.
It was created with ArcMap and now I am exclusively working in Pro.
I looked at the roads ONEWAY field and it only has "T" as oneway and "B" for both ways.
The Roads Against evaluator is referencing letters that don't exist in the ONEWAY field.
Roads Along
restricted = False
Select Case UCase([ONEWAY])
Case "N", "TF", "T": restricted = True
End Select
Roads Against
restricted = False
Select Case UCase([ONEWAY])
Case "N", "FT", "F": restricted = True
End Select
