Latest Contributions by JohannesLindner

OK. For the start point: // Calculation Attribute Rule on the line fc // field: upstreammanhole // triggers: insert(, update) // load the manholes var manholes = FeaturesetByName($datastore, "Database.DataOwner.Manholes", ["uniqueID"], false) // get the line's start point var p = Geometry($feature).paths[0][0] // find the intersecting manhole var manhole = First(Intersects(p, manholes)) // return a default value if no manhole intersects, else return the manhole's uniqueID return IIf(manhole == null, null, manhole.uniqueID)     For the end point, copy the rule and replace line 9: var p = Geometry($feature).paths[-1][-1]     You can also do both points in one rule. To do that, leave the field parameter of the Attribute RUle empty. // Calculation Attribute Rule on the line fc // field: empty! // triggers: insert(, update) // load the manholes var manholes = FeaturesetByName($datastore, "Database.DataOwner.Manholes", ["uniqueID"], false) // get the line's start and end points var start = Geometry($feature).paths[0][0] var end = Geometry($feature).paths[-1][-1] // find the intersecting manholes var start_manhole = First(Intersects(start, manholes)) var end_manhole = First(Intersects(end, manholes)) // instead of returning a value, return a dictionary return { result: { attributes: { upstreammanhole: IIf(start_manhole == null, null, start_manhole.uniqueID), downstreammanhole: IIf(end_manhole == null, null, end_manhole.uniqueID), } } } ... View more

Do you have empty id values? In that case, your query would be "ID = ", which is an invalid query. var id = $feature.ID if(id == null) { return false } // feature is invalid if no id var tbl = FeaturesetbyName($datastore, "IDs", ["ID"], false); var query = "ID = @ID"; // try using this notation instead var countID = Count(Filter(tbl, query)); return countID == 1 // valid if exactly 1 feature has this ID, else invalid ... View more

It doesn't work because you're not comparing to a date. Instead you compare a date (a very large number - milliseconds since January 1, 1970 UTC) to a very small number (1/4/2024 = 0.00012). Instead, you have to compare to actual dates: // month is 0 based -> January = 0, April = 3 var financialYear = When( dates >= Date(2023, 3, 1) && dates < Date(2024, 3, 1), "2023/2024", // ... "None")   This is very cumbersome. A better way: var dates = $feature.TargetExchange var y = Year(dates) var m = Month(dates) return IIf( m >= 3, // if after April `${y}/${y+1}`, // use "current/next" `${y-1}/${y}`) // else use "previous/current" ... View more

The Community's email address is handled separately from you AGOL account. Not the most intuitive decision, and there probably should be a note in the Community settings... You have to contact the Community team at [email protected] , they'll change it for you. ... View more

A basic approach: # This will try to rename your feature classes, be sure that you really want that! arcpy.env.workspace = "C:/your_database.sde" # database connection of the data owner (dbo in your example) for fc in arcpy.ListFeatureClasses() + arcpy.ListTables(): name = fc.split(".")[-1] new_name = "County_" + name try: arcpy.management.Rename(fc, new_name) except Exception as e: print(f"Could not rename {fc} to {new_name}: {e}")   To filter what classes and tables you rename: ListFeatureClasses—ArcGIS Pro | Documentation ListTables—ArcGIS Pro | Documentation ... View more

Field—ArcGIS Pro | Dokumentation Although the Field object's type property values are not an exact match for the keywords used by the Add Field tool's field_type parameter, all of the Field object's type values can be used as input to this parameter. The different field types are mapped as follows: Integer to LONG, String to TEXT, and SmallInteger to SHORT.     if field.name == x and field.type == "String"       ... View more

There are two main ways to add attachments to a feature: Using the Attribute Pane in ArcGIS Pro to manually add attachments to single features: Add or remove file attachments—ArcGIS Pro | Documentation Using the tool Add Attachments to add attachments to multiple features: Add Attachments (Data Management)—ArcGIS Pro | Documentation   To use the Add Attachments tool, you need an Attachment Match Table, which you can generate in a previous step with Generate Attachment Match Table (Data Management)—ArcGIS Pro | Documentation The Match Table is not the Attachment table. The Match Table is not associated with the feature class. The behavior you see is completely correct. The Match Table is just an intermediate step, it can be deleted after you used it in the Add Attachments tool.   Let's look at an easy example for how to add multiple attachments to a feature class. Let's say you have a polygon feature class of lots. This feature class has a text field called LotID with values like "LotA", "LotB", etc. Now you want to add some reports to these lots. Enable attachments for the feature class. Enable Attachments (Data Management)—ArcGIS Pro | Documentation Put the reports you want to attach into a folder, name them according to the LotID values -> "LotA.pdf" Generate the Match Table Generate Attachment Match Table (Data Management)—ArcGIS Pro | Documentation use LotID as key field, output match table can be anywhere (but not the attachment table!) The Match Table should look like this: LotID Path LotA C:/reports/LotA.pdf LotB C:/reports/LotB.pdf Add the attachments to the feature class Add Attachments (Data Management)—ArcGIS Pro | Documentation Use the table you generated in the previous step as match table, use LotID as join field The Match Table is unneccessary now, you can delete it.   For more on how to work with attachments, take a look at the docs: An overview of the Attachments toolset—ArcGIS Pro | Documentation ... View more

I am would like to merge 2 or more point layers within a feature class to 1 layer.  You say that you want to do this with the interactive Merge tool in the Edit tab, so I'm assuming you mean point features, not layers. A feature is one row in your feature class. A layer is the representation of your feature class in ArcGIS Pro (used for symbology, labels, selections, etc.). Sorry if that sounds nitpicky, but that's why the others assume you want to merge feature classes.   Anyway, Dan's answer is really close: You can't merge Points, only Multipoints. So you have to convert your point feature class into a multipoint feature class first: Use the Pairwise Dissolve tool to turn your point feature class into a new multipoint feature class. Toolboxes -> Analysis -> Pairwise Overlay -> Pairwise dissolve choose all fields as Dissolve fields make sure the "Create multipart features" checkbox is marked Select all features in the new feature class and run the interactive Explode tool in the edit tab   This new feature class is a multipoint featureclass, you can merge your point features here. ... View more