下方表格记录了 Network Analyst 工具箱中每个工具所发生的更改。每个表格对应一个工具，您可通过单击工具名称导航至工具参考页面。有关解释这些历史表格内容的详细信息，请参阅该主题结尾部分。
向分析图层添加字段
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
添加位置
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 新增了 2 个参数：
|
9.2 | 新增了 3 个参数：
移除了参数：snapcontrol |
9.1 | New at this version |
构建网络
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | 新增参数：out_network_dataset |
9.1 | New at this version |
计算位置
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 新增了 4 个参数：
|
9.2 | New at this version |
复制遍历的源要素
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | New at this version |
创建转弯要素类
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 新增参数：has_z |
9.1 | New at this version |
方向
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 新增了 3 个参数：
参数 file_type 新增了选项：HTML |
10.0 | 新增参数：output_layer |
9.3 | 参数 report_units 新增了选项：NauticalMiles |
9.1 | New at this version |
融合网络
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | New at this version |
查找最近设施点
| 版本 | 描述 |
|---|---|
10.4 | 参数 Travel_Mode 移除了选项 CUSTOM |
10.3 | Not ported over to ArcGIS Pro 1.0 所需的扩展模块已由 none 更改为 Network Analyst 新增的参数：Travel_Mode |
10.2.1 | New at this version |
查找路径
| 版本 | 描述 |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
生成服务区
| 版本 | 描述 |
|---|---|
10.4 | 参数 Travel_Mode 移除了选项 CUSTOM |
10.3 | Not ported over to ArcGIS Pro 1.0 所需的扩展模块已由 none 更改为 Network Analyst 新增的参数：Travel_Mode |
10.2.1 | 新增的参数：Time_Zone_for_Time_of_Day |
10.2 | 新增的参数：Save_Output_Network_Analysis_Layer |
10.1 | New at this version |
增加最大边数
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | 新增的参数：out_turn_features |
9.1 | New at this version |
创建最近设施点分析图层
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 新增了 2 个参数：
|
10.0 | 参数 UTurn_policy 新增了选项：ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
创建位置分配图层
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 新增了 2 个参数：
参数 loc_alloc_problem_type 新增了选项：MAXIMIZE_CAPACITATED_COVERAGE |
10.0 | New at this version |
创建 OD 成本矩阵图层
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 新增的参数：time_of_day |
10.0 | 参数 UTurn_policy 新增了选项：ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
创建路径分析图层
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 参数 UTurn_policy 新增了选项：ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | 新增的参数：start_date_time |
9.1 | New at this version |
创建服务区图层
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 新增了 2 个参数：
|
10.0 | 参数 UTurn_policy 新增了选项：ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | 新增了 3 个参数：
|
9.1 | New at this version |
创建车辆配送图层
| 版本 | 描述 |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.0 | 参数 UTurn_policy 新增了选项：ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.3 | New at this version |
填充备用 ID 字段
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | 新增的参数：out_network_dataset |
9.1 | New at this version |
求解
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 新增的参数：simplification_tolerance |
10.0 | 新增了 2 个参数：
|
9.2 | 新增的参数：ignore_invalids |
9.1 | New at this version |
求解位置分配
| 版本 | 描述 |
|---|---|
10.4 | 参数 Travel_Mode 移除了选项 CUSTOM |
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
求解车辆配送（VRP）
| 版本 | 描述 |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 新增了 2 个参数：
|
10.1 | New at this version |
转弯表至转弯要素类
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
更新分析图层属性参数
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New at this version |
按备用 ID 字段更新
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | 新增的参数：out_network_dataset |
9.1 | New at this version |
按几何更新
| 版本 | 描述 |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | 新增的参数：out_turn_features |
9.1 | New at this version |
更新流量数据
| 版本 | 描述 |
|---|---|
10.4 | NAVTEQ 的 provider 选项已更改为 HERE。例如，NAVTEQ North America 已更改为 HERE North America |
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.2.1 | 新增的参数：speed_unit |
10.2 | 参数 provider 新增了选项：INRIX |
10.1.1 | 参数 provider 新增了选项：NAVTEQ South East Asia |
10.1 | New at this version |
更新交通事件
| 版本 | 描述 |
|---|---|
10.4 | NAVTEQ 的 provider 选项已更改为 HERE。例如，NAVTEQ North America 已更改为 HERE North America |
10.3 | Not ported over to ArcGIS Pro 1.0 参数 provider 新增了选项：NAVTEQ Oceania |
10.1 | New at this version |
升级网络
| 版本 | 描述 |
|---|---|
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.