Available with Standard or Advanced license.
Multiple editors can simultaneously edit a feature dataset and its topology.
- Each editor follows a workflow to validate their edited topology and to find and repair errors (or set them as exceptions) for the individual edit version.
- Typically, multiple edit versions are merged into a common version (usually referred to as the default version).
- New topology errors may occur when versions are reconciled and potential conflicts occur, even if each edit version has been validated and is free of errors.
- To manage such errors, versioned topologies have special error handling and conflict detection rules that influence the reconciliation process.
The following sections describe the results of reconciling dirty areas, errors, exceptions, and potential conflicts. In each case, the results are based on reconciliation in which a parent (default) and child version have both been updated since the child version was created. If the default version is not edited before the child version is reconciled, the results of reconciliation will be the contents of the child version. In each example, Version2 is created as a child of Version1 (default). Both versions are then edited in the manner described in the example, and then Version2 is reconciled against Version1 (default). For the illustrations in the following examples, use the following as a legend:
Note:
For branch versioning, in the following examples, Version1 is the default and Version2 is a child of the default.Example 1
- Any dirty areas present in the default or child version that did not exist before the child version was created remain dirty as a result of reconciling.
- Any dirty area that was present in the default version and validated in the child version becomes dirty as a result of reconciling.
- Any dirty area introduced and validated in the default version, whether or not it was present in the child version, remains validated as a result of reconciling.
As shown above, the original state of the default (no dirty area) is maintained after reconciling. However, other dirty areas may be created as a result of updates performed against the child version.
Examples 2 and 3 below illustrate other scenarios in which any dirty area introduced and validated in the default version remains validated as a result of reconciling.
Example 2
Example 3
Any edits made to topology features in the child version result in a dirty area after reconciling, even if the dirty area resulting from the edit is validated in the child version. This is also the case when the original edit did not result in a dirty area, such as an attribute update. This is illustrated in the examples below.
Note:
In the following example, both Version1 and Version2 have been edited; however, the polygon shape in the example has only been modified in Version2.
Example 4
Example 5
