The tables below catalog changes made to every tool in the Spatial Statistics 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.
Average Nearest Neighbor
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | The derived output parameter name changed from HTML_Report_File to Report_File. |
10.0 | Three new derived output parameters were added:
The Display_Output_Graphically parameter name was changed to Generate_Report and the pop-up graphical results were replaced with a report file. While still supporting previous formats, for consistency, the format of the Distance_Method parameter options were changed to:
|
9.3 | New derived output parameter added: PValue |
9.0 | New at this version |
Calculate Areas
| Version | Description |
|---|---|
10.5 | Deprecated. Tool deprecated because there are now easier and more efficient ways to get the area of features such as the Calculate Field tool or the Geometry Calculator. |
10.3 | Not ported to ArcGIS Pro 1.0 |
9.0 | New at this version |
Calculate Distance Band from Neighbor Count
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.0 | While still supporting previous formats, for consistency, the format of the Distance_Method parameter options were changed to:
|
9.2 | New at this version |
Central Feature
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.0 |
While still supporting previous formats, for consistency, the format of the Distance_Method parameter options were changed to:
|
9.3 | New parameter added: Case_Field |
9.0 | New at this version |
Cluster and Outlier Analysis (Anselin Local Moran's I)
| Version | Description |
|---|---|
10.5.1 | The symbology for the Not Significant result category changed from RGB (255, 255, 191) to RGB (247, 247, 242). |
10.5 | Environment added: Random number generator New parameter added: Number_of_Permutations |
10.3 | Ported to ArcGIS Pro 1.0 |
10.2 | New parameter added: Apply_False_Discovery_Rate__FDR__Correction |
10.1 | New derived output parameter added: Source_ID The Conceptualization_of_Spatial_Relationships parameter has two new options:
The CONTIGUITY_EDGES_ONLY replaces the POLYGON_CONTIGUITY_(FIRST_ORDER) option (removed). |
10.0 |
While still supporting previous formats, for consistency, the format of the Distance_Method parameter options were changed to:
While still supporting previous formats, for consistency, the format of the Conceptualization_of_Spatial_Relationships parameter options were changed to:
|
9.3 | Two new derived output parameters were added:
With the ability to calculate suggested distance values, the distance_band_or_threshold_distance parameter changed from Required to Optional. |
9.0 | New at this version |
Cluster/Outlier Analysis with Rendering
| Version | Description |
|---|---|
10.5 | Deprecated. Tool deprecated. Due to new capabilities that allow output from script and model tools to be associated with default rendering, this functionality has been included in the automatic output of the Cluster and Outlier Analysis (Anselin Local Moran's I) tool. |
10.3 | Not ported to ArcGIS Pro 1.0 |
9.0 | New at this version |
Collect Events
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
9.0 | New at this version |
Collect Events with Rendering
| Version | Description |
|---|---|
10.5 | Deprecated. Tool deprecated. Due to new capabilities that allow output from script and model tools to be associated with default rendering, this functionality has been included in the automatic output of the Collect Events tool. |
10.3 | Not ported to ArcGIS Pro 1.0 |
10.1 |
The Output_Layer_File parameter was renamed to Output_Layer. |
9.0 | New at this version |
Convert Spatial Weights Matrix to Table
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
9.3 | New at this version |
Count Rendering
| Version | Description |
|---|---|
10.5 | Deprecated. Tool deprecated. Due to new capabilities that allow output from scripts and model tools to be associated with default rendering, this functionality has been included in the automatic output of the Collect Events tool. |
10.3 | Not ported to ArcGIS Pro 1.0 License changed from Basic to Advanced |
10.0 | Parameter name case changes:
|
9.0 | New at this version |
Directional Distribution (Standard Deviational Ellipse)
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.0 | While still supporting previous formats, for consistency, the format of the Ellipse_Size parameter options were changed to:
|
9.2 | A critical bug fix corrected the algorithm for calculated standard deviational ellipses; they were not calculated correctly prior to the 9.2 release. To correct a typo, Output_Ellipse_Feature_Class replaced the Ouput_Ellipse_Feature_Class parameter. |
9.0 | New at this version |
Linear Directional Mean
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.0 | The options for the boolean parameter, Orientation_Only, were clarified:
|
9.0 | New at this version |
Exploratory Regression
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | New at this version |
Export Feature Attribute To ASCII
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | Parameter name case change: from Output_Ascii_File to Output_ASCII_File New boolean parameter added: Add_Field_Names_to_Output |
9.0 | New at this version |
Generate Network Spatial Weights
| Version | Description |
|---|---|
10.4 | Ported to ArcGIS Pro 1.0 The tool UI changed to included a new tool category, Custom Travel Mode Options. In addition, the Network Options category was renamed to Network Analysis Options. These changes do not impact previous workflows or how the tool is called from the Python command line. Two new parameters were added to take advantage of new functionality available with StreetMap Premium for ArcGIS:
|
10.3 | Not ported to ArcGIS Pro 1.0 Required Network Analyst extension specified. |
9.3 | New at this version |
Generate Spatial Weights Matrix
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | Three new parameters added:
The Conceptualization_of_Spatial_Relationships parameter had new option added: SPACE_TIME_WINDOW |
9.3 | New at this version |
Geographically Weighted Regression (GWR)
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.2 | The coefficient_raster_workspace parameter had data type Folder removed |
10.1 | The BANDWIDTH PARAMETER option for the bandwidth_method parameter was renamed to BANDWIDTH_PARAMETER |
9.3 | New at this version |
Grouping Analysis
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | New at this version |
High/Low Clustering (Getis-Ord General G)
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | The derived output parameter name changed from HTML_Report_File to Report_File. The Conceptualization_of_Spatial_Relationships parameter has two new options:
The CONTIGUITY_EDGES_ONLY option replaces POLYGON_CONTIGUITY_(FIRST_ORDER) (removed). |
10.0 | A new derived output parameter was added: HTML_Report_File. The Display_Output_Graphically parameter name was changed to Generate_Report and the pop-up graphical results were replaced with a report file. While still supporting previous formats, for consistency, the format of the Distance_Method parameter options were changed to:
While still supporting previous formats, for consistency, the format of the Conceptualization_of_Spatial_Relationships parameter options were changed to:
|
9.3 | New derived output parameter added: PValue With the ability to calculate suggested distance values, the distance_band_or_threshold_distance parameter changed from Required to Optional. |
9.2 | Critical bug fix to correct calculation of variance. |
9.0 | New at this version |
Hot Spot Analysis (Getis-Ord Gi*)
| Version | Description |
|---|---|
10.5.1 | The symbology for the Not Significant result category changed from RGB (255, 255, 191) to RGB (247, 247, 242). |
10.3 | Ported to ArcGIS Pro 1.0 |
10.2 | New parameter added: Apply_False_Discovery_Rate__FDR__Correction |
10.1 | New derived output parameter added: Source_ID The Conceptualization_of_Spatial_Relationships parameter has two new options:
The CONTIGUITY_EDGES_ONLY replaces the POLYGON_CONTIGUITY_(FIRST_ORDER) option (removed). |
10.0 | While still supporting previous formats, for consistency, the format of the Distance_Method parameter options were changed to:
While still supporting previous formats, for consistency, the format of the Conceptualization_of_Spatial_Relationships parameter options were changed to:
|
9.3 | New derived outputparameter added: Probability_Field With the ability to calculate suggested distance values, the distance_band_or_threshold_distance parameter changed from Required to Optional. |
9.0 | New at this version |
Hot Spot Analysis with Rendering
| Version | Description |
|---|---|
10.5 | Deprecated. Tool deprecated. Due to new capabilities that allow output from script and model tools to be associated with default rendering, this functionality has been included in the automatic output of the Hot Spot Analysis (Getis-Ord Gi*) tool. |
10.3 | Not ported to ArcGIS Pro 1.0 |
9.3 | With the ability to calculate suggested distance values, the distance_band_or_threshold_distance parameter changed from Required to Optional. |
9.1 | New parameter added: Distance_Band_or_Threshold_Distance |
9.0 | New at this version |
Incremental Spatial Autocorrelation
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | New at this version |
Mean Center
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
9.0 | New at this version |
Median Center
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.0 | New at this version |
Multi-Distance Spatial Cluster Analysis (Ripley's K Function)
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | Critical bug fix for incorrect results when you select SIMULATE_OUTER_BOUNDARY_VALUES for the Boundary Correction Methodand elect to Compute Confidence Envelope. |
10.0 | New derived output parameter added: Result_Image The Display_Results_Graphically parameters were clarified to be:
While still supporting other formats, for consistency, the Compute_Confidence_Envelope parameter options were changed to:
While still supporting other formats, for consistency, the Study_Area_Method parameter options were changed to:
While still supporting other formats, for consistency, the Boundary_Correction_Method parameter options were changed to:
|
9.2 | New at this version |
Optimized Hot Spot Analysis
| Version | Description |
|---|---|
10.5.1 | The symbology for the Not Significant result category changed from RGB (255, 255, 191) to RGB (247, 247, 242). |
10.5 | The Density_Surface parameter has been disabled and the following Environments removed:
2 new parameters added:
Parameter Incident_Data_Aggregation_Method had new option added: COUNT_INCIDENTS_WITHIN_HEXAGON_POLYGONS |
10.3 | Ported to ArcGIS Pro 1.0 Algorithm to compute cell size changed. Most notably, this change resulted in cell sizes matching regardless of whether or not a feature class for the Bounding Polygons Defining Where Incidents Are Possible parameter is specified. |
10.2 | New at this version |
Optimized Outlier Analysis
| Version | Description |
|---|---|
10.5.1 | The symbology for the Not Significant result category changed from RGB (255, 255, 191) to RGB (247, 247, 242). |
10.5 | New at this version |
Ordinary Least Squares (OLS)
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | New parameter added: Output_Report_File |
9.3 | New at this version |
Similarity Search
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.2.1 | New at this version |
Spatial Autocorrelation (Global Moran's I)
| Version | Description |
|---|---|
10.3 | Ported to ArcGIS Pro 1.0 |
10.1 | The derived output parameter name changed from HTML_Report_File to Report_File. The Conceptualization_of_Spatial_Relationships parameter has two new options:
The CONTIGUITY_EDGES_ONLY option replaces POLYGON_CONTIGUITY_(FIRST_ORDER) (removed). |
10.0 | A new derived output parameter was added: HTML_Report_File. The Display_Output_Graphically parameter name was changed to Generate_Report and the pop-up graphical results were replaced with a report file. While still supporting previous formats, for consistency, the format of the Distance_Method parameter options were changed to:
While still supporting previous formats, for consistency, the format of the Conceptualization_of_Spatial_Relationships parameter options were changed to:
|
9.3 | New parameter added: PValue With the ability to calculate suggested distance values, the distance_band_or_threshold_distance parameter changed from Required to Optional. |
9.2 | A critical bug was fixed correcting results for standardized weights; analyses with standardized weights prior to the 9.2 release were incorrect. |
9.0 | New at this version |
Standard Distance
| Version | Description |
|---|---|
10.5 | Environment added: Output Z Domain |
10.3 | Ported to ArcGIS Pro 1.0 |
10.0 | While still supporting previous formats, for consistency, the format of the Circle_Size parameter were changed to:
|
9.2 | To correct a typo, Output_Standard_Distance_Feature_Class replaced the Ouput_Standard_Distance_Feature_Class parameter. |
9.0 | New at this version |
ZScore Rendering
| Version | Description |
|---|---|
10.5 | Deprecated. Tool deprecated. This functionality has been included in automatic outputs of the Hot Spot Analysis (Getis-Ord Gi*) and Cluster and Outlier Analysis (Anselin Local Moran's I) tools. |
10.3 | Not ported to ArcGIS Pro 1.0 License changed from Basic to Advanced |
10.0 | Parameter name case changes:
|
9.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.
As an example of how you might use these history tables, suppose you are helping a colleague who is using version 10.2 while you're using version 10.3. You might suggest to your colleague that they use the Add Geometry Attributes tool to find point centroids of polygon features. The Add Geometry Attributes tool is found in the Data Management toolbox, and checking the Data Management toolbox history topic, you find that Add Geometry Attributes was not introduced until the 10.2.1 release. You can then suggest a 10.2 workflow of using the Feature To Point tool to find polygon centroids.
When changes are made to existing tools, every effort is made to maintain backward compatibility, meaning that the use of a tool in the previous release continues to work in the new release. That is, suppose you have a model or script written in version 10.2 that uses the Buffer tool. At version 10.3, the Buffer tool has a new optional parameter, method, with the default value of PLANAR. Your 10.2 script or model will work in 10.3 because the new method parameter is optional and its default value causes Buffer to work exactly the same way it did in 10.2.
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 Desktop Advanced to Desktop 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.
Ported / Not ported to ArcGIS Pro
If you're transitioning from ArcMap to ArcGIS Pro, you may need to know whether a tool in ArcMap is also available in ArcGIS Pro. The majority of tools found in version 10.3 were ported over to (that is, replicated and made available in) ArcGIS Pro version 1.0. Information about whether the tool was ported over from ArcMap to the ArcGIS Pro platform is usually contained in the first row of the table. Note that you can use the Analyze Tools For Pro tool to check whether your ArcMap models and scripts will run in ArcGIS Pro.
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.