AssignTerminalConnections do not work in untools 3.3.3.1

[geopamplona]

Hello,

I have a Sewer dataset on which I apply AssignTerminalConnections following sense of digitizing as not , but the tool always returns the same result.

ArcGIS pro 3.3.0
untools 3.3.3.1

I have also tried using untools 3.5 version but I get the same result; it writes changes in SewerLine, it writes log file, but there is no change between respecting or not digitizing direction, I get always same results whether I enable the check or not.

Best regards!

[MikeMillerGIS]

Can you provide some more details?  What type of device/terminal configuration are the sewer lines connected to.  Do the sewer lines have any assignment in the From/To Terminal ID fields?  

[geopamplona]

Hello @MikeMillerGIS ,

I provide more information

I am summarising it to a very specific case, but it is the behaviour I have in the whole network.

The direction of the digitalisation is from right to left (I draw a line so there is no doubt). At both ends there is a device, only the device on the right has properly configured IN(upstream)/OUT directional terminals correctly configured and assigned. The other device has no terminals assigned to it.

The result I get is that the device on the right from where the flow starts, is assigned an IN terminal to the pipe (FROMDEVICETERMINAL=IN, TODEVICETEMRINAL=NONE), when actually following the direction of the digitalisation it should be OUT. This behaviour in previous versions was correct and is the way we are using to fix the behaviour of gravity based networks in which the direction of digitisation marks the direction of flow.

I said, OK, the direction will be reversed, but I try clearing the pipe terminals (FROM and TO DEVICE TERMINAL = 0) and re-run assignterminals so that it does not honour the digitisation direction and I get exactly the same result.

I have tried this with higher versions of untools and different versions of arcgis pro 3.3.0 and 3.3.2 and I have the same behaviour. In earlier versions of untools and using arcgis pro 3.1 the behaviour was different.

Maybe we are not quite understanding how the assignterminal tool works, but so far this has been the expected behaviour.

There are no network controllers involved in the example. When I enter them I also get the same result.

Best regards !!

[MikeMillerGIS · Accepted solution]

Thank you for the details.  We did find a bug related to setting terminal in sink networks.  This was fixed in 3.5 and are targeting the 3.3.4 update that will include this fix next week.

[MikeMillerGIS]

We have released untools 3.3.4 and it is available in the python package manager.  

https://community.esri.com/t5/arcgis-utility-network-documents/utility-network-package-toolbox-3-3-r...