Latest Contributions by RobertKrisher

@GIS_Solutions , @Sneha_Das This question was promoted to the ideas section of the community. If you are interested in seeing this become a feature, please vote for this idea. ... View more

Please post an image of the symbology properties for the layers in question. ... View more

This is a function of your asset management system. Without an Asset ID, or other unique identifier, there is no way to identify a unique section of pipe. If a pipe is split in the GIS then you should ensure that one of the new segments gets a new ID to preserve uniqueness. Your asset management system would then need to be updated to reflect the length of the old pipe as well as the length of the new pipe. ... View more

@MaryamAlHefeiti You're copying data from a simple feature layer to a geometric network layer. The geometric network imposes additional restrictions (like the one outlined in the KB article Cody referenced). You'll need to find and repair any features with the same location for their start/stop vertex. ... View more

This is outlined in the article I linked to, so you may want to do a closer reading to make sure you were following all the points. When you set manage isdirty=false, the subnetwork will always have the status of dirty. For customers with large water and gas systems, it does not make sense to track status because any time any edit occurs in the network the entire system becomes dirty. By setting manage isdirty=false it makes their validates a little faster (because it doesn't have to trace the entire system) and they just run a script to update their system subnetworks several times a day. The default behavior of the system is to track the status of subnetworks, we added the option to not manage the status for customers using hierarchical networks that had large tiers like the system tier. We would never want to you have a tier configured to manage status and then allow a user to opt-out during validate because this would invalidate the state of the entire system. ... View more

No. Open/closed is a condition barrier because it affects the normal traversability between the isolated location and its controller. The filter barrier is used to specify the criteria for identifying normally traversable features that should be used for isolation purposes. This is typically things like operable equipment designed for isolation (e.g. system or isolation valves), or in a pinch ... pinchable pipes. ... View more

I'm still waiting for you to answer my initial question around what your use case is for this. From your discussion, it sounds like you want the state to be normally managed but want to give users the ability to opt out of this check. But why? If a user opts out of marking subnetworks as dirty, then they are destabilizing the system by allowing a subnetwork to appear clean when it actually needs to be updated. This means that the subnetwork name and "is connected" field can no longer be relied on to be accurate. Any integrations, interfaces, or tools that rely on that information or look at the status/last modified date of subnetworks will also become unreliable or out of sync with the GIS. Given all these problems, what is the driver behind this? Why are you intentionally wanting subnetworks to ignore certain edits and have their information become out-of-date (with no indication that it is inaccurate)?   ... View more

There is currently no tool to perform this or any plan to develop one. If you want to create a reporting database of all your layers, I recommend you check out the Export Reporting Data tool from the ArcGIS Solutions team. ... View more

@JürgenBiendara we have a detailed article explaining the purpose of this option here Subnetwork Deep Dive: Status. I'll try to summarize it here. Managing Dirty means that when data is validated, the system will identify which specific subnetworks were modified by the edit. This is used to assist in quality assurance, so an editor knows specifically which subnetworks need updating. If you disable this setting, then the system will no longer perform this analysis and every subnetwork will always be considered dirty. Running update subnetwork is always a separate operation that must be run separately by a user (or process), the state of clean/dirty is just a way of indicating which subnetworks have been modified. So, if you care about precision with your quality assurance and just focusing on the subnetworks that have changed, you want to manage the status of your subnetworks. If you don't have any subnetwork-specific quality assurance and are ok with just running update subnetwork on all your subnetworks on a periodic basis, then you can disable managing the status of subnetworks. ... View more

@JürgenBiendara can you provide a bit more context for why you want this? Is it that you want to set a tier to be managedirty=true and occasionally ignore a validate? Or do you want to have a tier be managedirty=false and choose to only mark the network as dirty at a time-and-place of your choosing? ... View more