The tables below catalog changes made to every tool in the Network Analyst toolbox. There is one table per tool and you can click the tool name to navigate to the tool reference page. For more information on interpreting the contents of these history tables, see the section at the end of this topic.
Add Field to Analysis Layer
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
Add Locations
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 2 new parameters added:
|
9.2 | 3 new parameters added:
Parameter removed: snapcontrol |
9.1 | New at this version |
Build Network
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New parameter added: out_network_dataset |
9.1 | New at this version |
Calculate Locations
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 4 new parameters added:
|
9.2 | New at this version |
Copy Traversed Source Features
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | New at this version |
Create Turn Feature Class
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | New parameter added: has_z |
9.1 | New at this version |
Directions
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 3 new parameters added:
Parameter file_type had new option added: HTML |
10.0 | New parameter added: output_layer |
9.3 | Parameter report_units had new option added: NauticalMiles |
9.1 | New at this version |
Dissolve Network
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | New at this version |
Find Closest Facilities
| Version | Description |
|---|---|
10.4 | Parameter Travel_Mode had CUSTOM option removed |
10.3 | Not ported over to ArcGIS Pro 1.0 Required Extension changed from none to Network Analyst New parameter added: Travel_Mode |
10.2.1 | New at this version |
Find Routes
| Version | Description |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
Generate Service Areas
| Version | Description |
|---|---|
10.4 | Parameter Travel_Mode had CUSTOM option removed |
10.3 | Not ported over to ArcGIS Pro 1.0 Required Extension changed from none to Network Analyst New parameter added: Travel_Mode |
10.2.1 | New parameter added: Time_Zone_for_Time_of_Day |
10.2 | New parameter added: Save_Output_Network_Analysis_Layer |
10.1 | New at this version |
Increase Maximum Edges
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New parameter added: out_turn_features |
9.1 | New at this version |
Make Closest Facility Layer
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 new parameters added:
|
10.0 | Parameter UTurn_policy had new option added: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
Make Location-Allocation Layer
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 new parameters added:
Parameter loc_alloc_problem_type had new option added: MAXIMIZE_CAPACITATED_COVERAGE |
10.0 | New at this version |
Make OD Cost Matrix Layer
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | New parameter added: time_of_day |
10.0 | Parameter UTurn_policy had new option added: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
Make Route Layer
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | Parameter UTurn_policy had new option added: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | New parameter added: start_date_time |
9.1 | New at this version |
Make Service Area Layer
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 new parameters added:
|
10.0 | Parameter UTurn_policy had new option added: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | 3 new parameters added:
|
9.1 | New at this version |
Make Vehicle Routing Problem Layer
| Version | Description |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.0 | Parameter UTurn_policy had new option added: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.3 | New at this version |
Populate Alternate ID Fields
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New parameter added: out_network_dataset |
9.1 | New at this version |
Solve
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | New parameter added: simplification_tolerance |
10.0 | 2 new parameters added:
|
9.2 | New parameter added: ignore_invalids |
9.1 | New at this version |
Solve Location-Allocation
| Version | Description |
|---|---|
10.4 | Parameter Travel_Mode had CUSTOM option removed |
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
Solve Vehicle Routing Problem
| Version | Description |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 2 new parameters added:
|
10.1 | New at this version |
Turn Table To Turn Feature Class
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
Update Analysis Layer Attribute Parameter
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New at this version |
Update by Alternate ID Fields
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New parameter added: out_network_dataset |
9.1 | New at this version |
Update by Geometry
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New parameter added: out_turn_features |
9.1 | New at this version |
Update Traffic Data
| Version | Description |
|---|---|
10.4 | provider options for NAVTEQ changed to HERE. For example, NAVTEQ North America changed to HERE North America |
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.2.1 | New parameter added: speed_unit |
10.2 | Parameter provider had new option added: INRIX |
10.1.1 | Parameter provider had new option added: NAVTEQ South East Asia |
10.1 | New at this version |
Update Traffic Incidents
| Version | Description |
|---|---|
10.4 |
provider options for NAVTEQ changed to HERE. For example, NAVTEQ North America changed to HERE North America |
10.3 | Not ported over to ArcGIS Pro 1.0 Parameter provider had new option added: NAVTEQ Oceania |
10.1 | New at this version |
Upgrade Network
| Version | Description |
|---|---|
10.1 | Deprecated |
10.0 | New at this version |
About the toolbox history tables
At every release, Esri makes changes to existing tools and introduces new tools. These changes provide solutions to problems that were difficult to solve in previous releases and make tools more powerful and easier to use.
Esri strives to maintain backward compatibility. However, it's not always possible due to the new functionality being introduced. Here are the cases where backward compatibility may break:
- If a parameter was removed, old workflows that used the parameter will no longer work.
- If a parameter option was removed, old workflows that used the option may no longer work. In many cases, the option that was removed is replaced by another option and the tool knows what to do if the previous option was specified.
- If a parameter had a data type removed and your old workflow used inputs of that data type, the old workflow will not work in the new version.
- A license change may affect your workflow. Most license changes are downward (from Advanced to Standard, for example) which would not affect backward compatibility.
- An extension change may affect your workflow. Extension changes that affect existing workflows are rare.
- If a parameter's default value changed, it may affect your workflow. You'll need to examine your existing workflows to determine the effect of the default value change.
- If the order of parameters changed, scripts that use positional arguments may break.
Below is more information about changes cataloged in the history tables.
New at this version
The last row of each table always contains the release version at which the tool was introduced to the toolbox.
Parameter options
A parameter option (also referred to as an enumerator) is a string that affects tool execution. For example, the join_attributes parameter of the Intersect tool has three options: ALL, NO_FID, and FID_ONLY. New options appear occasionally from release to release, and options may be removed. An option introduced in a later version (such as 10.4) cannot be used in an earlier version (such as 10.3).
Sometimes you'll see an option removed and replaced with a very similar option, such as Euclidean distance replaced with EUCLIDEAN_DISTANCE. In cases like this, the tool is programmed to accept either option and backward compatibility is not broken.
New and removed parameters
New parameters are almost always added as the last parameter so backward compatibility is maintained in scripts. However, sometimes the new parameter must be inserted between existing parameters and compatibility in scripts may be broken—you may have to edit your script to run in the later version. If a new parameter is inserted between existing parameters, it will be noted as a change in parameter order.
Removed parameters are rare. Scripts that use the removed parameter will have to be changed, but models should continue to run.
Parameter default value changes
Optional parameters have a default value—the value that will be used unless you change it. If there is a change to a parameter's default value, it may affect your existing models and scripts.
Parameter data type changes
A data type defines the permissible values for a parameter, such as the type of datasets (features, tables, networks, and so on). If a data type is removed at a version, it means that the parameter no longer accepts the dataset as input or output. You may have to change your models and scripts if they use the removed data type.
Parameter order
New parameters are almost always added as the last parameter and don't affect the order of existing parameters. In rare cases, the order of existing parameters may change, and scripts that use positional arguments may break. Instead of using positional arguments, you can use keyword arguments as shown below. Models will still execute as they are not dependent on parameter order.
# Positional arguments - skipping optional arguments using empty strings is dependent on
# the order of the optional parameters
#
arcpy.AddField_management("schools", "school_id", "LONG", "", "", "", "", "NON_NULLABLE")
# Keyword arguments - position doesn't matter
#
arcpy.AddField_management("schools", "school_id", "LONG", field_is_nullable="NON_NULLABLE")
Parameter name case
The name of a parameter may change case, for example, from In_Features to in_features. This change only affects scripts that use keyword arguments. In Python, keyword arguments are case sensitive.
Parameter type
A parameter type may change from required to optional or from optional to required. Changing from optional to required may affect existing workflows.
Tool licensing and extension
A licensing or extension change may affect existing workflows.
Deprecated tool
See the topic What is a deprecated tool? for more information.