laptop and a wrench


Added costs for global turns are ignored by scaled cost barriers.

Last Published: July 21, 2016 ArcGIS for Desktop
Bug ID Number BUG-000082445
SubmittedOctober 10, 2014
Last ModifiedJune 5, 2024
Applies toArcGIS for Desktop
Version found10.2.2
Operating SystemWindows OS
Operating System Version7
StatusKnown Limit

Additional Information

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).

Steps to Reproduce

Bug ID: BUG-000082445


  • ArcGIS for Desktop

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options