Latest Contributions by RobertKrisher

@BrandoCrozier  If you can consistently reproduce the crash, please create a case with support. The approach outlined by @gis_KIWI4 to use the Summarize UN Errors tool is the recommended approach. ... View more

The map's coordinate system must match the basemap's coordinate system, so if you don't have a basemap in the same projection as your data, then your data will be reprojected on the fly in the map in the web. This shouldn't cause any errors in the web, but it may affect performance. If you follow the process for publishing services and sharing maps using the process outline in these articles there shouldn't be any problems. You appear to have taken a different process, and it's hard for me to understand what is going on to cause the issues you reported. Try following the procedures listed above, or if you feel you need to continue to do it the way you its set up now, please log an issue with technical support. ... View more

There are a few edge cases to this rule. Firstly, a feature can belong to many subnetworks without an error if the feature acts as a barrier between multiple subnetworks. Think of a closed valve between two pressure zones. Another less common situation is when a feature is in an area fed by two different subnetworks, but the subnetwork controllers themselves aren't connected. This can happen if you have something like a pressure zone that is fed by different water systems, but the valves in the area prevent water from one system from entering the other system. From the screenshot it looks like you are not using one of the utility network foundations, so it's for me to speculate what could be going on in your situation since I don't know how your data is configured. ... View more

This question was posted at 2 AM my time 😀 The REST documentation for the trace operation is pretty good and would have helped you figure out what was wrong with your trace locations and trace configuration globalid parameters. ... View more

If your OMS is saying the line is looped, then the line is looped. This means that either there is an open switch, fuse, elbow, etc somewhere that you haven't modeled in your GIS or that the situation is actually looped (which is fine). In the example above, there can't be 3 lines connected to a single switch. ... View more

Features with that subnetwork categories are capable of being controllers, but to make them controllers you must use the Modify Subnetwork Controllers pane. The barriers are defined in the subnetwork definition for that tier. Any feature that meets the condition barriers defined for that subnetwork will be treated as a barrier. In the water utility network foundation a pressure zone treats features that are closed or features that are proposed as barriers. A system valve between pressure zones is typically kept closed, meaning it will act as a barrier, but if you set the pressure zone system valve to be open it will no longer act as a barrier (which will likely result in inconsistent subnetwork names between the pressure zones on either side of it). ... View more

I guess I've lost the thread here. What is the problem you are trying to solve? Is there an error you are receiving in the utility network? ... View more

The utility network can export a network with loops without any problems, the only thing that would be an issue is an area is fed by two different subnetworks (i.e. feeders) at the same time. In the diagram above there is no way for you to energize the customer without for FDR 295 without also connecting them to FDR 273, my guess this is a problem with how the diagram is depicting the connectivity. If you discuss the field configuration with an engineer or operator familiar with the area they should be able to show you how the switches/switchgear in the area are configured to allow the system to shift the customer from one feeder to the other without paralleling the system. My guess is that the switch in the top of the diagram is to the left of the tap, and the closed switch at the bottom is likely a switching cabinet / switchgear with switches for either feeder and a fuse on the customer side. ... View more

You can disable snapping or use the disconnect tool to temporarily suspend the snapping/rubber banding behavior while editing in Pro. Disabling the network topology requires dropping and rebuilding the topology for the entire network, which requires stopping services, so it's not feasible to do that for a single edit. ... View more