Exclude Restricted Portions of Network

[JamesOutlaw]

This is related to BUG-000134987 - in ArcGIS Desktop's Network Analyst Extension, there was an option in the GUI for the "Add Locations" GP tool for "Excluding Restricted Portions of The Network"- such as non-traversable segments in a network dataset.  Without this option, users have to manually edit a feature class to move order points to the closest traversable segment.  This option is missing from the "Add Locations" GUI in ArcGIS Pro 2.6 but is available as an option if you use the tool in a Python script.  It would be helpful to many of our users if the option was available in the GUI as many of them rely on the GUI tools rather than scripts.

networkanalysis‌

networkanalyst‌

[MelindaMorang]

In ArcGIS Pro, the default value for the Exclude Restricted Portions of the Network parameter is True. This means that by default, points will not be located on restricted elements. This is different from ArcMap, where the default was False. In Pro, we switched the default to True because we believe this is the setting most, if not all, users need. Furthermore, we could not come up with a compelling reason why a user would want to set the parameter to False, so we hid the parameter in the UI. It is maintained in the python tool signature for backwards compatibility.

Additionally, Pro automatically relocates points at solve time if they are located on an element restricted by a restriction or impedance attribute or a barrier. Consequently, if a user runs Add Locations with the Exclude Restricted Portions of the Network parameter set to False, the point would simply get relocated at solve time anyway.

Please let us know if you have a specific reason why you want to set Exclude Restricted Portions of the Network to False, and we will reevaluate.

[MelindaMorang]

We believe the behavior is already implemented the way this user wants, and they offered no further clarification.

[RussellProvost1]

@MelindaMorang ,

The ability to include restricted portions of the network when loading locations was imperative to our work at Montgomery Planning. We heavily rely on Network Analyst to measure changes in bike connectivity by leveraging the level of traffic stress methodology. We build restrictions using the LTS values to be able to modify the traversability of the network according to a desired LTS. We use a "weakest link" methodology where if there is any portion of the route that is above a desired LTS value, the connection cannot be made. Forcing locations (in our case parcels) to "jump over" adjacent uncomfortable bike facilities defeats the purpose of this methodology. You cannot just pick your bike up and cross several lanes of high stress roads to reach the nearest comfortable street. This has caused an abrupt error in my latest analysis. Is it my understanding that even if I set the "exclude_restricted_elements" parameter to "INCLUDE" in the add locations tool, ArcGIS Pro will ignore it? This is VERY problematic.