Available with Standard or Advanced license.
There are a number of scenarios in which reconciliation can result in new dirty areas that did not exist in the parent (default) or child due to cluster processing during the validation process. In the following example, both versions contain polygons that share edges in a topology. A polygon is split in the child version, and the dirty area is validated.
Splitting a polygon deletes the original feature and replaces it with two new polygon features. When the dirty area is validated, cluster processing introduces new vertices into the shared edges of the adjacent polygons. When the versions are reconciled, all the features that have been modified in the child version—the split polygons and the polygons with new vertices added by cluster processing—are covered by dirty areas.
Note:
In branch versioning, in the following image, Version1 is the default and Version2 is a child of the default.
The following example illustrates why this is necessary. Suppose a new features is created in two versions and the resulting dirty areas are validated, resulting in no errors. In reconciliation, dirty areas must be created so potential errors introduced by merging the changes from the two versions can be discovered. In this example, features added in Version1 and Version2 overlap each other, which is a violation of the must not overlap rule.
