En las tablas siguientes se muestra un catálogo de los cambios realizados en todas las herramientas de la caja de herramientas Network Analyst. Hay una tabla por herramientas y puede hacer clic en el nombre de la herramienta para navegar a la página de referencia correspondiente. Para obtener más información sobre cómo interpretar el contenido de estas tablas de historial, consulte la sección al final de este tema.
Agregar campo a la capa de análisis
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
Añadir ubicaciones
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 2 nuevos parámetros agregados:
|
9.2 | 3 nuevos parámetros agregados:
Parámetro eliminado: snapcontrol |
9.1 | New at this version |
Construir red
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nuevo parámetro agregado: out_network_dataset |
9.1 | New at this version |
Calcular ubicaciones
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 4 nuevos parámetros agregados:
|
9.2 | New at this version |
Copiar Entidades de origen de trazado poligonal
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | New at this version |
Crear la clase de entidad de giro
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | Nuevo parámetro agregado: has_z |
9.1 | New at this version |
Direcciones
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 3 nuevos parámetros agregados:
Al parámetro file_type se le ha agregado una opción nueva: HTML |
10.0 | Nuevo parámetro agregado: output_layer |
9.3 | Al parámetro report_units se le ha agregado una opción nueva: NauticalMiles |
9.1 | New at this version |
Disolver red
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | New at this version |
Buscar instalaciones más cercanas
| Versión | Descripción |
|---|---|
10.4 | Al parámetro Travel_Mode se le ha quitado la opción CUSTOM |
10.3 | Not ported over to ArcGIS Pro 1.0 La extensión necesaria ha cambiado de none a Network Analyst Nuevo parámetro agregado: Travel_Mode |
10.2.1 | New at this version |
Buscar rutas
| Versión | Descripción |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
Generar las áreas de servicio
| Versión | Descripción |
|---|---|
10.4 | Al parámetro Travel_Mode se le ha quitado la opción CUSTOM |
10.3 | Not ported over to ArcGIS Pro 1.0 La extensión necesaria ha cambiado de none a Network Analyst Nuevo parámetro agregado: Travel_Mode |
10.2.1 | Nuevo parámetro agregado: Time_Zone_for_Time_of_Day |
10.2 | Nuevo parámetro agregado: Save_Output_Network_Analysis_Layer |
10.1 | New at this version |
Aumentar los bordes máximos
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nuevo parámetro agregado: out_turn_features |
9.1 | New at this version |
Crear capa de instalaciones más cercanas
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 nuevos parámetros agregados:
|
10.0 | Al parámetro UTurn_policy se le ha agregado una opción nueva: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
Crear la capa de ubicación y asignación
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 nuevos parámetros agregados:
Al parámetro loc_alloc_problem_type se le ha agregado una opción nueva: MAXIMIZE_CAPACITATED_COVERAGE |
10.0 | New at this version |
Crear capa de la matriz de coste OD
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | Nuevo parámetro agregado: time_of_day |
10.0 | Al parámetro UTurn_policy se le ha agregado una opción nueva: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
Crear la capa de ruta
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | Al parámetro UTurn_policy se le ha agregado una opción nueva: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | Nuevo parámetro agregado: start_date_time |
9.1 | New at this version |
Crear la capa de áreas de servicio
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 nuevos parámetros agregados:
|
10.0 | Al parámetro UTurn_policy se le ha agregado una opción nueva: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | 3 nuevos parámetros agregados:
|
9.1 | New at this version |
Crear la capa de problema de generación de rutas para vehículos
| Versión | Descripción |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.0 | Al parámetro UTurn_policy se le ha agregado una opción nueva: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.3 | New at this version |
Rellenar los campos de ID alternativo
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nuevo parámetro agregado: out_network_dataset |
9.1 | New at this version |
Solucionar
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | Nuevo parámetro agregado: simplification_tolerance |
10.0 | 2 nuevos parámetros agregados:
|
9.2 | Nuevo parámetro agregado: ignore_invalids |
9.1 | New at this version |
Resolver ubicación y asignación
| Versión | Descripción |
|---|---|
10.4 | Al parámetro Travel_Mode se le ha quitado la opción CUSTOM |
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
Solucionar problema de generación de rutas para vehículos
| Versión | Descripción |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 2 nuevos parámetros agregados:
|
10.1 | New at this version |
Tabla de giro a clase de entidad de giro
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
Actualizar el parámetro del atributo de la capa de análisis
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New at this version |
Actualizar por campos de Id. alternativos
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nuevo parámetro agregado: out_network_dataset |
9.1 | New at this version |
Actualizar por geometría
| Versión | Descripción |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nuevo parámetro agregado: out_turn_features |
9.1 | New at this version |
Actualizar los datos de tráfico
| Versión | Descripción |
|---|---|
10.4 | Las opciones provider para NAVTEQ han cambiado a HERE. Por ejemplo, NAVTEQ North America ha cambiado a HERE North America |
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.2.1 | Nuevo parámetro agregado: speed_unit |
10.2 | Al parámetro provider se le ha agregado una opción nueva: INRIX |
10.1.1 | Al parámetro provider se le ha agregado una opción nueva: NAVTEQ South East Asia |
10.1 | New at this version |
Actualizar incidentes de tráfico
| Versión | Descripción |
|---|---|
10.4 | Las opciones provider para NAVTEQ han cambiado a HERE. Por ejemplo, NAVTEQ North America ha cambiado a HERE North America |
10.3 | Not ported over to ArcGIS Pro 1.0 Al parámetro provider se le ha agregado una opción nueva: NAVTEQ Oceania |
10.1 | New at this version |
Actualizar red
| Versión | Descripción |
|---|---|
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 Avanzado to Estándar, 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.