Hello,
I am considering implementing geodatabase topology within the Utility Network Model (UNM). Could there be any unforeseen consequences with this approach? Specifically, I’m curious if performance might be impacted, given that the Utility Network already includes its own network topology.
Given that we have been using geodatabase topology for quite a while, we would want to implement geodatabase topology instead of data reviewer.
A class can only participate in one controller dataset. So if the classes are controlled by the Utility Network, you cannot create a topology on those classes.
I was proven wrong
Hello @MikeMillerGIS , i have created geodatabase topology for this UNM and seem that it is working. Do you mean like I should not create topology on UN feature class? If I do, could it lead to some unforeseen consequences?
Well look at that. I am wrong. That is good to know. I retract my comment.
There will be some overhead in editing and validating since you have two sets of controllers each with different dirty areas, rules, and validations. You'll also want to be mindful of any restrictions to web/mobile workflows when using this dataset since you will be limited to the features of the dataset with the most restrictions in each case.
Hello @RobertKrisher & @MikeMillerGIS, may I know if there are any reported limitation for using geodatabase topology in UNM for now? Or any documentation on discussing geodatabase topology in UNM especially on performance wise. Will it make the performance of UNM become slower during data editing? Thanks so much.
In terms of performance and limitations, it is as I outlined in my previous reply. You are the first person I've encountered who is attempting this configuration and I'm not aware of any reported limitations, outside of any limitations associated with using either of these datasets.
Before going into uncharted waters, I would ask myself whether the potential benefits outweigh the risks and how quickly I could adjust course if it doesn't work out.