Latest Contributions by RobertKrisher

@GISUser1619_Nguyen There is at least one bug associated with the partial clipping behavior, I recommend you reach out to support to see if it resolves the issue.

It sounds like there is a loop upstream of this manhole (in actuality there might be many loops). You can use the shortest path trace to help you identify it. I recommend you copy your data out to a mobile geodatabase, upgrade it to v7, and test out the tracing with digitized direction. If you can get the digitized direction trace working, it will require significantly less data cleanup than trying to get all the terminals aligned to make consistent subnetworks. You can then use something like the Batch Trace tool or community sample to track your sewersheds.

@GISUser1619_Nguyen what you are seeing is a slightly different behavior than what is described in this issue, and it looks similar to a bug that we have a patch for. Please reach out to support with your environment information and steps to repro and they should be able to confirm whether this is the same bug.

If you haven't already, log an issue for this. Its either a bug or something that would be a good feature. Not including the version name in the on post message to the web hook seems like a good idea.

You can extend the data model in the utility network geodatabase to contain additional tables and relationships for maintenance records, etc. The features that were migrated into the utility network should not be in the new model, because they are now represented by the utility network features.

@angiexx1 in the screenshot above the symbology is using three fields (Asset group, status, operating status). Can you post a screenshot of the symbology on that layer in the map used to publish the service?

I think putting it in a utility network is a better plan, since this mean you can set up some basic subnetworks for each substation that represent what you need to extract into your OMS/ADMS. If you only care about the distribution side of each substation, set up the power transformer as a subnetwork controller and you're ready to start exporting substations (now all you need to do is transform them).

This is not available in the ArcGIS Pro SDK, but please log an enhancement request for this as its something we have considered implementing at some point in the future. However, you CAN already do this using the ArcGIS Enterprise SDK (IUtilityNetworkQuery2 Interface | ArcGIS Enterprise SDK | Esri Developer), the most common way of exposing this capability is through a SOE or SOI, in your case you would probably want to build an SOE for this.

I suspect there are multiple things happening. Let's start with something simple. Connect the lines on that manhole as shown below, configure an upstream trace with the "use digitized direction" option, and run the trace. Then post a screenshot of the resulting trace (it should look correct).

You need to determine which code you deleted from the domain and re-add the original code and description to the domain before you can reassign it.

What type of dataset is this? If its something with a system tier you could create a network diagram using that subnetwork.

@CristinHolmgren2 are you deploying this to a mobile geodatabase? or a file geodatabase? or enterprise geodatabase? Don't use a file geodatabase when working with associations, they are painfully slow for that. If you are using a mobile geodatabase, make sure it is on an SSD that is local to the machine that is running the tool. You could turn on simple build logging to see timestamps of when the various events are running.

What I'm saying is that you didn't need to extend the domain, you should have use the existing domain and values, just update the descriptions to match the customers data. I have already provided a proposal of how you could have mapped their values to the original values. You should be able to incorporate that into your data migration going forward, and if you need to fix it right now you can adjust the data and schema in the asset package to make the correction. You can see the bitsize in the network properties. Because you are using an asset package to build your utility network, refer to their documentation for hot to control the size of an inline attribute: Utility Network Package_Asset Package Reference.pdf

There is no such thing as creating a new association role. The roles are none, container, and structure. If you are setting the association role of an asset type (e.g. handhole) from None to a Container you will be able to do that as long as the topology is disabled. If the Handhole is already set to be a Structure and you want to make it a Container, then you are altering the association role, which is not allowed once you have enabled the network topology. Based on the error you are receiving, it sounds like this is the case. If you want to alter an association role after enabling the network topology you will need to go back to an asset package, remove any containment/attachment rules associated with it, change the role in the asset package, add new rules, then re-deploy your utility network. You can see what the asset type's current association role is by opening the tool or looking at the network properties (choose the show default values option to make it clearer). The association role of the handhole in the utility network foundation is structure.

The domain you have configured to set the bitsize of your phasesenergized domain (Electric_Phase_Attribution_All) only allows for 3 bits (max value = 7) The domains you have assigned to your features appear to have a maximum value of 14, which requires 4 bits. Furthermore, it looks like you just added RYB values onto the end of the domain instead of using the existing coded values and renaming the descriptions. This is important, because the way you have done this does not allow for the bitwise combination of the different phases, which will result in phase propagation not working correctly. It looks like RYB = ABC, and my guess is if you look at the original coded values in your source data you will see that the integer values from your original domain matched (R=4, Y=2, B=1, and RYB=7). After inspecting your data, it appears that you should have just mapped your phasing values to the existing domain values instead of extending the domain.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by RobertKrisher

Re: Validate doesn't validate "Error" dirty areas.

Re: Valid paths not routing upstream trace correctly through features in multiple subnetworks (Sewer Tee junction)

Re: Dirty Area Status meaning

Re: How to determine Version Name from OnPost WebHook

Re: Combine Utility Network and File GDB into one

Re: Published UN webmap showing coded domain value instead of description

Re: Trace Network in the ArcGIS Pro SDK

Re: Trace Network in the ArcGIS Pro SDK

Re: Valid paths not routing upstream trace correctly through features in multiple subnetworks (Sewer Tee junction)

Re: Utility Network – ERROR 004049 Unable to modify domain, one or more asset types have been deleted

Re: Has anyone created a One Line Diagram or has employed a third party?

Re: 14 Million Associations - Best way to load to Utility Network?

Re: ERROR 003856:* The max value of the domain exceeds the bit size of the network attribute while applying asset package

Re: Association Roles/New Rules

Re: ERROR 003856:* The max value of the domain exceeds the bit size of the network attribute while applying asset package

Re: Combine Utility Network and File GDB into one

Re: 14 Million Associations - Best way to load to ...

Re: Association Roles/New Rules

Re: ERROR 003856:* The max value of the domain exc...

Re: Isolation Trace - Skip Certain Control Valves ...

European Utility Network Community (UNC)

APAC Utilities Community of Practice