Latest Contributions by DavidSolari

Our team has received requests from multiple clients for this functionality, would love to see it in an upcoming release. ... View more

Our team was able to work around this after switching from standalone servers to Enterprise but our client has now tripled the amount of requests they make as they can't cache tokens between multiple requests. I think a reasonable compromise would be to keep the 2 week limit for Portal tokens, but allow the server tokens used for direct service access to have longer expiration times. This maintains some backwards compatibility with older server setups while keeping the current level of security intact for the newer Portal workflows. ... View more

Also, forgot to mention this, but the way you use the tool is to write a Python function that takes in 1 or more fields for each record and returns a boolean value to determine if it's selected or not. For example, if you have a text field called "CustomerName" and you want to select every record whose customer has a first name over 10 characters, your python function would be "return len(customername.split()[0] if customername else 0) > 10". ... View more

Felt like solving a challenge so here's a working tool. I can't attach the full tool so here's the components: Parameters: Execution: import arcpy import ast def parseSelectionType(s): return s.strip().upper().replace(" ", "_") def checkFunc(funcText): try: ast.parse(funcText) return True, None except SyntaxError as e: return False, "Invalid syntax in Python function, line {}".format(e.lineno - 1) def buildFuncText(funcBody, fieldNames): FUNC_NAME = "_select_func" signature = "def {}(".format(FUNC_NAME) if len(fieldNames): signature += ", ".join(f.lower() for f in fieldNames) signature += "):\n\t" indentFuncBody = funcBody.replace("\r\n", "\n").replace("\n","\n\t") return signature + indentFuncBody, FUNC_NAME def main(layer, fieldNames, funcBody, selectionType="NEW_SELECTION", isInvertSelection=False): selectFuncText, selectFuncName = buildFuncText(funcBody, fieldNames) isValid, error = checkFunc(selectFuncText) if not isValid: arcpy.AddError(error) raise SystemExit(1) namespace = {} exec(selectFuncText, namespace) selectFunc = namespace[selectFuncName] desc = arcpy.da.Describe(layer) oidFieldName = desc["OIDFieldName"] isOIDInFunc = True if oidFieldName not in fieldNames: fieldNames = ["OID@"] + fieldNames isOIDInFunc = False shapeFieldName = desc["shapeFieldName"] if shapeFieldName in fieldNames: fieldNames = [f if f != shapeFieldName else "SHAPE@" for f in fieldNames] selectOIDs = [] with arcpy.da.SearchCursor(layer, fieldNames) as search: for row in search: oid = row[0] params = row if isOIDInFunc else row[1:] if selectFunc(*params): selectOIDs.append(oid) sql = "{} IN ({})".format(oidFieldName, ",".join(str(o) for o in selectOIDs)) arcpy.management.SelectLayerByAttribute(layer, selectionType, sql, isInvertSelection) if __name__ == "__main__": layer = arcpy.GetParameterAsText(0) selectionType = parseSelectionType(arcpy.GetParameterAsText(1)) if arcpy.GetParameterAsText(1) else "NEW_SELECTION" fields = [f.value for f in arcpy.GetParameter(2)] funcBody = "\n".join(s for s in arcpy.GetParameter(3)) isInvertSelection = arcpy.GetParameter(4) main(layer, fields, funcBody, selectionType="NEW_SELECTION", isInvertSelection=False)    Validation: import ast def checkFunc(funcText): try: ast.parse(funcText) return True, None except SyntaxError as e: return False, "Invalid syntax in Python function, line {}".format(e.lineno - 1) def buildFuncText(funcBody, fieldNames): FUNC_NAME = "_select_func" signature = "def {}(".format(FUNC_NAME) if len(fieldNames): signature += ", ".join(f.lower() for f in fieldNames) signature += "):\n\t" indentFuncBody = funcBody.replace("\r\n", "\n").replace("\n","\n\t") return signature + indentFuncBody, FUNC_NAME class ToolValidator: # Class to add custom behavior and properties to the tool and tool parameters. def __init__(self): # set self.params for use in other function self.params = arcpy.GetParameterInfo() def initializeParameters(self): # Customize parameter properties. # This gets called when the tool is opened. return def updateParameters(self): # Modify parameter values and properties. # This gets called each time a parameter is modified, before # standard validation. return def updateMessages(self): # Customize messages for the parameters. # This gets called after standard validation. fields = self.params[2] funcBody = self.params[3] if fields.value and funcBody.value: fieldNames = [f.value for f in fields.values] funcBodyText = "\n".join(funcBody.values) funcText = buildFuncText(funcBodyText, fieldNames)[0] isValid, error = checkFunc(funcText) if not isValid: funcBody.setErrorMessage(error) return # def isLicensed(self): # # set tool isLicensed. # return True   The Python Function Body parameter is a bit of a hack, it uses multiple string params in lieu of a proper text box (ESRI pls). I also didn't implement parameter parsing like the Calculate Field tool does so your function parameters are just the field names in lower case (e.g. the field "ParcelID" is accessed as "parcelid"). It'll also convert the shape field to python geometry objects just like the "SHAPE@" cursor token so you can do shape.firstPoint.X and such. There's probably some bugs lurking in here and using eval to run arbitrary input can cause issues but overall this'll get you what you need. ... View more

Hi Shana, My team finally has Pro 2.5.1 and I can confidently say that this issue hasn't been fixed. All geocodes were performed using the World Geocoding Service. ... View more

Same behavior from my end in 2.4.0 and 2.4.2 (not sure about 2.5 and up). Once you start rematching a layer that layer is stuck in a sort of rematch state, which constantly adds address candidates to the map view and automatically zooms in on the first record of a new selection. Closing the rematch pane doesn't fix this, only removing then adding the layer again, and even then the candidate icons (A, B, C etc.) are stuck on my end. Hopefully if this isn't fixed in 2.5 it's addressed soon. ... View more

I have to deal with PDFs generated from CAD drawings regularly, being able to quickly georeference those PDFs (most of them already have some georeference info in them) and display them as a reference layer under the GIS data would be a fantastic feature for Pro. ... View more

This would be a massive boon to our field crews, they're frequently taking photos of confined areas or cramped service boxes and the only way they can note which photo is which part of the feature is to use the feature's comments field. Attachment renaming (and other types of metadata editing) in Collector would be the perfect solution. ... View more