Please enable JavaScript to view this site.

Version:

Navigation: VertiGIS Network Datamodel > Additional Model Extensions (Non-UN-Specific)

Tables or Feature Classes

Prev Top Next More

VertiGIS uses the “Networks” dataset name and the “Utility Network” network name for the utility-network feature classes of its data models. For non-Utility-Network objects, VertiGIS uses one dataset per utility, named according to the domain prefix: WAT, GAS, ELE, etc. VertiGIS uses the “DIV” dataset name for feature classes that do not depend on the utility.

Modify / Delete: no

Create: additional feature classes or tables should not be created in the “Networks” UN dataset. This makes the model clearer and makes maintenance easier. Naming convention:

“CUS_” prefix is used

Feature classes can, but do not have to, be present in a dataset. However, we suggest that feature classes are maintained in a utility-specific dataset so that it is always clear which new tables and feature classes belong to which utility for assignability. It can help with the overview. The same coordinate system is also used for feature classes of a dataset.

New feature-linked annotation classes should exist in the same dataset as the feature they label. This is to ensure that no problems or discrepancies arise when an asset package is exported, when the versioning and the editor tracking are changed, or when access rights are defined.

Examples:

The CUS_Photopoint feature class is added to a CUS_DIV dataset, which is used across all utilities in the data model.  

The CUS_WaterSupplyOrg_ table is added to the WAT dataset of the VertiGIS standard model.

© 2025 VertiGIS. All Rights Reserved. | Privacy Center | Imprint
Documentation Version 1.4 (c42ba42e)