{"id":2642652,"date":"2025-04-07T15:35:17","date_gmt":"2025-04-07T22:35:17","guid":{"rendered":"https:\/\/www.esri.com\/arcgis-blog\/?post_type=blog&p=2642652"},"modified":"2025-09-25T10:17:18","modified_gmt":"2025-09-25T17:17:18","slug":"attribute-rules-generate-spatial-join","status":"publish","type":"blog","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-spatial-join","title":{"rendered":"Template Attribute Rules – Generate Spatial Join"},"author":365172,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_acf_changed":false,"_searchwp_excluded":""},"categories":[23851],"tags":[42181,302212,86442,777832],"industry":[],"product":[36561],"class_list":["post-2642652","blog","type-blog","status-publish","format-standard","hentry","category-data-management","tag-arcgis-pro","tag-attribute-rules","tag-data-management","tag-template-attribute-rules","product-arcgis-pro"],"acf":{"authors":[{"ID":365172,"user_firstname":"Mihail","user_lastname":"Kaburis","nickname":"Mihail Kaburis","user_nicename":"mkaburis","display_name":"Mihail Kaburis","user_email":"mkaburis@esri.com","user_url":"","user_registered":"2024-11-20 00:37:26","user_description":"","user_avatar":""}],"short_description":"Generate Spatial Join template attribute rules populate fields within an input dataset based on spatial relationships with other datasets.","flexible_content":[{"acf_fc_layout":"content","content":"

In ArcGIS Pro 3.4 we have introduced three new Template Attribute Rules<\/a> that allow you to generate attribute rules tailored to specific workflows. We took some of the most commonly used attribute rules and created a geoprocessing (GP) tool experience to guide you through their creation process. This enhancement not only speeds up the generation of these rules but also makes them more accessible for users who may not have prior knowledge of Arcade scripting.<\/p>\n

This blog describes a workflow of creating and utilizing a Generate Spatial Join template attribute rule to determine the number of lots and average property values of a few parcels in New Haven, Connecticut.<\/p>\n

Spatial joins facilitate analysis and retrieval of information from multiple feature classes based on their spatial relationships. This means that an explicit attribute indicating that \u201cfeature class A is inside of feature class B\u201d is unnecessary. Instead, we utilize the inherent relationships between features to determine if they are spatially joined to one another. The spatial relationship between parcels and lots is quite intuitive: parcels contain<\/em> lots.<\/p>\n

Here\u2019s what our data looks like (note:<\/em> <\/strong>the light green polygons represent parcels and the yellow polygons represent lots):<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2681222,"id":2681222,"title":"GenerateSpatialJoin_Parcels","filename":"GenerateSpatialJoin_Parcels.png","filesize":703733,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-spatial-join\/generatespatialjoin_parcels","alt":"","author":"365172","description":"","caption":"","name":"generatespatialjoin_parcels","status":"inherit","uploaded_to":2642652,"date":"2025-02-13 01:19:05","modified":"2025-02-13 01:19:05","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":620,"height":443,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels.png","medium-width":365,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels.png","medium_large-width":620,"medium_large-height":443,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels.png","large-width":620,"large-height":443,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels.png","1536x1536-width":620,"1536x1536-height":443,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels.png","2048x2048-width":620,"2048x2048-height":443,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels.png","card_image-width":620,"card_image-height":443,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_Parcels.png","wide_image-width":620,"wide_image-height":443}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

Manually counting the number of lots within each parcel and determining their respective average property values can be a tedious and error-prone process. This task becomes even more daunting when it expands beyond the few lots in a city to encompass the entire county or even a whole state such as Connecticut. Additionally with frequent changes in urban landscapes, it is crucial for parcel data to be regularly updated for taxation and planning purposes. Imagine investing significant effort to obtain precise counts, only to find that you need to recount later. Not to worry though! As GIS professionals, we have a solution to streamline this process!<\/p>\n

Here\u2019s a brief overview video of the Generate Spatial Join Attribute Rule tool:<\/p>\n"},{"acf_fc_layout":"kaltura","video_id":"1_ixg5uqnz","time":false,"start":0,"stop":""},{"acf_fc_layout":"content","content":"

Utilizing the Generate Spatial Join Tool<\/strong><\/h2>\n

Review Generate Spatial Join Data<\/strong><\/h3>\n

