Latest Contributions by TorbjørnDalløkken2

Hi. I have created a toolbox (.atbx) which contains several pythonscripts, which I'm using in a project template. The projects created from the project template has been working fine, and all the tools runs ok. But this week I did some refactoring in a script and created a new project template. The script is tested and runs ok. But it doesn't work in projects based on the new project template. In my script I have this code  def beregnKortesteVeg(self, punktid, startpunktid, tilknytningspunkter, traceLayer): fl_tilknytningslinje = r"memory/Tilknytningslinje" fl_points = "points" tmp_featurelayer = "tmp_featurelayer" str_punktid = f"({punktid},{startpunktid})" arcpy.SelectLayerByAttribute_management(in_layer_or_view=tilknytningspunkter, selection_type="NEW_SELECTION", where_clause=f'"OBJECTID" IN {str_punktid}') When looking at the script after the packaging of the project, str_punktid and the where_clause has changed. The code has been subsituted with several ESRI_variables: g_ESRI_variable_4 = '(' g_ESRI_variable_5 = '"OBJECTID" IN ' def beregnKortesteVeg(self, punktid, startpunktid, tilknytningspunkter, traceLayer): fl_tilknytningslinje = r"memory/Tilknytningslinje" fl_points = g_ESRI_variable_2 tmp_featurelayer = g_ESRI_variable_3 str_punktid = g_ESRI_variable_4punktid},{startpunktid})" arcpy.SelectLayerByAttribute_management(in_layer_or_view=tilknytningspunkter, selection_type="NEW_SELECTION", where_clause=g_ESRI_variable_5str_punktid}') These variables (str_punktid and the where_clause) has been the same in all versions of the script and has not changed. Last time I created a working project templated was with ArcGIS Pro 3.2.x, and now I've upgraded to 3.3. In the last version (3.2) these variables was not replaced with ESRI_variables. Are there any changes to this in 3.3? Has anyone any resources on what the packaging does and why some variables are replaced with ESRI_variables?       ... View more

In one of my projects I have a point featureclass containing points which should be used for tracing a Trace Network. The trace network has simple edge. When looking at the documentation of the Trace-tool Trace (Trace Network) the parameter starting points needs to be a feature layer. I've also created a pythonscript which does the tracing. Steps in the pythonscript: 1. Selects two point features from the point featurelayer (featureclass) 2. Creates a FeatureLayer based on these to points 3. Runs the trace with the Trace tool When running this script I get this error: ERROR 002512: Shortest path requires two starting points. There are indeed selected two points and each point is snapped to the roads (edges). When adding an additional step to the script, that creates a featureclass containing the two points and creating the featurelayer based on this featureclass, it works. Do I actually need to have a featureclass for the points in the shortest path analysis and not only a featurelayer based on a selection?   ... View more

When creating a project template in ArcGIS Pro it might be useful to use a specific folder structure.  This picture shows an example. Here I've created an ArcGIS Pro project (stored in folder Skifteplan) which I'd like to share as a project template. Inside project folder, there's a folder called Skifte where there's a filegeodatabase containing some featureclasses and tables which should be distributed with the template.    When creating a project template, and creating a new project from the template, the folder Skifte is now gone and the filgeodatabase Skifteplan.gdb is placed directly under the projectfolder. Please make it possible to add a specific folder structure in a project template. ... View more

Hi. In one of my users workflows, they need to append a selection of features to a featureclass and I've created a pythonscript for doing this (appending data and corresponding field-mapping). The process of selecting features and appending might be done several times in the workflow, if the user sees the need to add more features.  I see that some users might add the same feature several times, causing duplicate features in the featureclass and this genrerates problems further down in the workflow. To restrict adding duplicate feature I've tried creating a contraint attribute rule. This attribute rule actually returns a message saying that features with same geometry is not allowed, but it inserts the feature multiple times. Do you see what might be wrong? var vegteig = FeatureSetByName($datastore, "Vegteiger") var isUnique = true; for(var p in vegteig){ if(Equals(Geometry($feature), Geometry(p))){ isUnique = false; break; } } return isUnique   ... View more

Hi. I'm working on migrating a ArcMap Toolbox from VB .NET (ArcObjects) to an ArcGIS Pro Add-In (ArcGIS Pro SDK). In the old code checks some polylines if the line is a "simple line" or if it's a circular arc. If it's a circular arc, I need to get the radius of the arc. In ArcObjects we converted the linesegment into ICircularArc and in this class there's a property for radius. I'm not able to find a similar property in ArcGIS Pro SDK, neither in CircularArc, EllipticArc nor EllipticArcSegment. How do I calculate or find the radius for a CircularArc? ... View more