Latest Contributions by JohannesLindner

So, as you discovered, if a point is within a polygon, NEAR_DIST will be zero. JohannesLindner_0-1674024491020.png     There's no way to switch to centroid in the Near tool. You have to do an extra step:   Use Feature To Point (Data Management)—ArcGIS Pro | Documentation to get the centroids of the polygons. Then run the Near tool with these centroids. JohannesLindner_1-1674024759061.png     While this results in NEAR_DIST > 0, it loses the relationship to the polygons, because NEAR_FID uses the ObjectID of the centroids and you can't switch that to ORIG_FID (the ObjectID of the polygons). If you need the OBJECTIDs of the polygons, you have to use Join Field (Data Management)—ArcGIS Pro | Documentation, joining Centroids.ORIG_FID to the station fc with the relation Centroids.OBJECTID = stations.NEAR_FID JohannesLindner_2-1674025077298.png   ... View more

Set messaging to None. The deletion happens because it is a composite relationship, regardless of messaging. The messaging takes care of updating geometry (automatic in a composite relationship) and attributes (has to be programmed). To read deeper into relationship class properties: Relationship class properties—ArcGIS Pro | Documentation ... View more

There are no Python Addins in ArcGIS Pro, and there are no plans to add them: Python Add-Ins for ArcGIS Pro - Page 8 - Esri Community Instead, Addins have to be built with the ArcGIS Pro SDK for .Net. Build your first add-in | Documentation | ArcGIS Developers With some luck, you can port the majority of your addin functionality into a Python toolbox. With that, you would have to same GUI as the normal ArcGIS geoprocessing tools. You may want to look into What is a Python toolbox?—ArcGIS Pro | Documentation . If you decide to go down that route, It's important to note that ArcMap uses Python 2.7, but ArcGIS Pro uses Python 3.X. There are some changes in the syntax, you can read more here: Python migration from 10.x to ArcGIS Pro—ArcGIS Pro | Documentation ... View more

