Latest Contributions by JanCreupelandt

‎10-08-2021

Had the same experience. seems to be solved with 2.8.3, at least with 2.8.3 I can install untools now.

‎07-08-2021

yes, this is exactly what I followed. Jan

‎07-05-2021

Hi, Installed Pro 2.8.1 on a clean machine (so, no upgrade). I cloned the Python Env, and closed Pro. Installed the untools via Python command: conda install -c esri untools When starting a new Pro project, I get this error: after click OK, no geoprocessing toolboxes appear anymore. Anybody got the same issue and knows how to resolve this? Thanks, Jan

‎06-01-2021

when try to apply asset package, I get these errors: ERROR 000110: Electric Generation Station does not exist ERROR 002824: Something went wrong in Polygon/Polyline simplification. Failed to execute (SetSubnetworkDefinition). I'm using Pro2.8 with ArcGIS Enterprise 10.9 on Postgres 12. Any idea how to solve this? Thanks, Jan

‎08-12-2020

Hello, I was testing this for one week now. unfortunately, the problem still persist after I removed these .cache files. Jan

‎08-05-2020

Thanks Michael, before I do something wrong ... can you point out what folder you mean? this is how it looks like on my machine; thanks, Jan

‎08-04-2020

Hi Michael, I tried the import untools in the python window in Pro 2.6 -> this succeeded. So it seems the python is available. but the geoprocessing task is failing. After using the python window, I tested the geoprocessing task, but still got the error message. restarting pro was the only option. thanks, Jan

‎08-04-2020

thanks, but this didn't work. I'm using Pro 2.6 and I recreated a complete new python environment before I added the untools again. still no success ... Jan

‎08-04-2020

Hi, Many times, I get the message "Tool has failed to open" when trying one of the Utility Network Package Tools. Only solution is to restart Pro, and mostly this solves the issue. I already removed my Python environment, then clone the default and add the untools again. But this doesn't seems to help. I still get this behavior. This was something I never had with Pro2.5, but occurs now with Pro 2.6 Anybody has the same issue and now how to solve? Thanks, Jan

‎03-04-2020

Hi Will, 2 coordinates (X,Y) are considered coincident if the distance between both are less then 2*square root(2)*tolerance. For save we use 3 times the tolerance. So, if the tolerance is 0,001 m, then we make sure distance between 2 coordinates is >= 3mm. this is applicable for 2 consecutively vertices in a line features, and also for connectivity between 2 features. In my tests, for Z coordinates it must just differ, no matter how much. Hope this helps, Jan

‎10-04-2019

Correct: * Test 1 = copy the feature classes from my asset package to an enterprise geodatabase as simple point/line/polygon feature classes -> no errors here * Test 2 = deploy the asset package -> many duplicated vertices & self-intersecting errors remarks: * resolution in the file geodatabase (asset package) is 0,0001 & tolerance is 0,001 * I executed the check geometry on the file geodatabase before loading data, but no errors came up Jan

‎10-03-2019

Hi, I was wondering how the XY tolerance / resolution is used in the Utility Network. To test this, I first loaded the feature classes from an asset package as simple feature classes into an enterprise geodatabase. Here, I didn't got any load errors like self-intersecting points nor duplicated vertices. In my second test, I deployed the asset package. The Territory feature class has a resolution of 0,0001meter & tolerance of 0,001meter (like my initial feature classes). After enabling network topology, I see a lot of self-intersecting & duplicated vertices errors. If I zoom into the errors, I see the distance between 2 vertices for error line is >2mm, which I believe is not withing the XY tolerance. So, why do I get all these errors? is there another way to define the XY tolerance / resolution in the utility network? thanks, Jan

‎08-23-2019

Thanks! this made it working

‎08-23-2019

Hi, I tried to deploy the Electric Solution v3.1.1 Asset package with Pro 2.4 (UN Tools 2.4) & Pro 2.4.1 (UN Tools 2.4.1) to a postgres (v10 & v11) geodatabase with ArcGIS Enterprise 10.7.1. Till now, no success. I have an impression the tools fails at the moment the associations are loaded. Any idea what can be the cause or how to solve this? I tried it on different machines, but always the same issue. Also the same with the Water solution, so I don't think it's related to the asset package. Thanks, Jan

‎01-25-2019

Hi, with Pro 2.2.4 I didn't experience this issue anymore. Now, I installed Pro 2.3 and this issue is back. when I try to Enable Network Topology, Pro crashes. My data is stored on Oracle 12.2 Regards, Jan #Utility Network #Enable Network Topology

Online Status	Offline
Date Last Visited	‎07-04-2024 03:27 PM

My Ideas

Latest Contributions by JanCreupelandt

Re: Failed to Load System Tools -- Pro 2.8

Re: Installing untools causing to disappear all toolboxes Pro

Installing untools causing to disappear all toolboxes Pro

Deploy "ElectricDataManagementForArcGISEnterpriseV1" fails

Re: UNtools 2.6 sometimes fails to open.

Re: UNtools 2.6 sometimes fails to open.

Re: UNtools 2.6 sometimes fails to open.

Re: UNtools 2.6 sometimes fails to open.

UNtools 2.6 sometimes fails to open.

Re: XY tolerance in the Utility Network

Re: XY tolerance in the Utility Network

XY tolerance in the Utility Network

Re: Deploy asset package with Pro 2.4 & Pro 2.4.1

Deploy asset package with Pro 2.4 & Pro 2.4.1

Re: ArcGIS Pro 2.1 Crashes

Re: Edit NON-geodatabase spatial tables from PostG...

Re: XY tolerance in the Utility Network

XY tolerance in the Utility Network

Re: Deploy asset package with Pro 2.4 & Pro 2.4.1

Add a transformation parameter to the Geomery Serv...