Display a utility network

You can display and share a complete using a or . You should include at most one for every in the utility network.

You can also create a map programmatically, making use of (known as subtype group layers in and in the web map). Subtype feature layers allow you to set symbology and other properties on a per-subtype basis. Utility networks make extensive use of subtypes (referred to as within a utility network). For example, a device feature table from an electric utility network would include subtypes for fuses, switches, transformers, and other kinds of equipment. For more information, see the Display subtype feature layer sample.

You can use display filters to show and hide inside containers, replicating the functionality available in ArcGIS Pro to show or hide containment association content. You can also use display filters to ensure that critical network features are returned in a result even if they are removed from the view to simplify the display. For more information, see display filters in feature layers.

Access a utility network

Utility networks are implemented as network controller datasets. These datasets contain a network's along with the network's domains, sources, , assets, , rules, and . A utility network is accessible from a geodatabase or a .

You can display and share a complete utility network with a user via a if the map includes one for every .

Diagram of objects loaded when loading a utility network with a map with layers for all network sources.

A UtilityNetwork object in Native Maps SDKs can be created from an online or an source.

These sources provide access to the topological network in the utility network. For example, you can provide a map that contains a subset of the for a specific workflow; any tracing is performed using the full topological network provided by the . To add additional utility network layers, you can create them from the individual as required. You can also access a utility network and run a completely without a map, just provide the URL when you create the utility network or load a utility network from a .

Utility Network version 2 and later is supported. This is provided from 2.2 and later. For details see utility network upgrade history.

Access a utility network from an online source

Online sources include a URL to a or a feature service portal . Maps from a portal authored in version 2.6 or higher may also include utility networks.

When using either a URL to a feature service or a portal as source, create and load a service geodatabase with that are used to create the layers on the map. Then create a utility network with the same source and map.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
        let geodatabase = ServiceGeodatabase(url: featureServiceURL)
        try await geodatabase.load()
        let map = Map(basemapStyle: .arcGISStreetsNight)

        guard let featureTable = geodatabase.table(withLayerID: 0) else { return }
        let featureLayer = FeatureLayer(featureTable: featureTable)
        map.addOperationalLayer(featureLayer)
        let utilityNetwork = UtilityNetwork(url: featureServiceURL, map: map)

When using a web map portal URL as source, get the utility network from a loaded map.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
        let map = Map(url: webmapURL)
        try await map?.load()
        var utilityNetwork: UtilityNetwork?
        if let utilityNetworksCount = map?.utilityNetworks.count,
           utilityNetworksCount > 0 {
           utilityNetwork = map?.utilityNetworks.first
        }

Branch-versioning

When a utility network is based on a ServiceGeodatabase that points to an (version 10.6 or higher) with branch versioning enabled, you can view, edit, and perform a trace on specific versions. Read more about Branch versioning in the ArcGIS Pro documentation and see the Use branch versioned data topic in this guide for more information.

A service can be created in a persistent or transient session. Using a web map or creating a service without a session type by default creates a service geodatabase in a transient session. A service geodatabase in a persistent session acquires a shared lock from the server during load which may be upgraded to an exclusive lock during an edit to allow multiple simultaneous viewers or a single editor. A service geodatabase in a transient session will not hold a lock to allow concurrent viewers and editors.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
        let serviceGeodatabase = ServiceGeodatabase(url: featureServiceURL, sessionType: .persistent)

To create and switch to the new version ...

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
        let versionParameters = ServiceVersionParameters()
        versionParameters.access = .private
        versionParameters.name = "MyVersionName"
        let versionInfo = try await utilityNetwork?.serviceGeodatabase?.makeVersion(parameters: versionParameters)
        guard let versionName = versionInfo?.name else { return }
        try await utilityNetwork?.serviceGeodatabase?.switchToVersion(named: versionName)

To get versions accessible to the logged-in user and switch to a specific version ...

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
        let versionInfos = try await utilityNetwork?.serviceGeodatabase?.versions
        if let foundVersionInfo = versionInfos?.first(where: { $0.name == "userName.MyVersionName" }) {
            try await utilityNetwork?.serviceGeodatabase?.switchToVersion(named: foundVersionInfo.name)
        }

Access a utility network from an offline source

sources include path to a file with a *.geodatabase extension or a web map containing a UtilityNetwork that has been taken offline.

A mobile geodatabase source can be one of the following:

  • a stand-alone that is exported from 2.7 or higher

  • a sync-enabled mobile geodatabase that is generated from Feature Service 10.9 or higher using a GeodatabaseSyncTask or OfflineMapSyncTask.

When using a mobile geodatabase, create and load a whose are used to create the and utility networks on the map.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
        let geodatabase = Geodatabase(fileURL: pathToGeodatabase)
        let map = Map(basemapStyle: .arcGISStreetsNight)
        guard let featureTable = geodatabase.featureTable(withServiceLayerID: 0) else { return }
        let featureLayer = FeatureLayer(featureTable: featureTable)
        map.addOperationalLayer(featureLayer)
        if geodatabase.utilityNetworks.count > 0 {
            let utilityNetwork = geodatabase.utilityNetworks.first!
            map.addUtilityNetwork(utilityNetwork)

        }

Load the utility network

The utility network follows the pattern described in Loading resources asynchronously.

Loading the utility network loads the entire utility network schema (information about the datasets that participate in the network). Once loaded, your app can navigate this network schema to discover the it contains and any further details about the network. The utility network's definition includes the capabilities supported by the utility network object, such as whether tracing and/or querying are supported.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
            try await utilityNetwork.load()

            if let doesSupportTrace = utilityNetwork.definition?.capabilities.supportsTrace,
               doesSupportTrace {
                traceResults = try await utilityNetwork.trace(using: traceParameters)
            }
            if let doesSupportQueryAssociations = utilityNetwork.definition?.capabilities.supportsQueryAssociations,
               doesSupportQueryAssociations {
                associations = try await utilityNetwork.associations(for: element)
            }

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.

You can no longer sign into this site. Go to your ArcGIS portal or the ArcGIS Location Platform dashboard to perform management tasks.

Your ArcGIS portal

Create, manage, and access API keys and OAuth 2.0 developer credentials, hosted layers, and data services.

Your ArcGIS Location Platform dashboard

Manage billing, monitor service usage, and access additional resources.

Learn more about these changes in the What's new in Esri Developers June 2024 blog post.

Close