Added costs for global turns are ignored by scaled cost barriers.
Last Published: July 21, 2016ArcGIS for Desktop
Bug ID Number
October 10, 2014
March 30, 2022
ArcGIS for Desktop
Operating System Version
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
There are various reasons why scaled cost barriers don’t apply to turns (this was actually by design). However, there is a very simple solution to their problem. Essentially, it appears they want global turn delays everywhere *except at a few choice intersections where they know that there are crosswalks/traffic-signals*.
At those few choice intersections, they are currently willing to digitize barriers in an attempt to “scale down” the global-turn delays. A more appropriate solution would instead be to digitize explicit turns at those specific intersections, and directly assign them the desired (scaled-down) turn costs. Explicit turns always override global turns, so the global turns won’t be used at these intersections, but instead the explicit turns with the smaller desired costs will be used. This not only solves the problem, but will speed up their solves, as having to add in barriers slows things down considerably at solve time (barriers are really only intended to support ephemeral scenarios [e.g., temporary road closures or weather conditions], not permanent aspects of the network, such as this).