|
POST
|
The types of tie devices are pretty unique within each tier, so if you see an open medium voltage switch you know its a tie between two distribution circuits. If you see an open high voltage switch its for your transmission system.
Tier rank and tier name are used to indicate the tier rank and tier name of the subnetwork controller. For features that participate in the subnetwork you will need to infer this using the subnetwork name.
... View more
11-01-2024
05:44 AM
|
0
|
1
|
1062
|
|
POST
|
The process is described in full at the Configure a utility network environment help topic for the utility network foundations. In brief, you run the Configure Utility Network Layers tool from the Utility Network Data Management tools (included in the foundation) on your map.
... View more
11-01-2024
05:33 AM
|
1
|
1
|
1240
|
|
POST
|
The utility network uses a slightly larger tolerance than just the x/y resolution and x/y tolerance when establishing connectivity, so this is reflected in our analysis of vertices.
... View more
10-31-2024
10:31 AM
|
0
|
0
|
3522
|
|
POST
|
Depending on which tools you run the data will either be stored in memory or layers on your local machine. If you want to have a persistent representation of this data that you want to be accessible by other users you can build something into the end of your notebook to persist the results to a layer accessible by others (enterprise geodatabase, feature service, etc). When persisting the data you will need to determine whether its more effective to truncate/reload or try to incrementally update the layer with changes (the append tool can do this by upserting using the match fields parameter).
... View more
10-31-2024
09:21 AM
|
0
|
0
|
1932
|
|
POST
|
There is a slight difference. However, because you can get your data you should use the errors captured there to identify the features you need to clean up. You can use the Summarize Utility Network Errors tool in the Utility Data Management Support toolbox (included in the Utility Network Foundation) to create a report database that describes all the errors that you can overlay on your source data.
... View more
10-31-2024
09:07 AM
|
0
|
0
|
3544
|
|
POST
|
Glad it was as simple as clearing your cache. I'll see you next week!
... View more
10-31-2024
08:18 AM
|
0
|
0
|
1292
|
|
POST
|
I just verified I can access the link using my work and personal computer. This does link to a teams event, is it possible your IT department is blocking access to the site?
... View more
10-31-2024
08:05 AM
|
0
|
2
|
1298
|
|
POST
|
You can also use python to directly query databases. I would recommend using the technology that you are most comfortable with using and supporting. Using notebooks or a python script is going to have a smaller footprint in terms of licensing/installs, but using the Data Interoperability extension is going to allow you to have access to more data formats and ways of transforming the data.
... View more
10-31-2024
08:01 AM
|
2
|
2
|
1953
|
|
POST
|
To bulk load associations into a utility network after the fact you need to use the Import Associations tool. The tool takes a CSV with the global ids and layer information for each feature you want to associate. You can create this CSV using something like python or FME/Data Interop, whichever you're most comfortable with.
... View more
10-30-2024
02:57 PM
|
1
|
0
|
1065
|
|
POST
|
I often refer to this article for these discussions: Understanding the Differences Between Utility Network Maps.
The first graphic in the article should help understand this better:
When you "publish a web layer" you are creating a feature service for the features in your enterprise geodatabase (this feature service SHOULD NOT include subtype group layers or any additional symbology). When you "publish a web map" you are taking a display where you have applied configuration (labels, symbology, etc) to those feature services and wish to share the resulting display with web/mobile users. There are situations where you can have multiple feature services, but you shouldn't have a separate service for each map (ne feature service should support many maps).
... View more
10-30-2024
12:35 PM
|
2
|
1
|
3466
|
|
POST
|
You'll want to follow this article for instructions on how to publish the service and maps required to support an enterprise deployment, you can find additional detail in the online help about publishing and consuming utility network services. You can also find detailed instructions for publishing services in the solutions documentation.
If you want to use your web map for tracing (experience builder, web editor, etc) you'll need to include one or more trace configurations in the web map you've published. You can find detailed instructions for configuring a web application for tracing in this article.
... View more
10-30-2024
06:36 AM
|
1
|
4
|
3492
|
|
POST
|
What you're talking about only applies to overhead transformers, the standard for underground/padmounted transformers is quite different...with that in mind.
I would typically use something like the Esri Data Interop extension (or Safe Software's FME Workbench, it's pretty much the same thing) to do this. You'll need to create the junction, fuse, and transformer(s) based on the insertion point of the original transformer and its orientation. You'll then need to create lines (or connectivity association) to connect the electrical features. If you're creating an asembly you'll need to create containment associations for the new features. If you are modeling relationships between the transformer and structures you'll need to create attachment associations for the new features.
... View more
10-29-2024
10:16 AM
|
1
|
0
|
1618
|
|
POST
|
Step 1 is going to be use the Export Attachments tool to get the photos out of the FGDB. From there you can either make changes to the photos on your local file system.
Step 2 is to Generate Attachment Match Table to line up the attachments with their corresponding SDE feature.
If storage is an issue in your SDE I would consider keeping the files on a file system and use the match table to maintain a link to the files in your SDE. If you do decide to load the attachments into your SDE you would use the Add Attachments tool.
... View more
10-29-2024
07:02 AM
|
0
|
0
|
1263
|
|
POST
|
@helderhelder First question, why do you need to change the transformer to have a tap? If you are modeling your transformers as devices with related units (or non-spatial objects) you don't need to create a tap as long as you are willing to split the medium-voltage lines wherever you have a transformer. This can be done during data migration, or in bulk manually using the "By Feature" tab in the Split tool.
... View more
10-29-2024
06:56 AM
|
0
|
0
|
1630
|
|
POST
|
The above script is pretty good, although there are a few issues you'll need to adjust to suit your data. Consider this crudely drawn example:
Instead of using the entire trail line you will likely need to break each line into multiple segments, so you only consider the angles of the line segments that intersect each other.
The orientation of these line segments may not always be consistent, you may need to periodically flip the orientation of a segment when doing your calculation.
If you found all the locations where trails intersected, buffered those points out slightly, and calculated the angle of each line intersection that would solve most of these issues. You would just need to flip the angle of the line that represents the angle of travel.
... View more
10-28-2024
05:48 AM
|
0
|
0
|
1238
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | yesterday | |
| 1 | 03-30-2026 07:24 AM | |
| 1 | yesterday | |
| 1 | Thursday | |
| 1 | Thursday |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|