|
POST
|
If you want a controller to propagate out as de-energized then set its phasing value to be de-energized. So you'd need to have some kind of check or process that would adjust the phasing of the controller when its no longer energized from its parent subnetwork.
... View more
yesterday
|
0
|
0
|
41
|
|
POST
|
Currently the only way to do this is through a post-processing step, but if you log a case with support there is an existing enhancement you can help escalate: ENH-000126146
... View more
yesterday
|
0
|
0
|
18
|
|
POST
|
@Rohanrajan if you select the junction and move it, do both lines come with it?
... View more
yesterday
|
0
|
0
|
5
|
|
POST
|
There are some differences between the labeling engine of ArcGIS Enterprise/ArcGIS Pro and the JavaScript labeling engine. Because this is a Web Map question I'd recommend you check that community for recommendations about which label settings to use/avoid.
... View more
yesterday
|
1
|
0
|
11
|
|
POST
|
Create a web map pointed at the feature service using the desired label expression and placement properties. Then reference that web map in your experience builder and field map applications.
... View more
Wednesday
|
0
|
1
|
91
|
|
POST
|
Capturing directly into an asset package is a little unusual for manual editing is a little unusual. Why not deploy the utility network to a local mobile geodatabase and let your user edit it there? Editing in an asset package means you won't have access to any of the tools for populating terminals, associations, or subnetwork controllers. You also won't have any of the built in intelligence of the editing tools to enforce snapping/connectivity rules or validating your topological edits. Anyways, if you are going to capture in an asset package, you can let the users edit as normal in the asset package. But before deploying it run a script that will find any blank guid columns (the 000... that you mentioned above) and calculate them to a proper value. This can be done by modifying the script Patrick provided to identify GUIDs that need to be recalculated. Doing it incrementally would allow you to deploy the asset package to a mobile geodatabase on a weekly basis to do QaQc (enable network topology, look for errors, then correct them in the source data).
... View more
Wednesday
|
1
|
1
|
54
|
|
POST
|
Run a subnetwork trace with the aggregated geometry result type to see EXACTLY where the subnetwork stops. The most likely scenario is that the pipe itself has become a barrier (lifecycle status is the most common cause) or there is a feature on the pipe that is acting as a barrier (lifecycle status, activate volume, or device status are all possible causes). In the case of a device/junction on the line being a barrier the aggregated geometry will show you exactly which junction/device is stopping the trace.
... View more
Tuesday
|
0
|
0
|
110
|
|
POST
|
Because the asset package is designed for data migration, the "globalid" field in the asset package is actually a GUID. This allows you to map the global id from your source data into this globalid (guid) field in the utility network. If we made it an actual globalid field, it would be managed by the system and you wouldn't be able to preserve your globalids through the data migration process.
... View more
Tuesday
|
1
|
3
|
121
|
|
POST
|
The junction doesn't appear to be selected, so the line is probably a barrier. If you are modeling z-values in your geometry make sure that end point of the line is actually snapped to the juction.
... View more
Tuesday
|
0
|
0
|
92
|
|
POST
|
Unless you're using the "use digitized direction" option, the digitized direction of the line doesn't matter. If the trace stops at the junction, and includes the junction in the returned features, then the junction is a barrier. Check its attributes against the condition barriers of your trace (lifecycle status, device status, etc). If the trace doesn't select the junction, its actually stopping at the line (this is the more likely scenario) which means that the line itself is a condition barrier. Once again, compare the attributes of the line against the condition barriers of your of your trace.
... View more
Tuesday
|
0
|
0
|
90
|
|
POST
|
@KokilaM I can't remember the specific asset type, but that's correct. The Power transformer that steps transmission/subtransmission voltages down to distribution levels would be a subnetwork controller for the distribution side of the station, then the circuit breakers for each feeder are also subnetwork controllers for each circuit.
... View more
|
0
|
0
|
74
|
|
POST
|
@VishApte_NGIS an upstream trace as you have described it would show you the path upstream to the valve(s) to isolate the starting location(s), but not the area affected by the isolation.
... View more
Monday
|
1
|
0
|
127
|
|
POST
|
If you want to do that you can use something like the batch trace tool to do a connected trace to get everything upstream of the processing plant. You can also set up each controller to have the same subnetwork name, maybe broken by rank (PP1 Gathering, PP1 Trunk), they're allowed to be disjoint. If you keep the model as it is right now, and set up your compressors/pumps as your controllers then when you run an isolation trace it will show you how to cut off pressure from the pump/compressor to prevent gas/oil from leaking out into the enviornment. If you were to switch to a sink-based model, the isolation trace would only show you how to prevent gas/oil from getting to the treatment plant, but it wouldn't show you how to isolate the pressure source. Given that there is a workaround for naming your processing areas (batch trace tool) but not for isolation traces, I would lean towards rely on the model as it was built. You know your data and your business requirements better than I do. Those trunk lines are probably much easier to understand how to isolate than a typical distribution system, but if you model the pipework inside stations than it will be very beneficial to have that isolate trace working the way it was originally configured.
... View more
Saturday
|
0
|
0
|
175
|
|
POST
|
@Joshua-Young @PierreloupDucroix If you haven't already, please log a case with support on this so they can get a bug created and get a fix out for the next person who comes along with an unwieldy map!
... View more
a week ago
|
0
|
0
|
161
|
|
POST
|
@SamDeLore tips for looking at logs to understand performance: Utility Network Diagnostics Parsing Utility Network Diagnostic Logs
... View more
a week ago
|
1
|
1
|
293
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | yesterday | |
| 1 | Wednesday | |
| 1 | 3 weeks ago | |
| 1 | Tuesday | |
| 1 | Monday |
| Online Status |
Online
|
| Date Last Visited |
yesterday
|