Latest Contributions by ThomasColson

I have Solved: Attribute Rule Expressions: calculate max value fr... - Esri Community successfully working in the fgdb environment. What I'm looking to do is replicate in a "new" web map viewer "Form" to autopopulate an unique ID field that IS NOT the objectID nor the GlobalID. Thing is, the data contains many existing records, with this ID ranging from 1-15000, with many values in between missing due to past deletions. What I want is to look at the max value in this field, and have (Arcade?) auto populate the next highest value when the user creates a new point, based on this form. But I don't see how this is possible as AGOL (still!) does not support GDB attribute rules and Create Database Sequence (Data Management)—ArcGIS Pro | Documentation ... View more

In an AGOL webmap, I have an Attribute Expression (that I sourced from here😞   // get the states layer var portal = Portal('https://arcgis.com') var states = FeatureSetByPortalItem( portal, 'a454cf97c4264cd2b77f27175e01d3ba', 3, ['ABBRV'] ) // intersect feature with States var xs = Intersects( $feature, states ) // create array of intersected state names var c_array = [] for (var c in xs){ Push(c_array, c['ABBRV']) } // remove duplicates var unique_states = Distinct(c_array) // concatenate array, return string return Concatenate(unique_states, ', ') That works as expected: user clicks on a line, pop-up returns a list of state(s) that the selected line intersects.  Here's the problem: the line is multiple parts (features? Sections?). CHunked up by numerous attributes (state, county, district, etc....). So if the user clicks on a line segment, they get the state(s) that the segment intersects.  But what I want is:  Every single state the ENTIRE line intersects, based on the name of the line. So if the NAME attribute of the line they click on is "BIGFOOT", some sort of magical arcade thing that FIRST selects every single line segment (which could be dozens) with NAME = "BIGFOOT", then do the intersect and return every state intersected by every line segment where NAME = "BIGFOOT". ... View more

With the following I am evaluating:  Does the field exist and correct length. Print message Does the field exist and incorrect length. Print message Does the field not exist. Create field. Print Message #Create required TRLNAME Field try: in_Field = "TRLNAME" if len(arcpy.ListFields(in_Table,in_Field))>0 and len(in_Field) == 254: arcpy.AddWarning(in_Field+" exists and is the correct length. Yay!") elif len(arcpy.ListFields(in_Table,in_Field))>0 and len(in_Field) != 254: arcpy.AddWarning(in_Field+" exists but is not the correct string length (254).") else: arcpy.AddField_management(in_Table, in_Field, "TEXT", "", "", 254, in_Field, "NON_NULLABLE", "REQUIRED", "") arcpy.AddMessage ("Created the "+in_Field+" field.") except arcpy.ExecuteError: msgs = arcpy.GetMessages(2) arcpy.AddError(msgs) except: tb = sys.exc_info()[2] tbinfo = traceback.format_tb(tb)[0] pymsg = "PYTHON ERRORS:\nTraceback info:\n" + tbinfo + "\nError Info:\n" + str(sys.exc_info()[1]) msgs = "ArcPy ERRORS:\n" + arcpy.GetMessages(2) + "\n" arcpy.AddError(pymsg) arcpy.AddError(msgs)  If the field does not exist, it correctly creates it. However, if the field exists, regardless of if it's the correct length (254 or any other string length), it always defaults to the "elif" in the block and reports that the field is not the correct length.  Feel like this is a simple syntax error but I've been at it for hours and not seeing it. Help? ... View more