This blog assumes you know the basics of the utility network, to learn more visit our core help page here.
This release is focused on delivering the tracing functionality through the new named trace configuration shipped in 10.9. Trace configurations can be created and persisted on a UN 5.0 with Pro 2.7 and later. The persisted trace configuration has all the properties, filters and output required to execute a particular trace. Trace configurations can be shared through webmaps and consumed by simply referencing the trace configuration id (GUID). Read more about trace configurations here.
Opening a WebMap with utility network
Here is an example of how you can load a webmap and any utility network objects shared within it.
Reading UN Metadata and shared named trace configuration
Once the utility network is loaded successfully, you can query for its meta-data. Let’s consider few examples of properties that can be read from the utility network object.
Reading basic utility network meta-data
While most properties require fully loading the utility network definition via the load method to be accessed, some properties can be accessed without loading the un. Example are layerId, id and title.
Reading the named trace configurations
During publishing, a webmap containing a utility network can be shared with a list of named trace configurations. These named trace configurations can be accessed through the utiltynetwork object.
Reading the full named trace configurations
While the title and the globalId properties can be accessed without loading the utility network, access to the full trace configuration require loading the utility network. Here is how to access the result types of a particular named trace configuration.
Performing a trace using a named trace configuration
You can perform a trace by providing the globalId of the trace configuration and optional starting locations. You can even provide the version and moment to trace to support tracing in a version or a pervious historical moment.
In 4.20 we also introduced the ability to view associations located in a given extent. Control exists to filter what type of associations you would like to render and to limit the number of rows to pull.
Full demo with source code
We are very excited for this first release but of course we are just getting started. Here are few more things brewing in our incubator for the upcoming releases
Override trace configuration
In the 4.20 release, you can execute traces by referencing a persisted named trace configuration global Id. In the coming releases you will be able read and override existing named trace configurations as well as build your own to pass into the trace. This will allow for example the ability to modify a named trace configuration that only returns elements to instead return aggregated geometries without the need to create a new named trace configuration.
Query Network Topology Moments
Additional functionality to read the state of the network topology, such as when it was last validated, when the last schema change was applied and more.
Rule-based Editing, Validate, Subnetwork Management
The ability to run utility network functions such as validate network topology and update subnetwork to maintain network consistency while also exposing network rules for use to derive editing snapping.
Here are few links that will help you get started.