The following limitations are known in this version:

•Z-values in the coordinate system
The current version of the Network Editor has a known limitation in connection with the processing of 3D data. The Z values of vertices are determined by the Network Editor are not explicitly set and therefore assume the default value of the Esri Feature Service (see: Esri article Configuring default Z values for editable feature services).

It is therefore currently not advisable to process data for which the Z values have been explicitly recorded.

If your data uses a non-zero constant Z value, make sure that the setting in the feature service matches this value. We are working diligently on a solution that will be included in the next version of Network Editor .

•Print:
VertiGIS Studio Printing does not currently support subtype group layers. If a use case involves printing, a web map without a subtype group layer should be used.

•Associations:
For connectivity associations, currently only junction-junction type associations are supported. Junction-edge type associations will follow in a future release.

•Snapping:

▪General - When creating network elements, the rules for the utility network (UN) are loaded for snapping. Unfortunately, it is not yet possible to catch non-network elements at the same time. As a temporary workaround, the rules for the utility network can be turned off and on via a switch during capture, e.g.,when creating a network feature that is to be snapped to a construction point.

▪Creating graphics/markups - Snapping is not yet implemented.

•Editing:

▪Editing versioned data currently requires that exactly one single feature service is referenced in the WebMap.

▪Currently offers Network Editor no support for app templates that contain multiple map elements.