Latest Contributions by JosephKinyon1

Thank you for ideas for the work around. The feature class used to mask is a polygon. (...can a feature class be a raster data type? I don't think it works like that for ESRI data types and tools) As a matter of habit I set the analysis extent  (processing extent in the environments setting) and the mask to the same feature class, unless there is a compelling reason to have the analysis include the whole raster extent. The data being used in the slope tool is a raster in a File Geodatabase (DEM) and the tools returns a raster (DEM) as expected for the slope calculation--the problem is that it is the wrong mask. Clipping the raster data set  does work, but this requires that I export the selected features I want to use to a new data set to perform the clip, then perform the clip, then run the slope analysis on the clipped data set.  I tested this workflow to confirm it works before concluding the mask option is doing odd things and before posting my question/observation. To get the task done and off my plate I used that workaround and settings to complete the slope calculation. The task was to calculate the slope limited to my area of interest (a few ranches) so I could then estimate locations to exclude from grazing due to erosion criteria related to steep slope. However, while this workflow is possible (thank you for confirming) this process leaves me with the two interstitial data sets I was trying to avoid creating (plus manage and now need to delete) that the mask setting should have skipped. I'll clarify my settings: Selected parcel boundaries from a polygon feature class in a file geodatabase. Turned selected features into a separate layer (did not export as a new feature class) under the selection options under the context menu after right clicking the feature class with selected features in the contents pane. Added DEM raster from file geodatabase. Confirmed vertical units of measurement for raster and horizontal units of map and analysis environment were the same for correct calculation of slope. Opened slope tool. Set DEM for input. Set projection for environment settings. Set selected polygons added as layer  in map contents as mask (no features in that layer were selected) Also set selected polygons layer as analysis extent/processing extent under the environments settings Ran slope analysis. Slope tool calculated slope. Slope tool did not calculate whole raster, it did a mask. However, from the results it is clear that the mask used all the parcel polygons in the underlying feature class, not the set of three polygons in the layer chosen as input. Because the mask was not limited to the features in the layer that was chosen as the mask input I believe this is not the expected behaviour. While the work around as a one-off solution is good, creating extra steps in a model that require the creation, deletion, and confirmation of deletion of multiple sets of additional data in the process means I can't make use of the speed and efficiency of the mask- especially in an iterative model. I suspect this is a bug. Or... if it is true that layers created from selections cannot be used as a mask input then this should be noted in the slope tool documentation. A previous and troublesome bug of selections in ArcGIS Pro was that when selected features were turned into layers  the layer was damaged if you renamed it. The layer was was  a product of the "turn this selection into a layer" tool in the context menu for the feature class with selected features. When you renamed the new layer created from the selected subset of features (e.g. to use in the legend) the selection disappears and the layer reverts to displaying all the features of it's source (similar to deleting a definition query) I suspect that if this is a bug I am encountering in the slope tool, it is related to that prior bug that caused those problems with renamed layers. I'll try to have an ESRI technical support staff reproduce to see if it is an existing bug documented in the production management database after the winter holidays unless anyone else has already confirmed this problem with the mask. ... View more

Brad, I was able to update with release 2.6.1 on Tuesday September 1st and it now works correctly for me. Joe ... View more

Thanks Brad! That is exactly the problem we've been troubleshooting on a script that had worked fine before. If you're calculating acres of burned areas for recent fire maps recently, double check your results from scripts and models since upgrade. ... View more

I would like to pile on this good idea. Having visual examples to complement written instructions is rather handy. Implement HTML or other pop-up quality code. We can insert links to images and videos, which is great Adding images inline seems like a logical evolution of the Task Designer's abilities. Holding a user's had through a task to reinforce decisions with clear examples in the Task Pane would be a welcome imrovement to this feature. ... View more

Also looking at how this proposed feature extends this program linked below in a really important way: Conservation Easement Monitoring | ArcGIS Solutions for State Government  Staff went with Avenza Pro in the interim because they can't include track in visit in Survey123 as easily as they would like. ... View more

Thanks James, I was testing that last year and put it down, I have tracker on device and will look at workflow again. ... View more

Yaw Anokawa did a great job implementing it in ODK in 2018. Here's that parallel feature request in different XLSForms type tool Collect: Extend audit log to include GPS coordinates - Features - ODK Forum  By the way, is this a new idea or simply an extension of the Geotrace functionality? ... View more