Display a utility network

You can display and share a complete utility network using a web map or mobile geodatabase. You should include at most one feature layer for every feature table in the utility network.

You can also create a map programmatically, making use of subtype feature layers (known as subtype group layers in ArcGIS Pro and in the web map). Subtype feature layers allow you to set symbology and other layer properties on a per-subtype basis. Utility networks make extensive use of subtypes (referred to as asset groups 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 features 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 trace 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 feature tables along with the network's domains, sources, tiers, assets, terminals, rules, and associations. A utility network is accessible from a feature service geodatabase or a mobile geodatabase.

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

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

A UtilityNetwork object in ArcGIS Maps SDK can be created from an online or an offline 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 feature layers for a specific workflow; any tracing is performed using the full topological network provided by the feature service. To add additional utility network layers, you can create them from the individual network sources as required. You can also access a utility network and run a trace completely without a map, just provide the feature service URL when you create the utility network or load a utility network from a mobile geodatabase.

Utility Network version 2 and later is supported. This is provided from ArcGIS Pro 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 feature service or a feature service portal item. Maps from a web map portal item authored in ArcGIS Pro version 2.6 or higher may also include utility networks.

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

Branch-versioning

When a utility network is based on a ServiceGeodatabase that points to an ArcGIS Enterprise Feature Service (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 geodatabase can be created in a persistent or transient session. Using a web map or creating a service geodatabase 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.

Access a utility network from an offline source

Offline sources include path to a mobile geodatabase 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 mobile geodatabase that is exported from ArcGIS Pro 2.7 or higher

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

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

Load the utility network

The utility network follows the loadable 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 domain networks 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 associations are supported.

Use dark colors for code blocksCopy
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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
        utilityNetwork.load().getOrElse { error ->
            return showError("Error loading utility network: ${error.message}")
        }
        Log.i(localClassName, "The utility network schema version is ${utilityNetwork.definition?.schemaVersion}")

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