One way directions have to be set up relative to the digitized direction of the line (affecting the From-To or To-From edge), and cannot detect line orientations relative to a compass or clock face direction. Therefore, I use a domain based on digitized direction, not compass directions.
- Open in both directions
- Open in From-To direction
- Open in To-From direction
- Closed in both directions
This gives me the freedom to digitize the line in either direction on the circle and still be able to apply a one-way value that will make it flow correctly.
My evaluator restriction expression for the From-To edge is set to:
NOT ([Direction_of_Traffic] = 1 OR [Direction_of_Traffic] = 2)
(This restricts travel if the line only allows travel in the To-From Direction or is Closed in both directions)
My evaluator restriction expression for the To-From edge is set to:
NOT ([Direction_of_Traffic] = 1 OR [Direction_of_Traffic] = 3)
(This restricts travel if the line only allows travel in the From-To Direction or is Closed in both directions)
If you choose to always digitize your lines so that a particular set of compass/clockwise direction rules is observed, that is up to you, but I find it much easier to change an attribute than to flip lines, especially if I have already assigned address ranges or other attributes that are sensitive to the line's digitized direction.
My expression is based on a text field, not a numeric domain, but the expression shown is equivalent to what I have written above.