|
POST
|
We're using the UNC data model from the Utility Network Community. John Alsup / Mike Miller know it. I will send information about tiers and terminals tomorrow.
... View more
11-23-2022
11:07 AM
|
0
|
0
|
7696
|
|
POST
|
I experience inexplicable and inconsistent downstream trace results. I have really tried myself understanding what is going on - I do not get it though. From a high voltage substation (HV/MV) I set a trace start flag on the secondary winding on one of the transformers and request a downstream trace - se screen dump below: As the trace is set to continue into low voltage (target tier), of course I would expect the trace to do so. In the below screen dump, you see that it does not continue into the low voltage mesh (blue lines): And zooming into a medium voltage substation (MV/LV) it is clear that the trace stops at the MV/LV transformer - se screen shot below: Really strange, cause I have successfully run an update subnetworks on the low voltage mesh, so I know that the trace from this transformer and downstream should work. Now, moving the trace start point (from the HV/MV transformer secondary) to just outside this substation and running the exact same trace I reach this inconsistent result that you see below - the trace continuing through the MV/LV transformer and into the low voltage mesh as configured in the GP: Enlighten me please, Esri (or someone else). I cannot see me doing anything wrong here - I might though. Or UN might have a bug? One thing is for sure - you have a puzzled user.
... View more
11-23-2022
06:53 AM
|
1
|
11
|
9346
|
|
POST
|
If what you need is to visualize the trace result at a higher scale, ask yourself if you actually need to show the features at this higher scale. If not, the answer to your need may be to simply output the trace result as Aggregated Lines - a graphic element built with the geometries of the trace result. Such graphic element will not be turned off a higher scales (unless you actually do something to make the do so).
... View more
11-16-2022
05:55 AM
|
0
|
0
|
2154
|
|
IDEA
|
For a meshed network subnetworks meet at open breaking units (as well as at the subnetwork controller). Typically having a subnetwork per transformer (for three winding transformers we would even have two subnetworks) very quickly an electric utility will end up having tens of thousands of subnetworks. Each of the subnetworks (Subnet Lines) generated will have a subnetwork name together with a few other attributes (https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/subnetline-feature-class.htm). Coloring Subnet Lines offers a quick overview of how the grid is fed and where tie breakers exist. Yet, coloring the many thousand subnet lines (coloring by subnetwork name, what else can I do)) we get this warning: Well, I have to click Yes to have some sort of useful coloring. Besides likely not being nice to performance having coloring based on a very large number of unique values, we also quickly see the problem: Adjacent subnetworks (subnet lines) are assigned colors very alike (or perhaps the same). In the screen dump below, the green arrow indicates a place where adjacent subnetworks are assigned contrasting colors whereas at the red arrow two adjacent subnetworks are assigned the same color: My propsal to Esri is, that when updating subnetworks, you also assign a coloring-number to each subnetwork (an extra attribute to be added). Not a color code (#3380ff) - just a number from 1 and up. Then I may choose whether 1 is represented by red, green, ... In a previous proof of concept, I showed that the entire low voltage grid (real world data for a low voltage grid feeding several hundred thousand customers) could be colored using less than 15 colors (it's years ago - I don't recall the exact number - it was less). As the utility network is persisted in a graph, without being an expert on these matters I believe such coloring-numbers could be easily generated using the so-called graph edge-coloring: https://en.wikipedia.org/wiki/Edge_coloring This way I could symbolize my subnet lines based on not thousands of subnetwork names but based on less than 15 coloring numbers. And I would be sure that adjacent subnetworks would be assigned contrasting colors; It's quite a lot easier to define 15 contrasting colors than to do the same with thousands...
... View more
10-26-2022
04:18 AM
|
5
|
1
|
1562
|
|
BLOG
|
What am I getting wrong here? Reading the 'The Configuration field uses a domain with three different values' section, I would conclude that: Scenario 1 would include Transformer, Meter, and Circuit Breakers subtypes only (NOT Switch nor Fuse as these are excluded) Scenario 2 would include all subtypes except Fuse (as this is excluded) Scenario 3 would include all subtypes except Switch (as this is excluded) Scenario 4 would include ... ? ... all ... ? ... subtypes (as no configuration removes subtypes)? If this is correct, the above description seems incorrect. More likely, I'm not getting the approach 😉
... View more
09-23-2022
03:21 AM
|
0
|
0
|
3921
|
|
POST
|
What you report as an error could very well be a real-world scenario - parallel connections (overhead lines / cables) between two point in the network. You'll likely have to do your own analysis to find line features with duplicate geometries.
... View more
09-04-2022
11:28 PM
|
1
|
0
|
1196
|
|
POST
|
I doubt changing tolerance is the right approach. It'll likely render new issues - e.g., performance. And what would be the 'correct' tolerance. Much better would be having Esri delivering a script parsing data to be loaded and removing irrelevant vertices; that is an arbitrary of two too closely placed vertices, of course not removing end-vertices as this may impair connectivity.
... View more
04-08-2022
04:28 AM
|
0
|
1
|
4043
|
|
POST
|
The branch versioning holds complete history allowing the user to view data for a certain date and time back in time. Is there any way of (service allowing) requesting history for a specific feature / record? It would offer great value if I where able to easily visualize history for a single feature (the breaker was created 4 July 12:15 PM, the attribute SwitchingStatus was changed from Open to Closed on 6 October 15:20 PM, ... etc.)
... View more
09-09-2021
12:46 AM
|
0
|
1
|
1791
|
|
POST
|
Assuming your post is the result of a bad Monday I take the time to answer you. It IS possible to develop your own data model for utility network; It's a complex and cumbersome task though. I suggest referring to the electric data model released by the Utility Network Community - freely available. We are actively migrating into this data model with very positive result. The data model is freely available here: utilitynetworkcommunity.com A LinkedIn post on our migration to UN: https://www.linkedin.com/pulse/migrating-arcgis-utility-network-jens-dalsgaard/ With respect to tools: Esri is delivering a framework - a very flexible one indeed. Any partner with the right skills may create tailored functionality further increasing usability. Don't give up to early. ArcGIS Utility Network is not to be abandoned - it is destined to rule the world 😉
... View more
08-13-2021
12:39 AM
|
0
|
0
|
2046
|
|
POST
|
Editing shapes in itself is not that hard. Doing it for utility network enabled features though imply a number of challenges so as to avoid stacked junctions, duplicate vertices, self-intersecting lines, etc. Do not under estimate the challenges 🙂 Yet, you are not alone in having this challenge. It would be awesome if Esri would give some input on proposed approach. That said, I would start by getting inspired by this link: https://desktop.arcgis.com/en/arcmap/latest/tools/3d-analyst-toolbox/how-interpolate-shape-works.htm Looking forwarding to following your learnings here.🙂 Best regards Jens Dalsgaard
... View more
04-23-2021
12:38 AM
|
1
|
0
|
1770
|
|
IDEA
|
Upon insert or move of a feature I would like to call a service (using X and Y of the feature as input) and use the returned result for updating an attribute on the feature in question. This seems like something I should write an Arcade expression for. Apparently this is not supported for now. I believe such capability is highly relevant considering Esri promoting the service-based architecture. Anyone out there agreeing, please give it a vote. Esri - should you already be considering this please let me know of the roadmap. Best regards Jens Dalsgaard
... View more
09-15-2020
04:21 AM
|
77
|
18
|
15445
|
|
IDEA
|
Upon insert or move of a feature I would like to call a service (using X and Y of the feature as input) and use the returned result for updating an attribute on the feature in question. This seems like something I should write an Arcade expression for. Apparently this is not supported for now. I believe such capability is highly relevant considering Esri promoting the service-based architecture. Anyone out there agreeing, please give it a vote. Esri - should you already be considering this please let me know of the roadmap. Best regards Jens Dalsgaard
... View more
09-15-2020
04:21 AM
|
7
|
0
|
10999
|
|
POST
|
Any idea about where I may seek further information on whether and when such capability may be available. Seems pretty relevant considering Esri promoting the service-based architecture.
... View more
09-14-2020
12:23 AM
|
0
|
1
|
1742
|
|
POST
|
https://community.esri.com/message/952524-is-it-possible-to-create-attribute-rule-arcade-expression-calling-webservice-and-processing-result
... View more
09-09-2020
01:11 AM
|
0
|
0
|
645
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 03-03-2026 05:24 AM | |
| 2 | 02-26-2026 02:15 AM | |
| 1 | 09-05-2025 02:34 AM | |
| 2 | 08-19-2025 04:36 AM | |
| 1 | 01-31-2023 08:01 AM |
| Online Status |
Online
|
| Date Last Visited |
Tuesday
|