ArcGIS Solutions Blog

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Other Boards in This Place

Latest Activity

(6 Posts)
AndyShoemaker
Esri Contributor

Updates to Arcade in  ArcGIS Online causes some expressions shipped with solutions to fail. This article describes how to fix these issues after deployment. 

Read more...

more
1 0 92
AlexKabak
Esri Contributor

With the rapidly approaching October 16, 2024 deadline for all water utilities in the United States to complete an initial lead service line inventory, we have had many questions about how to upgrade a previous deployment of the Lead Service Line Inventory solution to version 3.0.  This blog explains the process.

UpgradeLSLI.png

Read more...

more
0 0 455
ChrisFox
Esri Regular Contributor

Changes in ArcGIS Pro 3.1 cause some attribute rules to fail. This article describes how to resolve these errors in your existing deployment.

Read more...

more
0 2 170
ChrisFox
Esri Regular Contributor

There may be cases where you want to deploy multiple versions of a solution. For example, a county who deploys our Election Results solution for each midterm and general election to visualize and share election results with the community. Each deployment of a solution places the solution and associated items into a new folder in your content. If you deploy Election Results three times you will have three copies of each item in 3 separate folders. Renaming the folder can help you uniquely identify each solution, however when you search your content for an item it can be challenging to know which item is associated with which deployment of the solution.

To assist with this we have created a new geoprocessing tool for ArcGIS Pro that can add a prefix or suffix to all the items and groups included with a solution deployment. So for example, if we deployed Election Results for the 2020 general election we could add the prefix '2020 General' to all the items included with that deployment. If we then deploy Election Results for the 2022 midterm we could add the prefix '2022 Midterm' to all items in this deployment. Now when we search for an item we can more easily distinguish between items associated with different deployments of the same solution.

Complete the following steps to add a prefix or suffix to all items deployed with an ArcGIS Solution:

  1. Download the Solution Helper Tools and unzip the zip file
  2. Open ArcGIS Pro and sign into your ArcGIS organization.
  3. From the Insert tab click Toolbox > Add Toolbox and add the SolutionHelperTools.atbx
  4. Expand Toolboxes in the Catalog pane and open the Rename Solution Content tool in the SolutionHelperTools toolbox.

    toolbox.png

  5. In the Deployed Solution Item parameter selection the solution associated with the items you want to add a prefix or suffix to. You can also copy/paste the item id from the browser into the parameter.
  6. Add either a prefix or suffix you want to add to the item name.

    tool.png

  7. Click Run.

    Content.png

more
3 1 539
JeremiahLindemann
Esri Contributor

CAMEOfm software updates allow data to be exported for easier use in ArcGIS Pro.

Read more...

more
2 0 785
ChrisFox
Esri Regular Contributor

The Address Data Management solution can be used by mapping technicians to maintain an inventory of road centerlines, valid road names, site addresses, and related mailing addresses.The solution includes an ArcGIS Pro project with a schema database and feature classes pre-configured with attribute rules to help automate and ensure the integrity of you addresses and centerlines while editing.

One capability that isn't included by default but can be configured in the solution is the ability to pull information from an intersecting feature when a new address is created or moved. For example, you might want to pull the name of the municipality, the zip code, or the property identification number (PIN) the address falls within and write it to a field within the site address point. This involves adding a new attribute rule to the Site Addresses feature class.

To add an attribute rule to your site addresses layer and pull information from an intersecting feature complete the steps below. It is important to note this rule requires both the addresses feature class and the feature class you want to pull the intersecting feature from be in the same database.

  1. In ArcGIS Pro from the Contents pane, right-click the Site Addresses layer.
  2. From the Design menu, select Attribute Rules.
  3. From the Attribute Rules view, click the drop-down next to Add Rule and select Add Immediate Calculation Rule.
  4. Provide a Name and Description for your rule.
  5. From the Field drop-down, select the field in your Site Addresses layer you want to write the attribute from the intersecting feature to.
  6. Click the Expression button to open the Expression Builder.
  7. Copy and paste the code below into the Expression Builder.
    // replace 'FeatureClassName' with the name of the feature class to pull intersecting features from (ex. Cities, ZipCodes, Parcels)
    var intersectingFeatures = Intersects(FeatureSetByName($datastore, "FeatureClassName"), $feature);
    for (var feature in intersectingFeatures) {
         // replace 'fieldname' with the name of the field from the intersecting feature to pull the value from
         var value = feature.fieldname;
    	 if (IsEmpty(value)) continue;
         return value;
    }
    return null;‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍
  8. In the code find and replace the text "FeatureClassName" with the name of the feature class to to pull intersecting features from (ex. Cities, ZipCodes, Parcels)
  9. In the code find and replace the text "fieldname" with the name of the field from the intersecting feature to pull the value from.
  10. Click the Verify button and click OK to close the Expression Builder.
  11. From Triggers, check Insert. If you would also like the rule to run when the address is moved as well, check Update.
  12. Click Save on the Attribute Rules tab on the ribbon. This button will be disabled if you have any pending feature edits, save or discard your edits to enable the Save button.

The rule should now be active, when you create a new site address point the rule should run and pull the attribute of the intersecting feature into the field specified by the rule. You could repeat the steps above to add additional rules for different feature classes and field values.

The code above is configured to return null if no intersecting features are found and if multiple intersecting features are found (overlapping polygons) it will return the first non null feature attribute found. Below are some additional code samples for some other common scenarios.

Return multiple intersecting feature values as comma delimited list

// replace 'FeatureClassName' with the name of the feature class to pull intersecting features from (ex. Cities, ZipCodes, Parcels)
var intersectingFeatures = Intersects(FeatureSetByName($datastore, "FeatureClassName"), $feature);
var values = [];
for (var feature in intersectingFeatures) {
	// replace 'fieldname' with the name of the field from the intersecting feature to pull the value from
	var value = feature.fieldname;
	if (IsEmpty(value)) continue;
	values [Count(values )] = value;
}
return Concatenate(values, ", ");
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Return multiple intersecting feature values as a statistic (Mean, Min, Max, Sum)

// replace 'FeatureClassName' with the name of the feature class to pull intersecting features from (ex. Cities, ZipCodes, Parcels)
var intersectingFeatures = Intersects(FeatureSetByName($datastore, "FeatureClassName"), $feature);
var values = [];
for (var feature in intersectingFeatures) {
	// replace 'fieldname' with the name of the field from the intersecting feature to pull the value from
	var value = feature.fieldname;
	if (IsEmpty(value)) continue;
	values[Count(values)] = value;
}
return Mean(values);‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

more
2 1 690
80 Subscribers