Latest Contributions by TorbjørnDalløkken2

Hi. My organization is currently relying heavily on filegeodatabases distributed on several network drives, which has been working fine for years. We're considering migrating to a new enterprise solution (ArcGIS Server + Portal and SQL Server). Each year we start approximatly 1000 new projects (and closes other ones) and each project is independent of each other. The data is most commonly edited by one user in charge of the project, but several users might be looking at it.  I think a common geodatabase will make the data more organized and be easier to analyze for organizational purposes, but it will bring more complexity to administer. It will also be easier to migrate the workflows from ArcGIS Pro to web applications further on. Do you have any opinions on this topic? Has anyone done such a migration? ... View more

I'm experiencing a strange error when packaging a project to a project template.  I've created a project that contains two maps with featurelayers from a filegeodatabase, a predefined layout, a toolbox containing pythonscripts and a task. I've been able to create project templates from this project several times over the last two years. Yesterday I made some changes to a pythonscript and tried to create a new project template, and the packaging failed with the error: ERROR 000185: This data type is not supported I reverted the pythonscript to the original version, and tried to create the project template (which worked one hour before), but the process still fails with the same error. Since I have my project and scripts in GitHub, I've tried to change to another branch which worked two days ago. This time it fails with the same error.  Have anyone experienced this before or know what might be causing this? ESRI, please add more detailed information about what causes the error, specially which data type is not supported.   Update: It seems that the geodatabase had been corrupted. I tried creating a new project with the same database, with the same error. When replacing the geodatabase with a older copy, the packaging process worked fine. ... View more

I have a filegeodatabase containinig a dataset and some featureclasses. The dataset is originally created with the spatial reference ETRS 1989 UTM Zone 32N. One of the features in the add-in is to change the spatial reference of this dataset based on some values from a list. The code runs the "Define Projection" tool and the dataset is being updated with the new spatial reference. ETRS 1989 UTM Zone 32N to ETRS 1989 UTRM Zone 33N (or 35N). When I try to get the spatial reference of one of the featureclasses through ArcGIS Pro SDK: await QueuedTask.Run(() => { using (Geodatabase geodatabase = new Geodatabase(new FileGeodatabaseConnectionPath(uri))) using (FeatureClass featureClass = geodatabase.OpenDataset<FeatureClass>("JSRGrensepunkt")) { var featureclassDefinition = featureClass.GetDefinition(); var sr = featureclassDefinition.GetSpatialReference(); /* more code ...*/ }); GetSpatialReference() returns the original spatial reference (32N) and not the current one (33N): If I look at the same featureclass in ArcGIS Pro, I can see that the featureclass indeed is in 33N: What might be wrong here? ... View more

I have developed an ArcGIS Pro Add-in that allows users to insert several preconfigured elements into the layout. These elements are constructed using the ArcGIS Pro SDK. I need the font size of the text elements to adjust based on the layout page size. To achieve this, I created a class called "Ark" (Norwegian for "Page") which contains functions to determine the page type (A0, A1, etc.) based on the layout page's height and width, and return the correct font size. This works fine when the user selects a page size from the Layout -> Size dropdown. However, if the user selects "Page from printer," the height and width values are incorrect. For example, if the user selects ISO A4 portrait, the height should be 297 mm and the width 210 mm. But when using "Page from printer," the values returned from Layout.GetPage() are 286 mm (height) and 202 mm (width), even though the page chosen in the printer preference is ISO A4. Why do I get these differences?         ... View more

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