Latest Contributions by BRENNEJM

I have arcade set up in a smart form to auto-generate the next unique ID when a new feature is created. When updating an existing feature, the script should use the existing unique ID. This works great in Field Maps and when the arcade script is tested. However, when editing through Experience Builder, the arcade script always generates the next unique ID and replaces the existing unique ID. Arcade Script: Arcade Test (the next unique ID based on my features would be PSPT-00089. PSPT-00071 already exists, and the arcade script is working correctly) Map Viewer pop-up (this point shows that unique ID is already set to PSPT-00049) Experience Builder edit pop-up after selecting the same point as above (PSPT-00049 shows up briefly and then is overwritten with PSPT-00089) ... View more

I have three FeatureSets: a grid (red lines below), planned treatments (based on the grid, green areas below), and completed treatments (not based on the grid, black lines below). I need to determine total acreage for three categories: Planned but not completed (6 of the grid cells below), Planned and completed (6 of the grid cells below), and Completed but not planned (3 of the grid cells below). This would be really easy using Intersects() to create a new FeatureSet() for all grid cells that intersect with completed treatments, but I only want to count a cell as completed if it overlaps with a completed treatment by 25%. I know I can use Intersects() to get all grid cells with completed treatments and then use Intersections() to check the overlap percentage, but is there a faster more optimized way of doing this? This method works okay for the example pictured below (not many grid cells), but my actual dataset has 116,000 grid cells and many planned/completed treatments. The above method times out at around 36 minutes in. I've streamlined the process by performing a Union() on all of the planned treatments and another Union() for all of the completed treatments, but it still takes too long for staff to use. Does anyone know of a faster way to go about this? My current thought is to use the ArcGIS API for Python and host it on PythonAnywhere. I'm still learning Arcade and would love to know if there's an optimized solution that would keep this live in a Dashboard. ... View more

Just posting this in case others have the same issue. Issue: When trying to "Predict to Raster" using the Forest-based and Boosted Classification And Regression tool, as soon as the message for "Cell Size" is printed, the tool ends as "Completed" without creating the model or predicting to a raster. Settings: Model Type = Forest-based Input Training Features = Polygon Treat Variable as Categorical= Checked Only using explanatory training rasters Convert Polygons to Raster Resolution for Training = checked Polygon and rasters are all in the same projection Match Explanatory Rasters are all matched correctly Comments: Everything works as intended if "Train Only" is selected. After switching to "Predict to Raster" the tool fails as mentioned above. If I uncheck "Convert Polygons to Raster Resolution for Training", the tool will predict to raster as expected. While using "Train Only", I can convert my training polygons to points using the "Output Trained Features" setting. If I use these points as the "Input Training Features", the tool will predict to raster without any issues (however, it should be noted that for some reason out-of-bag errors are worse when using these points vs the original polygons, which seems odd if the "Convert Polygons to Raster Resolution for Training" setting works as described). Tool Settings Tool Messages Note: I get the above warnings even when the tool runs successfully. ... View more

In Experience Builder, when I use the Edit widget to create a new feature I must also fill in misc attributes about that feature. When I open dropdown menus, the dropdown opens above the field, and this pushes the top options out of the viewable window. In the below image, you can see that the top months (January and February) are obscured, and both of the scroll bars are at the top most point. I can get around this by starting to type in the obscured month or by expanding the Edit window until the vertical scroll bar disappears. This makes the dropdown open beneath the field, but these options aren't the preferred solutions to this bug.  ... View more

I have the arcade pop-up expression written (see below). The pop-up displays correctly in ArcGIS Online and in Field Maps. However, Collector returns a dash ("-"). I've reviewed a number of tutorials and Esri Community posts, but none seem to apply here.  Expression 1   //Access 'Hydrant Inspections' table as a FeaureSet var inspections = (FeatureSetByName($datastore,"Inspections")) //Filter related features by using a common attribute var UID = $feature.UID var filterStatement = 'UID = @UID' //Related features as a variable var relatedData = Filter(inspections, filterStatement) //Sort related features from oldest to newest var relatedDataSorted = OrderBy(relatedData, 'InspectionDate ASC') //Build the pop-up string by iterating through all related features var popupString = '' for (var f in relatedDataSorted){ popupString += Text(f.InspectionDate, 'MMMM D, Y') + TextFormatting.NewLine + 'Box Condition: ' + f.Condition + TextFormatting.NewLine + 'Notes: ' + f.Notes + TextFormatting.NewLine + TextFormatting.NewLine } return popupString     I've also tried simpler expressions and get the same result. The bellow expression works in AGO and Field Maps, but not in Collector. Expression 2   //Related features as a variable var relatedData = FeatureSetByName($map,"Inspections") var popupString = '' //Add all inspection dates to a pop-up string for (var row in relatedData){ if ($feature.UID == row.UID) { popupString += Text(row.InspectionDate, 'MMMM D, Y') } } return popupString   EDIT Some additional info. The above was all edited in the new Map Viewer. I tried authoring a new map in Map Viewer Classic and copied both of the above expressions. Expression 1 works in AGO and Field Maps, but not in Collector. However, Expression 2 only works in Field Maps. AGO returns a blank (" ") and Collector returns a dash ("-").   ... View more