Modify / Delete: no

Justification:

•It cannot be discerned which changes originate from VertiGIS and which originate from customers. Therefore, they also cannot be updated.  

•Attribute domains can be used for network attributes. Any adjustment would jeopardize the functioning of the defined trace configurations and subnetworks.

Exception:  

•Content from Esri domain for DetailLifeCycleStatus. Please note that the attribute rule is tested for the calculation of the NET_MainLifeCycleStatus based on DetailLifeCycleStatus and may be disabled in favor of a custom attribute rule. We recommend adjusting the choice list in the attribute form configuration in the VertiGIS Networks web editor instead of the attribute domain in the database.

 

Create: yes.  

Used to define choice lists. Multilingual capability is not supported by Esri. Subsequent expansion of the values requires a schema lock on the database.

The domain attribute must be assigned to all AssetGroups (subtype behavior). In other words, the attribute domain of an attribute must be defined individually for each AssetGroup.

When defining an attribute domain, the split-and-merge policy must also be defined. You can find more information about this in Esri Help.

 

Conventions

•Start prefix with "CUS_".

Suggestion: <Prefix>_<DomainNetworkPrefix>_<AttributeName>{_FeatureClass}{_Assetgroup}

Comments:

•Asset group only provided if the domain is specifically defined for an asset group.

•Provide feature classes only if you have to differentiate between devices, junctions, lines, etc.

•DomainNetworkPrefix: See table in Section 2.8.