In den nachfolgenden Tabellen sind die Änderungen aufgeführt, die an den Werkzeugen der Toolbox "Network Analyst" vorgenommen wurden. Für jedes Werkzeug ist eine eigene Tabelle verfügbar. Klicken Sie auf den Namen des Werkzeugs, um zur Referenzseite des Werkzeugs zu navigieren Weitere Informationen zum Interpretieren dieser Änderungshistorie finden Sie am Ende dieses Themas.
Feld zu Analyse-Layer hinzufügen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
Standorte hinzufügen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 2 neu hinzugefügte Parameter:
|
9.2 | 3 neu hinzugefügte Parameter:
Parameter wurde entfernt: snapcontrol |
9.1 | New at this version |
Netzwerk berechnen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Neu hinzugefügter Parameter: out_network_dataset |
9.1 | New at this version |
Standorte berechnen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | 4 neu hinzugefügte Parameter:
|
9.2 | New at this version |
Passierte Quell-Features kopieren
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | New at this version |
Turn-Feature-Class erstellen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | Neu hinzugefügter Parameter: has_z |
9.1 | New at this version |
Wegbeschreibung
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 3 neu hinzugefügte Parameter:
Dem Parameter file_type wurde eine neue Option hinzugefügt: HTML |
10.0 | Neu hinzugefügter Parameter: output_layer |
9.3 | Dem Parameter report_units wurde eine neue Option hinzugefügt: NauticalMiles |
9.1 | New at this version |
Netzelemente reduzieren
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | New at this version |
Nächstgelegene Einrichtungen suchen
| Version | Beschreibung |
|---|---|
10.4 | Die Option CUSTOM des Parameters Travel_Mode wurde entfernt |
10.3 | Not ported over to ArcGIS Pro 1.0 Die erforderliche Erweiterung wurde von none in Network Analyst geändert Neu hinzugefügter Parameter: Travel_Mode |
10.2.1 | New at this version |
Routen suchen
| Version | Beschreibung |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
Einzugsgebiete generieren
| Version | Beschreibung |
|---|---|
10.4 | Die Option CUSTOM des Parameters Travel_Mode wurde entfernt |
10.3 | Not ported over to ArcGIS Pro 1.0 Die erforderliche Erweiterung wurde von none in Network Analyst geändert Neu hinzugefügter Parameter: Travel_Mode |
10.2.1 | Neu hinzugefügter Parameter: Time_Zone_for_Time_of_Day |
10.2 | Neu hinzugefügter Parameter: Save_Output_Network_Analysis_Layer |
10.1 | New at this version |
Maximale Anzahl an Kanten erhöhen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Neu hinzugefügter Parameter: out_turn_features |
9.1 | New at this version |
Layer der nächstgelegenen Einrichtung erstellen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 neu hinzugefügte Parameter:
|
10.0 | Dem Parameter UTurn_policy wurde eine neue Option hinzugefügt: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
Location-Allocation-Layer erstellen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 neu hinzugefügte Parameter:
Dem Parameter loc_alloc_problem_type wurde eine neue Option hinzugefügt: MAXIMIZE_CAPACITATED_COVERAGE |
10.0 | New at this version |
Layer mit Start-Ziel-Kostenmatrix erstellen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | Neu hinzugefügter Parameter: time_of_day |
10.0 | Dem Parameter UTurn_policy wurde eine neue Option hinzugefügt: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
Routen-Layer erstellen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.0 | Dem Parameter UTurn_policy wurde eine neue Option hinzugefügt: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | Neu hinzugefügter Parameter: start_date_time |
9.1 | New at this version |
Einzugsgebiet-Layer erstellen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 neu hinzugefügte Parameter:
|
10.0 | Dem Parameter UTurn_policy wurde eine neue Option hinzugefügt: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | 3 neu hinzugefügte Parameter:
|
9.1 | New at this version |
Layer für Vehicle Routing Problem erstellen
| Version | Beschreibung |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.0 | Dem Parameter UTurn_policy wurde eine neue Option hinzugefügt: ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.3 | New at this version |
Alternative ID-Felder füllen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Neu hinzugefügter Parameter: out_network_dataset |
9.1 | New at this version |
Berechnen
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | Neu hinzugefügter Parameter: simplification_tolerance |
10.0 | 2 neu hinzugefügte Parameter:
|
9.2 | Neu hinzugefügter Parameter: ignore_invalids |
9.1 | New at this version |
Location-Allocation berechnen
| Version | Beschreibung |
|---|---|
10.4 | Die Option CUSTOM des Parameters Travel_Mode wurde entfernt |
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
Vehicle Routing Problem berechnen
| Version | Beschreibung |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 2 neu hinzugefügte Parameter:
|
10.1 | New at this version |
Kantenübergangstabelle in Turn-Feature-Class
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
Attributparameter für Analyse-Layer aktualisieren
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New at this version |
Gemäß alternativen ID-Feldern aktualisieren
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Neu hinzugefügter Parameter: out_network_dataset |
9.1 | New at this version |
Gemäß Geometrie aktualisieren
| Version | Beschreibung |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Neu hinzugefügter Parameter: out_turn_features |
9.1 | New at this version |
Verkehrsdaten aktualisieren
| Version | Beschreibung |
|---|---|
10.4 | Die Optionen provider für NAVTEQ wurden in HERE geändert. NAVTEQ North America wurde beispielsweise in HERE North America geändert |
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.2.1 | Neu hinzugefügter Parameter: speed_unit |
10.2 | Dem Parameter provider wurde eine neue Option hinzugefügt: INRIX |
10.1.1 | Dem Parameter provider wurde eine neue Option hinzugefügt: NAVTEQ South East Asia |
10.1 | New at this version |
Verkehrsereignisse aktualisieren
| Version | Beschreibung |
|---|---|
10.4 | Die Optionen provider für NAVTEQ wurden in HERE geändert. NAVTEQ North America wurde beispielsweise in HERE North America geändert |
10.3 | Not ported over to ArcGIS Pro 1.0 Dem Parameter provider wurde eine neue Option hinzugefügt: NAVTEQ Oceania |
10.1 | New at this version |
Netzwerk aktualisieren
| Version | Beschreibung |
|---|---|
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.