Latest Contributions by Joseph_Kinyon

Thank you. That is what I expect. Because the template also pulls current time and date as well as calculates pagination I was hoping for a similar element to display other system level information like user name or path to report. ... View more

@IsmaelChivite Is it possible to set the appearance of a number field to bearing using the web designer? I have added this using the Survey123 Connect XLS form, but would like to port this over for editing using the web designer as a workflow to make it easier to transfer management of the form to another member in the organization. I don't believe it is, but have been going by the early adopter conversations using Connect. Joe ... View more

This is great stuff, thanks for sharing.  Another thanks to Roger Dunn and Joshua Bixby While it isn't the prettiest or even complete, I shoe horned it into a script tool in model builder to make use of the Iterate Multivalue tool in ArcGIS 3 The script is called Definition Query Update in the model image. I thought I'd add back how it worked for my needs. """ Script documentation - Tool parameters are accessed using arcpy.GetParameter() or arcpy.GetParameterAsText() - Update derived parameter values using arcpy.SetParameter() or arcpy.SetParameterAsText() """ import arcpy def script_tool(param0, param1, param3): """Script code goes below""" return #get the input paramaters passed from the model output and variables param0 = arcpy.GetParameterAsText(0) param1 = arcpy.GetParameterAsText(1) param3 = arcpy.GetParameterAsText(3) aprx = arcpy.mp.ArcGISProject('current') m = aprx.listMaps()[0] l = m.listLayers()[0] #limit changes to the list of layers selected, in this version layers cannot be in a layer group to work for l in m.listLayers(param0): if l.supports('DefinitionQuery'): #Get the list of definition queries dql = l.listDefinitionQueries() #Clear active definition queries otherwise the update will fail if there is already an active query for dq in dql: dq['isActive'] = False #Create a new definition query and append it to the list dql.append({'name': param3, 'sql' : param1, 'isActive': True}) #Update the definition queries with the newly modified list l.updateDefinitionQueries(dql) arcpy.SetParameterAsText(2, param1) arcpy.AddMessage(param0) arcpy.AddMessage(param1) arcpy.AddMessage(param3) #consider inserting a file picker variable that allows you to select an existing definition query .exp file for the sql input   ... View more

Mike, Would love to see the whole script tool you created if you have a moment. What you have created is very close to my tool. Select Layers>choose or write query definition (or set to clear)>check if definition query exists > update definition query ... View more

Bill, We have not, but I am curious. The obscured or ambiguous pricing information, the problematic drivers of the past getting little improvement (therefore losing trust in users), general hiccups in the ink scams of HP, random paper unloads has made us understandably wary to try. I have recently downloaded and will give it a whirl. Wondering now after a year ,what your experience has been? (a bit of desert island of a comment thread as I wash ashore.) Joe ... View more

All, I encountered this same problem in ModelBuilder in ArcGIS Pro 3.0 today ten years later and FYI the workaround still appears to do the job.   Joe ... View more

Came here to address this rumor exactly and appreciate the clear response. I told them I believed they were confusing it with Collector which was deprecated and that Field Maps is the succesor tool. ... View more

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

Thanks for confirming this. We were using integer and tried a couple tools including this to create a stop point in the middle of the model. We noodled with it this morning and our model was using it to create a dissolved shapefile of selected parcels in a zipped file that is to be submitted (via upload) as an area of interest to online reporting tools created by other agencies. Many of those have a minimum threshold (varies) of acres for the report to run. When the user selects the parcels of interest they are copied into memory, dissolved, and then the combined area is calculated. If larger than user defined minimum acres, then the tool proceeds. If less, then that is used as a precondition and the model stops. The "If Value Is" tool worked for us when we finally used it in conjunction with the "Get Field Value" on the final dissolved feature create in the prior step. Using that that previously calculated value to compare to the user defined minimum was the true false expression condition we wanted. Connecting directly to that caused the odd behavior while inserting the Get Field Value too removed the hangups. It has worked like a charm stopping/continuing the model this way. I now need to add a meaningful message to the user when it completes the model or not. ... View more

Curtis, Have you had success with this since you sought help here? We have had similar challenges with our model recently and troubleshooting it has been difficult and cannot discern if It is behaving as designed and our logic is circular or if it is giving unexpected results for other reasons. It stumped my tech support for similar reason and they are testing it. ... 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