Yes, you're passing values. BUT: Your values are objects with attributes and methods. In your operate function, you're using these methods to change the internal attributes of your values.   Here's what's happening: static void operate (StringBuffer x, StringBuffer y) { // x and y are passed by value. but they have internal values themselves. // here, you're changing x's internal value. You're not changing x itself, only its internal value! x.append(y); // here, you're creating a new variable in the local scope of this function. // this does not change the variable you passed into this function, because // it is outside of this function's scope. // IF you would be passing by reference (which you are not!), this would // change the outer y y = x; } public static void main (String [] args) { StringBuffer a = new StringBuffer ("A"); // a = "A" StringBuffer b = new StringBuffer ("B"); // b = "B" operate (a,b); // a = "AB", because you changed a's internal value // b = "B", because you didn't change its internal value // y_inside_the_function = "AB", but y only exists inside the function's scope System.out.println(a + "," +b); // "AB,B" }   There are some good explanations in this StackOverflow post: methods - Is Java "pass-by-reference" or "pass-by-value"? - Stack Overflow ... View more

You're not calling the function in your main You get an infinite recursive loop, because you keep calling the function even if position < 0 import java.io.*; public class Recursion { public static void main(String[] args) throws IOException{ int myArray[] = {1,2,3,4,5,6,7,8,9,10}; reverseDisplay(myArray, 9); } public static void reverseDisplay(int[] ary, int position){ if(position > 0) { System.out.print(ary[position]); reverseDisplay(ary, position - 1); } } }   ... View more

As Dan said, there's no out of the box tool. If you need that functionality in Model Builder, you have to create that tool yourself. Below are two quick examples. You can save that script as a Python toolbox (.pyt), load that into ArcGIS Pro, and then drag the tools in to your model. # -*- coding: cp1252 -*- import arcpy class Toolbox(object): def __init__(self): self.label = "Utility" self.alias = "utility" self.tools = [InsertRow, InsertRowIntoTableA] class InsertRow(object): label="Insert Row" description="Inserts a row into a table" def getParameterInfo(self): parameters = [ arcpy.Parameter(name="in_table", displayName="Table", datatype="DETable", parameterType="Required", direction="Input"), arcpy.Parameter(name="row", displayName="Row", datatype="GPValueTable", parameterType="Required", direction="Input"), arcpy.Parameter(name="out_table", displayName="Edited Table", datatype="DETable", parameterType="Derived", direction="Output"), ] parameters[1].columns = [ ["GPString", "Field"], ["GPString", "Value"] ] return parameters def updateParameters(self, parameters): par = {p.name: p for p in parameters} in_table = str(par["in_table"].value) # reset fields if no table is selected if in_table == "None": par["row"].value = None return # get fields from the table target_fields = [ f.name for f in arcpy.ListFields(in_table) if f.type not in ("OID", "GlobalID", "Geometry") ] # get currently loaded fields current_fields = [] if par["row"].value is not None: current_fields = [ f for f, v in par["row"].value ] # if these don't match, a different table was selected -> change fields if current_fields != target_fields: par["row"].value = [[f, None] for f in target_fields] def execute(self, parameters, messages): par = {p.name: p for p in parameters} # get fields with user input row = [ [field, value] for field, value in par["row"].value if value not in ('', None) ] fields, values = list(zip(*row)) # insert the new row # all values are str, but the InsertCursor should take care of the conversion with arcpy.da.InsertCursor(str(par["in_table"].value), fields) as cursor: cursor.insertRow(values) # set the output parameter par["out_table"].value = par["in_table"].value class InsertRowIntoTableA(object): label="Insert Row into TableA" description="Inserts a row into TableA" def getParameterInfo(self): parameters = [ arcpy.Parameter(name="in_table", displayName="TableA", datatype="DETable", parameterType="Required", direction="Input"), arcpy.Parameter(name="ID_A", displayName="ID_A", datatype="GPLong", parameterType="Required", direction="Input"), arcpy.Parameter(name="TEXT_A", displayName="TEXT_A", datatype="GPString", parameterType="Required", direction="Input"), arcpy.Parameter(name="out_table", displayName="Edited TableA", datatype="DETable", parameterType="Derived", direction="Output"), ] return parameters def execute(self, parameters, messages): par = {p.name: p for p in parameters} # get the values fields = ["ID_A", "TEXT_A"] values = [ par[f].value for f in fields ] # insert the new row with arcpy.da.InsertCursor(str(par["in_table"].value), fields) as cursor: cursor.insertRow(values) # set the output parameter par["out_table"].value = par["in_table"].value   JohannesLindner_0-1673948708318.png   JohannesLindner_1-1673948730329.png   JohannesLindner_2-1673948815911.png     ... View more

Create a database sequence: Create Database Sequence (Data Management)—ArcGIS Pro | Documentation Use this expression in the attribute rule: // Calculation Attribute Rule for the ID field // triggers: Insert, Update // Exclude from application evaluation // If there is already a value in the ID field, return that if(!IsEmpty($feature.AssetNumber)) { return $feature.AssetNumber } // get all the parts for the unique id, format them correctly var parts = [ $feature.RoadType, Text($feature.Location, "00"), Text($feature.Sublocation, "00"), "-", Text(NextSequenceValue("NameOfTheSequence"), "0000") ] // concatenate and return return Concatenate(parts, "") ... View more

There's a difference between a feature class and a layer. Very basically: the feature class is the actual data, the physical object being saved on your disc the feature layer is a representation of that data. Things like coordinate transformation, symbology, labeling, popups are done on the layer, not on the data. If you symbolize your layer, the underlying feature class doesn't know anything about that. Importantly, one other thing that only works on the layer, not on the feature class, is selection. You start out doing the right thing: Create a layer (klasse1_f1) of the data and do the selection on that layer. But then you copy the feature class (klasse1). The feature class has no selection, because you selected on your layer and there is no feedback to the feature class.   So this should work as intended: arcpy.management.CopyFeatures(klasse1_f1, "siedlung")     As a side note: you don't actually need to do the selection. You could just use your queries in the MakeFeatureLayer tool. This sets the definition query of the resulting layer. So you could do this: #Klassierung der Klasse1 (Siedlung) klasse1_siedlung = arcpy.management.MakeFeatureLayer(klasse1, "klasse1_siedlung", "'CLC15' = '111'") arcpy.management.CopyFeatures(klasse1_siedlung , "siedlung") #Klassierung der Klasse1 (Industrie) klasse1_industrie = arcpy.management.MakeFeatureLayer(klasse1, "klasse1_industrie ", "'CLC15' = '121' OR 'CLC15' = '131' OR 'CLC15' = '132' OR 'CLC15' = '133'") # you could also write this as # CLC15 IN ('121', '131', '132', '133') arcpy.management.CopyFeatures(klasse1_industrie , "industrie") ... View more