|
POST
|
You can only create Edge-Junction-Edge connectivity (and rules) for Electric Junction Objects with other non-spatial objects. You can find the full list of how different types of features are allowed to be connected on the feature restrictions page of ArcGIS Help. For Domain Junction Object to appear with an Edge-junction-edge connectivity rule, both the From Table and To Table must be Domain Edge Objects.
... View more
05-18-2025
08:18 AM
|
1
|
0
|
1138
|
|
POST
|
I recommend you continue to work the case through support, there is something very unusual happening with your data that I don't think we're going to be able to work through in the comments section here.
... View more
05-16-2025
11:15 AM
|
0
|
0
|
2153
|
|
POST
|
If you want to limit the data extracted data spatially, use Offline Work Areas. There currently isn't a way to limit the data extracted using an attribute. Consider using the Copy GP tool instead to copy the feature dataset directly to a mobile geodatabase, bypassing the need for an XML workspace document (which can get quite large). @MikeMillerGIS Does ArcGIS Solutions have a tool that would allow you to only copy out some features of the UN to a mobile geodatabase? Anything involving asset packages?
... View more
05-16-2025
11:11 AM
|
0
|
2
|
1297
|
|
POST
|
@BryanMay531 If we didn't have this behavior, you would have to explicitly set the terminal connections for every transformer in your system, which would make editing your conductors tedious. It makes sense that you wouldn't need to populate the terminals for your elbows, since the line side should always be connected to a conductor/cable and the bus side should always be connected to the bus work. Your rules may not be as clear cut, depending on your drawing standards. If you allow an elbow can be drawn with buswork or conductor on BOTH sides of the elbow THEN you will need to have rules allowing for this and will need to explicitly populate terminals on each line.
... View more
05-16-2025
11:06 AM
|
0
|
2
|
1943
|
|
POST
|
@Olusoji23Here's the process you should be following Instead of running Create Feature Dataset and Create Utility Network, you should use the Stage Utility Network tool in the UN Toolbox. You can find instructions for the migration and deployment process in this article/video series (if you already have a migration, you can ignore the data mapping/migration steps). You should be relying on the service territory from the asset package during your staging/deployment process. My guess is
... View more
05-15-2025
06:24 AM
|
0
|
3
|
2194
|
|
POST
|
@ChrisCyphers For your mappings you should only select the class that corresponds to your wastewater treatment plant. We discuss that step in the Migration toolset video, and the whole video gives a lot of tips and tricks worth knowing. Making most of your devices controllers is going to put terminals on everything, which is going to cause a lot of unnecessary errors.
... View more
05-14-2025
10:04 AM
|
1
|
0
|
1204
|
|
POST
|
@Olusoji23 Did you deploy your utility network using the UN Package tools? If so, they should have appended the service territory into your utility network when you staged your utility network. Adding in @MikeMillerGIS from the ArcGIS Solutions team.
... View more
05-14-2025
08:48 AM
|
0
|
1
|
2211
|
|
POST
|
@gpgisandsky yes, I am suggesting you try copying a utility network with an enabled network topology from a local geodatabase to an enterprise geodatabase.
... View more
05-14-2025
08:45 AM
|
0
|
2
|
3758
|
|
POST
|
@gpgisandsky Does this work in a local geodatabase? What happens if you copy the enabled network topology to enterprise and version it?
... View more
05-13-2025
08:30 AM
|
0
|
4
|
3793
|
|
POST
|
@AmyCleare this information will be available once ArcGIS Pro 3.5 and ArcGIS Enterprise 11.5 release. As a reminder, you can find the existing documentation about utility network versions and backwards compatibility on the Utility network compatibility page.
... View more
05-13-2025
08:28 AM
|
0
|
0
|
2576
|
|
BLOG
|
Propagation and Electrical Phasing In this article we will look at more advanced, practical examples of how electrical networks propagate phase in an unbalanced distribution system. If you aren’t already familiar with how propagation works, please read the Explore attribute propagation and attribute substitution article. You can also find more details about this behavior in the Use attribute propagation topic in the ArcGIS Online Help. Because the only way to directly observe propagated values is through the fields maintained by running Update Subnetwork, we will start by looking at how that process enforces propagation. Subnetworks As you saw in the previous article, the utility network will propagate phasing values as it walks the network. When a feature has valid phasing it will become part of the subnetwork, otherwise it will be de-energized. The examples shown in the previous article were simple linear examples, but the implementation of propagation also manages branching paths and loops. This means that if individual phases split and meet up downstream, the system can propagate the combined phases. An example of phasing splitting and recombining. Splitting and combining phases can lead to individual phases in an electric line going in different directions, causing the line to become looped and have indeterminate flow. Features that fail to propagate a value are called propagation barriers and are treated as de-energized. Propagation barriers are different from other barriers because propagation barriers are not included in the subnetwork regardless of the Include Barriers Feature setting of the trace. A device on the A phase will restrict the phasing of all downstream features to A phase. Propagation barriers, and the features downstream of them, are not part of the subnetwork. This is an important form of quality assurance since it allows you to quickly identify features with an invalid phasing as de-energized. The B-phase line downstream of an A-phase device will be de-energized Another important part of quality assurance is to look for features that are only partially energized, also sometimes referred to as being under phased. These are features that have one or more phase that is not energized. These features will still belong to a subnetwork but features downstream of them may become de-energized. You can identify an under phased feature by comparing the Phases field on the equipment to the Phases Energized field. A three-phase line downstream of a single-phase device will only have one of its phases energized. Now that we have seen how phasing and update subnetwork behaves with simple features, let us look at some examples of how it behaves with a device that has terminals. Terminals Tracing, barriers, and propagation behave differently when they pass through a device with terminals. This means that an open switch or the phasing of a transformer will only affect the trace when it passes through the device. This is why you can draw a single-phase transformer in-line with a medium voltage conductor. The phasing of a single-phase distribution transformer does not affect a medium voltage three-phase conductor because it connects to the high side of the transformer. The phasing on the low voltage conductor is determined by the phasing of the transformer because it only receives the phasing that passes between the high-side and low-side terminals. The phasing on the high-side of a transformer is not restricted because it doesn't pass through the transformer. This situation works well for transformers, but it is something to consider with other devices that use terminals. There are several ways to represent protective equipment for a tap line. The recommended way is to place the device offset from the main line, along the tap line so the map clearly shows which line is protected. However, you can draw the device at the intersection of the main line and tap line if the device has terminals and the terminals are connected properly. In cases where a single-phase device is protecting a tap line, the main line should connect to one terminal with the tap line connected to the other terminal. If we revisit the example above with a single-phase switch on a three-phase line and use terminals to manage the different connections with the main line and tap line, we can see phasing is now correct. Terminals can also be used to represent equipment that protects or isolates tap lines without restricting phasing on the main line. What do you do if your switch or protective device does not have terminals and you still want to have it not restrict the phasing? The Subnetwork Tap network category can be assigned to a device or junction asset type to accomplish this. Assigning the Subnetwork Tap network category to a device or junction asset type, those features will no longer restrict phasing when drawn midspan on a line. However, it also means that those features must always be midspan on at least one line. Below is an example of a tap line connected to a main line using a junction feature that is a subnetwork tap. Subnetwork taps also allow you to not restrict phasing when a device or junction is drawn midpsan on a conductor, without needing to use terminals. Looking at the example above we can see that subnetwork taps offer a way to represent the equipment for isolating or protecting a tap line when the equipment doesn’t have terminals, or you don’t want to split the main line. This is done by adding a subnetwork tap on the main line, then placing the device on the tap line as shown in the example below. Subnetwork taps can also be used in conjunction with isolating or protective equipment, when that equipment doesn't have terminals. Let us use this understanding of how propagation respects terminals, subnetwork taps, and is capable of splitting and recombining phases to solve the following problem: how do you model a single-phase device, like a recloser or regulator, installed in-line on a three-phase line? In this case you model the jumpers that bypass the device in the field to ensure that all three phases are available downstream of the equipment. You do this by creating subnetwork taps on either end of the device, then letting the two unprotected phases bypass the protection equipment while letting the protected phase trace through the device. When single-phase equipment is connected in-line with a three-phase conductor, you need to create a bypass for the other two phases. Boundary Devices Another interesting situation to consider is how to calculate the energized phases when a device exists between two circuits? In this case each circuit will propagate its phasing then the shared features receive the combined phasing from each circuit. The most common example of this is a three-phase open device between two circuits. A less common, but equally valid example, is to have a single-phase device between two circuits with distinct phases. A device that connects distinct phases from adjacent circuits is not common, but the utility network does model it correctly. Open devices between two subnetworks belong to both subnetworks. A similar issue arises when a customer connects to two transformers that belong to different circuits. In this case the customer, low-voltage conductor, and the transformers will all appear as belonging to multiple circuits. The utility network supports connecting a customer, or subset of each subnetwork, to multiple subnetworks but it is more likely to be bad data than a deliberate engineering decision. It is possible for sections of an electric network to belong to two different subnetworks, but this is often an indicator of a data quality issue. If you keep an eye on your subnetwork name field, and if you see a conductor or device that is not a tie device that belongs to more than one circuit you should investigate! Conclusion If you’re interested in learning more about tracing and analysis with ArcGIS Utility Network, you should visit the Analysis and Tracing with ArcGIS Utility Network learning series. This series contains a collection of articles, videos, and tutorials to help familiarize you with tracing, subnetworks, and ArcGIS Utility Network. If you have specific questions about how to solve different workflows, please visit us on the ArcGIS Utility Network channel on the Esri Community site. This is an active community with thousands of active members.
... View more
05-13-2025
08:25 AM
|
6
|
0
|
3913
|
|
POST
|
@gpgisandsky I will try to keep an eye on it as it develops, but at this point we need to work it through the process until we can get something reproducible to development. If you copy your utility network from Oracle to a File or Mobile Geodatabase, does it succeed there? If not, that's a much easier reproducible issue to push through support. If you can enable the network topology in a local geodatabase, try copying the dataset back into an enterprise environment and version the dataset. If versioning fails, that narrows down the issue. If that works, then you can move forward with that utility network.
... View more
05-13-2025
06:17 AM
|
0
|
6
|
3802
|
|
IDEA
|
A solution to this approach is discussed in this article: https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/utility-network-design-to-operations/
... View more
05-12-2025
08:25 AM
|
0
|
0
|
1548
|
|
POST
|
@SanchezNuñez Add a new column called something like "Rename_Foo" and put the value "Treatment Plant" in that column for the row that corresponds to "Treatment". When you deploy the asset package, you will see an option to rename using "Foo".
... View more
05-12-2025
07:19 AM
|
0
|
1
|
1684
|
|
POST
|
@DavidSolari has called out the most likely scenario. Look at the Design pane for your Attribute Rules and see if there are rules associated with that field that have the "Editable" box unchecked.
... View more
05-09-2025
08:03 AM
|
0
|
1
|
1395
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 1 | Tuesday | |
| 1 | 03-30-2026 07:24 AM | |
| 1 | Tuesday | |
| 1 | 2 weeks ago |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|