Les tables ci-dessous répertorient les modifications apportées à chaque outil de la boîte à outils Network Analyst. Il existe une table par outil et vous pouvez cliquer sur le nom de l'outil pour accéder à la page de référence de l'outil. Pour plus d'informations sur l'interprétation du contenu de ces tables d'historique, consultez la section figurant à la fin de cette rubrique.
Ajouter un champ à la couche d’analyse
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
Ajouter des localisations
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10,0 | 2 nouveaux paramètres ajoutés :
|
9.2 | 3 nouveaux paramètres ajoutés :
Paramètre supprimé : snapcontrol |
9.1 | New at this version |
Construire le réseau
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nouveau paramètre ajouté : out_network_dataset |
9.1 | New at this version |
Calculer les localisations
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10,0 | 4 nouveaux paramètres ajoutés :
|
9.2 | New at this version |
Copier les entités source traversées
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | New at this version |
Créer une classe d’entités tournants
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10,0 | Nouveau paramètre ajouté : has_z |
9.1 | New at this version |
Feuilles de route
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 3 nouveaux paramètres ajoutés :
Nouvelle option ajoutée pour le paramètre file_type : HTML |
10,0 | Nouveau paramètre ajouté : output_layer |
9.3 | Nouvelle option ajoutée pour le paramètre report_units : NauticalMiles |
9.1 | New at this version |
Fusion du réseau
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10,0 | New at this version |
Rechercher les ressources les plus proches
| Version | Description |
|---|---|
10.4 | Option CUSTOM supprimée pour le paramètre Travel_Mode |
10.3 | Not ported over to ArcGIS Pro 1.0 Extension obligatoire modifiée de none en Network Analyst Nouveau paramètre ajouté : Travel_Mode |
10.2.1 | New at this version |
Rechercher un itinéraire
| Version | Description |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
Générer des zones de desserte
| Version | Description |
|---|---|
10.4 | Option CUSTOM supprimée pour le paramètre Travel_Mode |
10.3 | Not ported over to ArcGIS Pro 1.0 Extension obligatoire modifiée de none en Network Analyst Nouveau paramètre ajouté : Travel_Mode |
10.2.1 | Nouveau paramètre ajouté : Time_Zone_for_Time_of_Day |
10.2 | Nouveau paramètre ajouté : Save_Output_Network_Analysis_Layer |
10.1 | New at this version |
Augmenter le nombre maximal de tronçons
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nouveau paramètre ajouté : out_turn_features |
9.1 | New at this version |
Générer une couche des ressources les plus proches
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 nouveaux paramètres ajoutés :
|
10,0 | Nouvelle option ajoutée pour le paramètre UTurn_policy : ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
Créer une couche emplacement-allocation
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 nouveaux paramètres ajoutés :
Nouvelle option ajoutée pour le paramètre loc_alloc_problem_type : MAXIMIZE_CAPACITATED_COVERAGE |
10,0 | New at this version |
Créer une couche de matrice de coût OD
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | Nouveau paramètre ajouté : time_of_day |
10,0 | Nouvelle option ajoutée pour le paramètre UTurn_policy : ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.1 | New at this version |
Générer une couche d'itinéraires
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10,0 | Nouvelle option ajoutée pour le paramètre UTurn_policy : ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | Nouveau paramètre ajouté : start_date_time |
9.1 | New at this version |
Générer une couche de zones de desserte
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | 2 nouveaux paramètres ajoutés :
|
10,0 | Nouvelle option ajoutée pour le paramètre UTurn_policy : ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.2 | 3 nouveaux paramètres ajoutés :
|
9.1 | New at this version |
Créer une couche d’optimisation des tournées de véhicules
| Version | Description |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 |
10,0 | Nouvelle option ajoutée pour le paramètre UTurn_policy : ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY |
9.3 | New at this version |
Renseigner les champs d’ID de substitution
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nouveau paramètre ajouté : out_network_dataset |
9.1 | New at this version |
Rechercher
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
10.1 | Nouveau paramètre ajouté : simplification_tolerance |
10,0 | 2 nouveaux paramètres ajoutés :
|
9.2 | Nouveau paramètre ajouté : ignore_invalids |
9.1 | New at this version |
Résoudre emplacement-allocation
| Version | Description |
|---|---|
10.4 | Option CUSTOM supprimée pour le paramètre Travel_Mode |
10.3 | Not ported over to ArcGIS Pro 1.0 New at this version |
Résoudre la tournée de véhicules
| Version | Description |
|---|---|
10.3 | Not ported over to ArcGIS Pro 1.0 2 nouveaux paramètres ajoutés :
|
10.1 | New at this version |
Table de tournants vers classe d'entités tournants
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.1 | New at this version |
Mise à jour du paramètre d’attribut d’analyse de la couche
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | New at this version |
Mettre à jour par des champs d’ID de substitution
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nouveau paramètre ajouté : out_network_dataset |
9.1 | New at this version |
Mettre à jour selon la géométrie
| Version | Description |
|---|---|
10.3 | Ported over to ArcGIS Pro 1.0 |
9.2 | Nouveau paramètre ajouté : out_turn_features |
9.1 | New at this version |
Mettre à jour les données de trafic
| Version | Description |
|---|---|
10.4 | Les options provider de NAVTEQ ont été modifiées en HERE. Par exemple, NAVTEQ North America a été modifié en HERE North America |
10.3 | Not ported over to ArcGIS Pro 1.0 |
10.2.1 | Nouveau paramètre ajouté : speed_unit |
10.2 | Nouvelle option ajoutée pour le paramètre provider : INRIX |
10.1.1 | Nouvelle option ajoutée pour le paramètre provider : NAVTEQ South East Asia |
10.1 | New at this version |
Mettre à jour les incidents de trafic
| Version | Description |
|---|---|
10.4 | Les options provider de NAVTEQ ont été modifiées en HERE. Par exemple, NAVTEQ North America a été modifié en HERE North America |
10.3 | Not ported over to ArcGIS Pro 1.0 Nouvelle option ajoutée pour le paramètre provider : NAVTEQ Oceania |
10.1 | New at this version |
Mettre à niveau le réseau
| 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 Avancé 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.