PROBLEM
In ArcGIS Pro 3.1 to 3.3, application-computed feature binning was introduced. It removed the requirement that a feature class must be stored in an RDBMS (relational database management system) and enabled for binning. Thus, any point feature layer can be aggregated into bins.
If a point feature layer is aggregated, the application checks whether binning is already enabled; if not, application-computed feature bins are generated. Feature classes enabled for binning in ArcGIS Pro 3.0 or earlier compute feature bins from the database by default in ArcGIS Pro 3.1, but this can be switched to application-computed feature binning as well.
When an aggregated point feature layer uses application-side computation to process feature bins, the value range of the bins’ symbology is set to two standard deviations from the mean of the summary field. If this value range is customized or changed, the settings are not saved to the layer or project. When you reopen the project, the settings return to the default setting of 2 standard deviations.
With application-computed feature binning, the CIM (cartographic information model) cannot retain standard deviation multiplier information for each value range level. If a feature class with database binning is enabled, standard deviation information is inferred from the MIN, MAX, MEAN, and STDDEV information stored at each level of the given value range. This information cannot be inferred at each level if database binning is not enabled.
If possible, export the feature layer to a managed database, and enable the feature class for binning. This allows the database to process and store standard deviation value range settings. Otherwise, reset the value range of the bin levels to the desired values.
Article ID: 000029489
Get help from ArcGIS experts
Download the Esri Support App