Latest Contributions by RobertKrisher

The scratch workspace is a great idea, since you can re-use the same table within the same session instead of having to recreate it every time your run your tool. If you did want to create a new temp layer each time you ran your tool, I'd recommend you use the memory workspace for the duration of the trace. To do this just use the word "memory" for the workspace path (e.g. "memory\\temp_start_barriers"). ... View more

Open the Set Subnetwork Definition tool, select your low voltage tier, and look at the Subnetwork Trace Configuration > Summaries section. You will see that there either isn't a summary for calculating circuit length on this tier. You should be able to add a summary with the function of "Add", on a network attribute of "Measured Length" into the "circuitlength" attribute. Every model is a little bit different so if some of these attribute names don't match up you should use the same configuration as in your distribution/mv tier but remove the filter (that limits it to MV conductor). The circuit length is calculated using the measured length of all medium-voltage conductors in a subnetwork, so it would make sense that it isn't being calculated for your low-voltage tier. ... View more

I have not seen this done in a utility network before, but I have seen companies create geospatial models for the "vertical assets" in their treatment plants that could be used to create a utility network. ... View more

Let's pick up this discussion over in main thread where you posted this ... https://community.esri.com/t5/arcgis-utility-network-questions/treatment-plant/m-p/1275976#M2461 ... View more

The views or materialized views I have included in that blog are going to be your best way of capturing this information. The main consideration for the materialized views in THIS use case is going to be performance. The materialized views will be faster for reporting purposes. Period. If you don't want the overhead of creating materialized views AND are willing to let your reports take a little longer to generate, use regular views. ... View more

I apologize if the blog didn't properly convey the design and intention of this, I will attempt to address your questions here. The materialized view is meant to act as a stand-in for the standard view, this is not to provide additional filtering, but because of the following two reasons: Evaluating the branch version query for all rows in your database is an expensive operation, so you don't want it evaluated for the entire database any time a user runs a report! Because data is edited throughout the day, there may be dependencies between your branch version data and other system tables / processes. Materializing the view ensure that your views + reports are always consistent and are unaffected by the edits that occur throughout the day. t0_ isn't a temporary file that is persisted anywhere, its a common table expression. While you could write a query that doesn't make use of a common table expression in Postgres, our testing has found that using a common table expression in Postgres allows for the planner to create more effective plans that execute in less time that the same queries that don't make use of common table expressions. ... View more

Thanks, I'll mark this as the solution you took. You should check out the Version Management role in a lower environment if you haven't already, it will allow you (as an admin) or any other super users to make changes to default while it is protected. This saves you the trouble of having to remember to run alter version to switch the version between protected / public when making schema changes. I would say it also means that you can post changes using your normal account, but you appear to already have a process in place for handling posting to your protected default. ... View more

If that is the case, try assigning the version management role to yourself and you should be able to get past this issue. See this blog or the online help if you want more info about this role. ... View more

Yes, an edge object can contain a domain line feature. A common example of this is that a conduit (Structure Edge Object), contained by a conduit system (Structure Line), can contain a Conductor (Electric Line). Mike's point on locatibility is important, so you'd either want your edge object to be contained in or connected to a spatial object. You can find the full matrix of what is allowed for connectivity, attachment, and containment associations on this page: https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/feature-restrictions.htm . ... View more

Mike,   The fields button lists all the fields for the feature class. If you want something like the online data dictionary that has aliases and visibility at the subtype level you will need to use the "Map Field Properties' button on a map that has been configured with subtype group layers that reflect the subtype settings you want. In the example below I've exported the map field properties from the water distribution utility network foundation utility network editor display and filtered the field properties to just show the values for hydrants.   ... View more

You can find an add-in in this thread that allows you to export your utility network properties to csv files to produce reports: https://community.esri.com/t5/arcgis-utility-network-blog/utility-network-properties-extractor/ba-p/1056201 ... View more