POST
|
Do you really need subnetworks? Of course, without subnetworks you would lose the ability to run a subnetwork, upstream and downstream traces and many other features and characteristics of subnetworked features. However, these could be replicated by other means if you really wanted to. Guess it depends on how much work you wanted to do and/or the business value tradeoff. 🙂
... View more
12-12-2023
08:42 AM
|
0
|
0
|
249
|
POST
|
Caveat Emptor: there is a cost to modeling fields as network attributes, that cost is measured in the synchronization of the network attribute with its database value(s), and vice-versa. Furthermore, there are subtleties about how the attributes are updated (or not) depending what type of version the data is being edited in (child or DEFAULT) and what the related settings are. Generally, you want to designate fields as network attributes that are sure to be used in a given trace setup or configuration.
... View more
10-23-2023
07:42 AM
|
1
|
0
|
641
|
POST
|
If you modeled it as a containment association, this would work. Might not make logical sense (for a pipe to "contain" a hydrant"), but hey...it's a solution.
... View more
10-19-2023
11:23 AM
|
1
|
1
|
378
|
POST
|
BUG-000161632: EditOperaion.Create() or Delete() throws "Edit Operation Failed" Error when creating/deleting Utility Network Associations in ArcGIS Pro SDK 3.1. Solution is to use UtilityNetwork class instead, something like this: HashSet<Table> dirtyTables = new HashSet<Table>();
Table tableFrom = this.utilityNetwork.GetTable(fromElement.NetworkSource);
Table tableTo = this.utilityNetwork.GetTable(toElement.NetworkSource);
dirtyTables.Add(tableFrom);
dirtyTables.Add(tableTo);
editOperation.Callback(
context =>
{
var newAssociation = new Association(this.AssociationType, fromElement, toElement);
this.utilityNetwork.AddAssociation(newAssociation);
}, dirtyTables);
bool result = await editOperation.ExecuteAsync();
... View more
09-28-2023
12:13 PM
|
1
|
1
|
823
|
IDEA
|
Probably a dumb idea, but could you move your abandoned features into a representative structure class? Then you could still track them as associated structures (if you wanted to) in traces, but none of the side-effects of disrupting traces, etc.
... View more
09-08-2023
08:04 AM
|
0
|
0
|
772
|
POST
|
Can do it the old-fashioned way of manual inspection. For each rule writeout to console. Console("<Rule name here> in use."); 🙂
... View more
09-08-2023
08:00 AM
|
0
|
0
|
292
|
POST
|
Yes, the nature of my question is if it is "ON" in named version, does it need to be "ON" in default? For efficiency reasons, of course.
... View more
08-25-2023
03:37 PM
|
0
|
0
|
637
|
POST
|
Thanks @MikeMiller , that makes sense. Question is, what does Eventing do if it's OFF in default? Direct writes to existing rows make sense - but eventing is responsible for more than which rows are updated or created, documentation states it is used for things like Editor Tracking, Attribute Rules, and Related Feature Annotation among other things. Hence, turning this off - does this turn "off" this functionality - even in default?
... View more
08-25-2023
08:08 AM
|
0
|
2
|
649
|
POST
|
Is it possible it can be reconsidered for a 3.1 patch release? Our teams work with the supported Network Management release. and consequently, won't be moving to 3.2 anytime soon. This fix would be very helpful for developers working under these conditions.
... View more
08-24-2023
03:33 PM
|
2
|
0
|
907
|
POST
|
Only features that have been modified in the version will have their subnetwork information updated when running update subnetwork in a version with eventing disabled. But this is inconsistent with the documentation which says When using this option (Without Eventing) with the default version, all features and objects in the subnetwork are updated.
... View more
08-23-2023
10:01 AM
|
0
|
4
|
690
|
POST
|
Yes, lots of questions. Thanks for taking a stab at it @RobertKrisher ! From the subnetwork definition documentation: eventing OFF(False) on DEFAULT the "propagated values and subnetwork definition will be edited in place" (1) Does this mean with it Eventing ON(True) in default they won't be edited in place? Or...is the behavior the same regardless of the setting for DEFAULT? The Pro documentation on the subject is less ambiguous, "all features and objects are updated" when "using this option" (2) Which option? Without Eventing = False? Again, what about Without Eventing = True? What happens then? Does it even matter? I thought I understood this topic but the more I look at it, the less I do...perhaps looking at it too long lol.
... View more
08-23-2023
09:35 AM
|
0
|
0
|
700
|
POST
|
08-23-2023
08:36 AM
|
0
|
8
|
769
|
POST
|
HI @VaL I think you have a lot of good suggestions in this thread on getting more detailed information - I was attempting to meet you where you are at and not overwhelm you with UN complexities right from the get-go - there is plenty of time for that. 🙂 | I assume this is part of a UN Yes. | asset group and asset type are domains? AG is a subtype and you are correct that the "super-subtype" (a term of my own making to facilitate understanding) is represented by a domain dedicated to that end. | (W)here is the voltage separation by asset group? Transmission is HV, Primary is MV and Secondary is LV | If you created a FC called electric line, what and where are the constraints imposed by the UN in terms of number of FCs? A UN implementation requires each of the documented feature classes, nothing more, nothing less. If you did create a FC called "Electric Line" not only would it be confusing to the user, it would not be recognized as part of the Utility Network definition. Hope that helps you along your way. As @RobertKrisher a schema model may be worth a "million words" and indeed that may be true - but I would encourage you to take baby steps and understand the foundational concepts before diving into the myriad of nuance and detail, It is easy to get overwhelmed - at first but, it's also totally learnable and as you will soon see, it has a lot more potential than the GN did/does.
... View more
07-26-2023
08:28 AM
|
0
|
0
|
1251
|
POST
|
HI @VaL and welcome! This could be a very lengthy conversation and explanation as there are quite a few differences between UN & GN. However, specifically to your question @VaL wrote: (snip) For instance will the 2 feature classes HV and LV become entries in one line feature classes of the UN each with attributes describing their voltage? And which term would this be asset class or asset type The answer is "yes". 🙂 What was formerly known as the feature class subtype is now known as Asset Group and a new "super subtype" (a subtype of the subtype) is referred to as the Asset Type There are many ways of organizing the data with these two new constructs. One common practice is to put HV in one Asset Group and MV and LV in others. Then, within those Asset Groups, you can further characterize the data by Asset Type. A picture is worth a 1000 words?
... View more
07-25-2023
01:05 PM
|
4
|
2
|
1359
|
POST
|
Hi Sirish, yes I discovered my error. I was attempting to merge two different asset types. Since they were two different asset types they didn't snap together when initially edited, hence the "Multipart Geometry not supported" error when attempting to merge. After seeing the error of my ways, I made them both the same asset type, then validated, saved and tried it again and it worked (?). Why was I getting a multipart geometry error when they were different asset types but not when they were the same? Something seemed off still. I attempted it again, but this time with fresh new lines. I snapped the two different asset types together by changing the asset type mid-edit such that it didn't change the snapping rules. When I went to merge, I got "Selection must be from the same layer" from the Merge tool. That's fair - except that they were both primaries and from the same layer... After this I just hung it up - there is some weirdness going on, not sure where but ...past the error. 🙂 Maybe TMI, but in the off chance you get some strangeness going on too...well, I do to.
... View more
03-17-2022
09:55 AM
|
0
|
0
|
633
|
Title | Kudos | Posted |
---|---|---|
1 | 10-23-2023 07:42 AM | |
1 | 10-19-2023 11:23 AM | |
1 | 09-28-2023 12:13 PM | |
2 | 08-24-2023 03:33 PM | |
4 | 07-25-2023 01:05 PM |
Online Status |
Offline
|
Date Last Visited |
01-10-2024
10:04 AM
|