Skip To Content

Manage Feature Bin Cache

Summary

Manages the feature binning cache for data with feature binning enabled.

Feature binning aggregates large amounts of point features into dynamic polygon bins that vary through scaled levels of detail. Learn how to enable feature binning and work with binned feature layers

Usage

  • Use this tool when feature binning has been enabled on a feature class and a static cache has been generated. If the underlying data has changed, run this tool to update the cache to reflect the most recent state of the data. If you run this tool on a feature class without a static cache, a static cache is generated. Use this tool to add or delete summary statistics that are stored in the cache, or to modify the cache level of detail.

  • Feature binning is only supported for point and multipoint feature classes stored in an enterprise geodatabase or database on the following platforms:

    • IBM Db2
    • Microsoft SQL Server
    • Oracle
    • PostgreSQL
    • SAP HANA
    However, because aggregated results are not cached for bins in SAP HANA, this tool is not needed or supported for SAP HANA data.

  • Use the Level of Detail parameter to specify the maximum level of detail for the tiling scheme to include in the cache. Tiling schemes are a continuum of scale ranges. Depending on your map, you may want to forego caching of some of the extremely large or small scales in your tiling scheme. Choose a level of detail that most closely matches the intended use of the map in which the data will be shown.

Syntax

ManageFeatureBinCache(in_features, {bin_type}, {max_lod}, {add_cache_statistics}, {delete_cache_statistics})
ParameterExplanationData Type
in_features

The binning-enabled feature class that will have its static cache updated.

Feature Layer
bin_type
(Optional)

Specifies the type of binning that will be enabled. If you are using SAP HANA data, only square bins are supported.

  • FLAT_HEXAGONA binning scheme that is also known as flat geohex or flat hexbinning. The tiles are a tessellation of hexagons in which the orientation of the hexagons has a flat edge of the hexagon on top. This is the default for Microsoft SQL Server, Oracle, and PostgreSQL data.
  • POINTY_HEXAGONA binning scheme that is also known as pointy geohex or pointy hexbinning. The tiles are a tessellation of hexagons in which the orientation of the hexagons has a point of the hexagon on top.
  • SQUAREA binning scheme in which the tiles are a tessellation of squares, also known as geosquare or squarebinning. This is the default for Db2 and SAP HANA data. This is the only bin type available for SAP HANA data.
  • GEOHASHA binning scheme in which the tiles are a tessellation of rectangles. Because geohash bins always use the WGS 1984 Geographic Coordinate System (GCS WGS 1984, EPSG WKID 4326), you cannot specify a bin coordinate system for geohash bins.
String
max_lod
(Optional)

Specifies the maximum level of detail that will be used for the cache.

Tiling schemes are a continuum of scale ranges. Depending on your map, you may want to forego caching of some of the extremely large or small scales in your tiling scheme. This tool examines the scale dependencies in your map and attempts to provide a maximum range of scale for caching. Choose a level of detail that most closely matches the intended use of the map in which the data will be shown.

  • WORLDA world scale will be used as the maximum level of detail.
  • CONTINENTSMultiple continents scale will be used as the maximum level of detail.
  • CONTINENTA single continent scale will be used as the maximum level of detail.
  • COUNTRIESMultiple countries scale will be used as the maximum level of detail.
  • COUNTRYA single country scale will be used as the maximum level of detail.
  • STATESMultiple states scale will be used as the maximum level of detail.
  • STATEA single state scale will be used as the maximum level of detail.
  • COUNTIESMultiple counties scale will be used as the maximum level of detail.
  • COUNTYA single county scale will be used as the maximum level of detail.
  • CITIESMultiple cities scale will be used as the maximum level of detail.
  • CITYA single city scale will be used as the maximum level of detail.
String
add_cache_statistics
[[Field, Statistic Type],...]
(Optional)

Specifies the statistics that will be summarized and stored in the bin cache. Statistics are used to symbolize bins and provide aggregate information for all the points in a bin. One summary statistic, shape_count (which is the total feature count), is always available.

  • Field—The field on which to calculate the summary statistics. Supported field types are short, long, float, and double.
  • Statistic Type—The type of statistic to calculate for the specified field. Statistics are calculated for all features in the bin. Available statistics types are as follows:
    • Mean (AVG)—Calculates the average for the specified field.
    • Minimum (MIN)—Finds the smallest value for all records of the specified field.
    • Maximum (MAX)—Finds the largest value for all records of the specified field.
    • Standard deviation (STDDEV)—Calculates the standard deviation value for the field.
    • Sum (SUM)—Adds the total value for the specified field.

Value Table
delete_cache_statistics
[delete_cache_statistics,...]
(Optional)

The summary statistic that will be deleted from the cache. You cannot delete the default COUNT summary statistic.

String

Derived Output

NameExplanationData Type
out_features

The input features with the updated feature bin cache.

Feature Layer

Code sample

ManageFeatureBinCache example (Python window)

Add a new statistic to calculate the maximum depth and set the level of detail of the feature bin cache for a feature layer named Earthquakes.

import arcpy
arcpy.ManageFeatureBinCache_management("lod_gdb.elec.Earthquakes", "SQUARE", 
                                       "STATE", "depth_km MAX")

Environments

Licensing information

  • Basic: Yes
  • Standard: Yes
  • Advanced: Yes

Related topics