Dirty areas are created to flag the location of edits made to the geometry of network features and network attributes, or to display errors. They serve as an indicator that a change to the network has taken place that is not reflected in the network topology. Dirty areas are cleared when the network topology is validated, as long as no error exists within the validation extent.
When the network topology is enabled, dirty areas are created to track edits. This can include creation of features, modifying fields associated with network attributes, establishing or modifying associations, and so on. The dirty area signifies that a change was made to the utility network but has not been updated in the network topology. Validate is used to update the network topology and clear dirty areas. Edits that are not reflected in the network topology are not considered with network analytic operations, such as tracing or network diagrams. When a network topology is disabled, a single dirty area covering the network is created. Dirty areas also remain for any features with errors. When the network topology is enabled again, all outstanding edits are validated.
Dirty areas track the extent of the feature that is edited, the type of edit, the global ID of the feature, and the editor who performed the operation. If a feature's geometry is modified, two dirty areas are generated for the single feature. One represents the envelope of the feature's previous geometry, and the other represents the feature's new geometry.
Operations that create dirty areas
Modifications to the following create dirty areas:
- Geometry
- Asset group or asset type fields
- Fields that are defined as network attributes
- Associations
- Terminal configuration information
Dirty areas are created when errors are discovered during the following processes:
- Enable network topology
- Validate network topology
- Update subnetwork
View and manage dirty areas
Dirty areas can be accessed as a sublayer of the utility network and can be symbolized using core symbology tools. The visualization of dirty areas can be turned on and off like any other layer. For example, if you are making edits to your network and you find the dirty areas are visually distracting, you can turn off the layer. The dirty areas are still created, but you will not see them on the map. You can symbolize the dirty areas based on attributes in the dirty areas layer. For example, editor tracking fields can help to display dirty areas in which a certain editor performed work, or when the edit occurred.
With Utility Network version 4 and later, dirty areas are also used to identify and work with errors discovered for network features. Dirty areas are used to represent errors that are generated by the system when a feature in the utility network is in violation of established rules and restrictions. Upon the creation of an error, a dirty area is created that encompasses the feature's geometry.
The dirty areas sublayer is symbolized using the Status field to indicate how it was created:
- Disabled
- Dirty
- Error
- Dirty and error
- Subnetwork error
The Status attribute field uses bitwise encoding to represent the operation that created the dirty area. For example, a deleted feature is represented by bit 1 and is displayed with a status of 2 (2^1 = 2). These values are summated if multiple operations led to the creation of the dirty area. A Status Description field is displayed in the pop-up expression to provide additional information about the operation that created the dirty area.
Validating the network topology maintains consistency between what you see on the map and what is present in the network topology. Analytic operations rely on the network topology and thus may return unexpected results if dirty areas exist. For example, if the path of a trace traverses a dirty area, the results are not guaranteed to be consistent with what you see on the map. The Validate Consistency option in the Trace tool is important to use to ensure trace results do not include results that intersect dirty areas.
When a version is reconciled with the default version, dirty areas that exist in the named version will remain and dirty areas are created from edits generated by the reconcile process. Likewise, when edits from a named version are posted to the default version, dirty areas are created for edits that were made in the named version. This includes edits that were previously validated in the named version.
Dirty areas in Utility Network version 3 or earlier
With Utility Network version 3 and earlier, dirty areas are only used to represent edits that are not reflected in the network topology. The UpdateType is an attribute in the dirty areas table that can be used to symbolize the dirty area by the type of edit.
Dive-in:
The type of dirty area is represented by the UpdateType field in the dirty areas attribute table. This field is assigned a system-provided coded value domain to classify how the dirty area was generated. Values for the coded value domain include Insert, Update, Delete, and Error.
| Update type | Dirty area type |
|---|---|
0 | Insert |
1 | Update |
2 | Delete |
3 | Error |