Choose area layer to summarize other features within its boundaries

The area layer that will be used to summarize features that fall within its boundaries. You can choose to summarize within a polygon layer that you provide or within square or hexagon bins that are generated when the tool runs. When generating bins, for Square, the number and units specified determine the height and length of the square. For Hexagon, the number and units specified determine the distance between parallel sides.

Analysis using Square or Hexagon bins 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.

Choose layer to summarize

Features in this layer that fall within the boundaries of features in the input layer, or bins specified above, will be summarized.

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.

Choose a distance to generate bins and aggregate into

The distance used to generate bins.

Either Bin Size for bins or Area Layer must be set.

Aggregate using time slices (optional)

If time is enabled on the input point layer and it is of type instant, you can analyze using time stepping. There are three parameters you can set when you use time:

• Time step interval
• How often to repeat the time step
• Time to align the time steps to

For example, if you have data that represents a year in time and you want to analyze it using weekly steps, set Time step interval to 1 week.

For example, if you have data that represents a year in time and you want to analyze it using the first week of the month, set Time step interval to 1 week, How often to repeat the time step to 1 month, and Time to align the time steps to to January 1, at 12:00 am.

Time interval to be aggregate into

The interval of time used for generating time steps. Time step interval can be used alone or with the How often to repeat the time step or Time to align the time steps to parameter.

For example, if you want to create time steps that take place every Monday from 9:00 a.m. until 10:00 a.m., set Time step interval to 1 hour, How often to repeat the time step to 1 week, and Time to align the time steps to to 9:00:00 a.m. on a Monday.

Time step to be aggregate into

The step used for calculating a time step. How often to repeat the time step can be used alone, with Time step interval, with Reference Time, or with both Time step interval and Time to align the time steps to.

For example, if you want to create time steps that take place every Monday from 9:00 a.m. until 10:00 a.m., set Time step interval to 1 hour, How often to repeat the time step to 1 week, and Time to align the time steps to to 9:00:00 a.m. on a Monday.

Reference time used to align the time slicing

The date and time used to align time slicing. Time stepping will start at and continue backward from this time. If no reference time is selected, time stepping will align to January 1st, 1970.

For example, if you want to create time steps that take place every Monday from 9:00 a.m. until 10:00 a.m., set Time step interval to 1 hour, How often to repeat the time step to 1 week, and Time to align the time steps to to 9:00:00 a.m. on a Monday.

Add statistics (optional)

You can calculate statistics on features that are summarized. You can calculate the following on numeric fields:

• Count—Calculates the number of nonnull values. It can be used on numeric fields or strings. The count of [null, 0, 2] is 2.
• Sum—The sum of numeric values in a field. The sum of [null, null, 3] is 3.
• Mean—The mean of numeric values. The mean of [0, 2, null] is 1.
• Min—The minimum value of a numeric field. The minimum of [0, 2, null] is 0.
• Max—The maximum value of a numeric field. The maximum value of [0, 2, null] is 2.
• Range—The range of a numeric field. This is calculated as the minimum values subtracted from the maximum value. The range of [0, null, 1] is 1. The range of [null, 4] is 0.
• Variance—The variance of a numeric field in a track. The variance of [1] is null. The variance of [null, 1,0,1,1] is 0.25.
• Standard deviation—The standard deviation of a numeric field. The standard deviation of [1] is null. The standard deviation of [null, 1,0,1,1] is 0.5.

You can calculate the following on string fields:

• Count—The number of nonnull strings.
• Any—This statistic is a random sample of a string value in the specified field.

In addition to these statistics, proportional statistics will be calculated on all numeric fields:

• Count—The count of each field multiplied by the proportion of the summary layer within the polygons.
• Sum—The sum of weighted of values in each field. Where the weight applied is the proportion of the summary layer within the polygons.
• Mean—The weighted mean of values in each field. Where the weight applied is the proportion of the summary layer within the polygons.
• Min—The minimum of weighted values in each field. Where the weight applied is the proportion of the summary layer within the polygons.
• Max—The maximum of weighted values in each field. Where the weight applied is the proportion of the summary layer within the polygons.
• Range—The difference between the maximum and minimum weighted values.

Depending on the types of features you are summarizing, the total count of nearby points, total length of lines, or total area will be calculated.

Choose field to group by

This is an attribute of the Summarize features that you can use to calculate statistics separately for each unique attribute value. For example, suppose the first input layer contains city boundaries and the summary features are parcels. One of the attributes of the parcels is Status which contains two values: VACANT and OCCUPIED. To calculate the total area of vacant and occupied parcels within the boundaries of cities, use Status as the group by attribute. The statistics for each group, as well as the count of features within each area boundary, will be displayed in the result layer's pop-up.

Add minority, majority

This checkbox is enabled when you choose a field to group by. If you want to find out which attribute values within each group are the minority (least dominant) or the majority (most dominant) within each boundary of the first input layer, select Add minority, majority. When you select Add minority, majority, two new fields are added to your result layer. If you also select Add percentages, two additional fields are added to the result layer containing the percentages of the minority and majority attribute values within each group.

• If you are summarizing points, minority and majority values are calculated based on the count of points within each bounding area in the input area layer.
• If you are summarizing lines, minority and majority values are calculated based on the length of lines within each bounding area in the input area layer.
• If you are summarizing areas, minority and majority values are calculated based on the areas within each bounding area in the input area layer.

Add percentages

This check box is enabled when you choose a field to group by. Select Add percentages if you want to find the percentage of each attribute value within each group. A new field is added to the result table containing the percentages of each attribute value within each group. If Add minority, majority is also checked, two additional fields are added to the result layer containing the percentages of the minority and majority attribute values within each group.

Choose datastore

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.

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.