Note:<\/strong>\u00a0Attribute Rules\u00a0<\/span>require<\/span>\u00a0an\u00a0<\/span>ArcGIS Pro\u00a0<\/span>S<\/span>tandard or\u00a0<\/span>A<\/span>dvance<\/span>d<\/span>\u00a0license level. To learn more please refer to the\u00a0ArcGIS Pro license levels help documentation<\/a>.<\/span><\/span><\/p>\n

    \n
  1. Download the\u00a0<\/span>TemplatedARs_SpatialJoin.ppkx<\/span><\/a> project package file and then click on the file to open the TemplatedARs_SpatialJoin project. This project contains the data to step through the workflow in this blog.<\/span><\/li>\n
  2. The project opens with the New Haven Lots and Parcels map active. The map contains two polygon feature classes representing lots and parcels.<\/li>\n<\/ol>\n

     <\/p>\n

    Let\u2019s go ahead and determine the number of parcels and average property values within the example data.<\/p>\n

    The first thing we are going to want to do is right click on the Parcels layer in the Table of Contents pane and select Data Design<\/strong> > Attribute Rules <\/strong>to open the Attribute Rules Data Design View.<\/p>\n

    In the Attribute Rules tab of the ribbon click on the bottom half of the Calculation Rules button. In the Context Menu go to Templates > Generate Spatial Join<\/strong>.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2718712,"id":2718712,"title":"GenerateSpatialJoin_TemplateOption","filename":"GenerateSpatialJoin_TemplateOption.png","filesize":46599,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-spatial-join\/generatespatialjoin_templateoption","alt":"","author":"365172","description":"","caption":"","name":"generatespatialjoin_templateoption","status":"inherit","uploaded_to":2642652,"date":"2025-03-05 22:56:08","modified":"2025-03-05 22:56:08","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":460,"height":231,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption.png","medium-width":460,"medium-height":231,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption.png","medium_large-width":460,"medium_large-height":231,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption.png","large-width":460,"large-height":231,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption.png","1536x1536-width":460,"1536x1536-height":231,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption.png","2048x2048-width":460,"2048x2048-height":231,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption.png","card_image-width":460,"card_image-height":231,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/02\/GenerateSpatialJoin_TemplateOption.png","wide_image-width":460,"wide_image-height":231}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    The Generate Spatial Join Attribute Rule GP tool dialog opens. Accessing the tool via the Attribute Rules Data Design View automatically selects the Parcels feature class as the Input Table <\/strong>for which the attribute rule will be created on.<\/p>\n

    Tool Overview<\/strong><\/h3>\n"},{"acf_fc_layout":"image","image":{"ID":2718732,"id":2718732,"title":"GenerateSpatialJoin_ToolUI","filename":"GenerateSpatialJoin_ToolUI.png","filesize":31655,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-spatial-join\/generatespatialjoin_toolui","alt":"","author":"365172","description":"","caption":"","name":"generatespatialjoin_toolui","status":"inherit","uploaded_to":2642652,"date":"2025-03-05 22:58:08","modified":"2025-03-05 22:58:08","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":398,"height":590,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI.png","medium-width":176,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI.png","medium_large-width":398,"medium_large-height":590,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI.png","large-width":398,"large-height":590,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI.png","1536x1536-width":398,"1536x1536-height":590,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI.png","2048x2048-width":398,"2048x2048-height":590,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI-314x465.png","card_image-width":314,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_ToolUI.png","wide_image-width":398,"wide_image-height":590}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    Here are the parameters for the tool and how we\u2019ll fill them out:<\/p>\n

      \n
    1. The optional Expression<\/strong> parameter allows us to specify a SQL expression to restrict which features from the Input Table participate with the attribute rule. Since we want all of the Parcel features to participate in the spatial joins, we\u2019ll leave this parameter with the default settings.<\/li>\n
    2. The Join Classes<\/strong> parameter represents the attributes from the join features that will be joined to the attributes of the input features. Go ahead and select the Lots class. To keep things straightforward, we are using a single join class but we could have more!<\/li>\n
    3. The Field Map<\/strong> parameter is next. It controls the mapping of fields from the Join Classes parameter to the Input Table parameter. It might look daunting, but don\u2019t be alarmed! Think of the field mappings as the linkages between the attributes from the Lots feature class to those in our Parcels class.\n
        \n
      1. There are two objectives in our analysis:\n
          \n
        1. Count the number of lots within each parcel.<\/li>\n
        2. Find the average property value of lots within each parcel.<\/li>\n<\/ol>\n<\/li>\n
        3. Note:<\/strong> The Generate Spatial Join Attribute Rule Tool will automatically create new fields added to the field maps in the Input Table feature class.<\/li>\n
        4. In the Field Map parameter go ahead and select the Edit <\/strong> In the Fields list go and select all the fields and click the Remove <\/strong>button\u2026bam we have a clean slate!<\/li>\n
        5. Click on the dropdown arrow next Add Fields<\/strong> button and click Add Empty Field<\/strong>. Name the field NumberOfLots. Change the type to Long<\/strong>. For the Actions <\/strong>dropdown select Count<\/strong>. For the Source Fields<\/strong> choose OBJECTID<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

           <\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2718782,"id":2718782,"title":"GenerateSpatialJoin_FieldMap","filename":"GenerateSpatialJoin_FieldMap.png","filesize":42973,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-spatial-join\/generatespatialjoin_fieldmap","alt":"","author":"365172","description":"","caption":"","name":"generatespatialjoin_fieldmap","status":"inherit","uploaded_to":2642652,"date":"2025-03-05 23:13:11","modified":"2025-03-05 23:13:11","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":553,"height":345,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap.png","medium-width":418,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap.png","medium_large-width":553,"medium_large-height":345,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap.png","large-width":553,"large-height":345,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap.png","1536x1536-width":553,"1536x1536-height":345,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap.png","2048x2048-width":553,"2048x2048-height":345,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap.png","card_image-width":553,"card_image-height":345,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap.png","wide_image-width":553,"wide_image-height":345}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

          e. Now let\u2019s create a Field Map for average property values within each parcel. Click on the dropdown arrow next to the Add Fields<\/strong> button again and click Add Empty Field<\/strong>. Name the field AvgPropertyValue. Change the Type to Double<\/strong>. Under the Actions<\/strong> dropdown select Mean<\/strong>. For Source Fields<\/strong> choose PropertyValue<\/strong>.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2726622,"id":2726622,"title":"GenerateSpatialJoin_FieldMap_AvgPropertyValue","filename":"GenerateSpatialJoin_FieldMap_AvgPropertyValue.png","filesize":55664,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-spatial-join\/generatespatialjoin_fieldmap_avgpropertyvalue","alt":"","author":"365172","description":"","caption":"","name":"generatespatialjoin_fieldmap_avgpropertyvalue","status":"inherit","uploaded_to":2642652,"date":"2025-03-10 23:36:05","modified":"2025-03-10 23:36:05","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":998,"height":620,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue.png","medium-width":420,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue.png","medium_large-width":768,"medium_large-height":477,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue.png","large-width":998,"large-height":620,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue.png","1536x1536-width":998,"1536x1536-height":620,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue.png","2048x2048-width":998,"2048x2048-height":620,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue-749x465.png","card_image-width":749,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/03\/GenerateSpatialJoin_FieldMap_AvgPropertyValue.png","wide_image-width":998,"wide_image-height":620}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

            \n
          1. The optional Search Options <\/strong>parameter allows us to define the spatial queries from the Input Table and Join Classes parameter values. Every Join Class gets its own set of Search Options parameters.\n
              \n
            1. The Join Class<\/strong> is the name of the class that the spatial query will be run on.<\/li>\n
            2. The Input Geometry Type<\/strong> is the portion of the input geometry that will be used to query the join class. There are four geometry types:\n
                \n
              1. Geometry <\/strong>\u2013 the complete geometry of the input feature. This is default. For our example we will choose this geometry type.<\/li>\n
              2. Start<\/strong> \u2013 The first vertex within a polyline feature. (Note: this option is only available on join classes that are polylines).<\/li>\n
              3. End<\/strong> \u2013 The last vertex within a polyline feature. (Note: this option is only available on join classes that are polylines).<\/li>\n
              4. Centroid<\/strong> \u2013 The geometric center of the input feature.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
                  \n
                1. \n
                    \n
                  1. The Spatial Operator<\/strong> is the spatial operation that will be used in the query. There are several spatial operators available:\n
                      \n
                    1. Intersects <\/strong>\u2013 Features in the join class will be matched if they intersect with an input feature. This is default.<\/li>\n
                    2. Crosses <\/strong>\u2013 Features in the join class will be matched if they cross with an input feature.<\/li>\n
                    3. Contains<\/strong> \u2013 Features in the join class will be matched if an input feature contains the joined class features. This is the opposite of the Within option.\n