Find Hot Spots

Find Hot Spots


The Find Hot Spots tool will determine if there is any statistically significant clustering in the spatial pattern of your data.

The Find Hot Spots tool will help you answer these questions with confidence.

Even random spatial patterns exhibit some degree of clustering. In addition, our eyes and brains naturally try to find patterns even when none exist. Consequently, it can be difficult to know if the patterns in your data are the result of real spatial processes at work or just the result of random chance. This is why researchers and analysts use statistical methods such as Find Hot Spots (Getis-Ord Gi*) to quantify spatial patterns. When you do find statistically significant clustering in your data, you have valuable information. Knowing where and when clustering occurs can provide important clues about the processes promoting the patterns you're seeing. Knowing that residential burglaries, for example, are consistently higher in particular neighborhoods is vital information if you need to design effective prevention strategies, allocate scarce police resources, initiate neighborhood watch programs, authorize in-depth criminal investigations, or identify potential suspects.

Choose layer for which hot spots will be calculated


The point layer from which hot and cold spots will be found.

This analysis uses bins and requires a projected coordinate system. You can set the Processing coordinate system in Analysis Environments. If your processing coordinate system is not set to a projected coordinate system, you will be prompted to set it when you Run Analysis .

In addition to choosing a layer from your map, you can choose Choose Analysis Layer at the bottom of the drop-down list to browse to your contents for a big data file share dataset or feature layer.

Find clusters of high and low


This analysis answers the question: Where do high and low values cluster spatially?

If your data is points and you choose Point Counts, this tool will evaluate the spatial arrangement of the point features to answer the question: Where are points unexpectedly clustered or spread out?

If you choose a field, this tool will evaluate the spatial arrangement of the values associated with each feature to answer the question: Where are high and low values clustering?

Select the bin size for aggregation


The distance used to generate the square bins that will be used to analyze your input points.

Find hot spots using time steps (optional)


If time is enabled on the point layer, and it's of type instant, you can analyze using time steps.

Time step interval


Interval of time used for generating time steps. Time can be aligned to the start or end time of the input data or to a specified reference time.

Time step interval


Interval of time used for generating time steps. Time can be aligned to the start or end time of the input data or to a specified reference time.

Choose how to align time steps


How time steps are aligned. There are three ways to align time steps:

  • Start Time—Time steps are aligned with the first feature in time.
  • End Time—Time steps are aligned with the last feature in time.
  • Reference Time—Time steps are aligned with a specified time.

Reference time to align time steps to


The date and time used to align the time steps.

Select the neighborhood size for hot spot calculations


The distance used to determine the neighborhood used for hot spot calculations. The neighborhood should be larger than the bin size to ensure that each bin has at least one neighbor. Each bin is analyzed and compared to the neighboring bins.

SpatialReference (wkid)


This is a temporary parameter for prerelease to set the processing spatial reference. Many big data tools require that a projected coordinate system is used as the spatial reference for processing. By default, the tool will use the input coordinate system but will fail if it's a geographic coordinate system. To set a projected coordinate system, enter the WKID. For example, Web Mercator would be entered as 3857.

Choose an ArcGIS Data Store to save results to


GeoAnalytics results are stored to an data store and exposed as a feature layer in Portal for ArcGIS. In most cases, results should be stored to the spatiotemporal data store and this is the default. In some cases, saving results to the relational data store is a good option. The following are reasons why you may want to store results to the relational data store:

  • You can use results in portal-to-portal collaboration.
  • You can enable sync capabilities with your results.

You should not use the relational data store if you expect your GeoAnalytics results to increase and need to take advantage of the spatiotemporal big data store's capabilities to handle large amounts of data.

Result layer name


The name of the layer that will be created. If you are writing to an ArcGIS Data Store, your results will be saved in My Content and added to the map. If you are writing to a big data file share, your results will be stored in the big data file share and added to its manifest. It will not be added to the map. The default name is based on the tool name and the input layer name. If the layer already exists, the tool will fail.

This result layer will show you statistically significant clusters of high and low values or point counts. If the result layer name already exists, you will be asked to rename it.

When writing to ArcGIS Data Store (relational or spatiotemporal big data store) using the Save result in drop-down box, you can specify the name of a folder in My Content where the result will be saved.