Versioning considerations for the parcel fabric feature adjustment
This topic applies to ArcEditor and ArcInfo only.
The parcel fabric supports editing and feature adjustment on a versioned ArcSDE geodatabase. Parcel fabric editing is supported on one version level below the default version. If you are working in manual mode using fabric jobs, multiple, overlapping fabric jobs can exist on both the default version and the child version of the database.
Running fabric least-squares adjustments on versioned geodatabase
Fabric parcels are always locked when edited on a versioned ArcSDE geodatabase and cannot be simultaneously edited in the same version or another version. Parcels can, however, be simultaneously adjusted by least squares on the same version or another version.
When overlapping fabric least-squares adjustments are run on the same set of parcels on different versions, the parcel point coordinates will receive adjustments from the last version to post to the default version. Coordinates in the overlapping area will not receive adjustments from both least-squares adjustments run on the area. Similarly, on the same version, coordinates in the overlapping area will receive adjustments from the most recent adjustment run on the area.
When reconciling versions with a parcel fabric, reconciliation will always occur in favor of the child version when dealing with changes to the parcel fabric. For example, a least-squares adjustment is run on version A. Version A is reconciled without conflicts and is posted to the default version. An overlapping least-squares adjustment is run on version B. When version B is reconciled, adjustment conflicts are automatically resolved in favor of version B (last version to post to default). All other conflicts, such as attribute edits, are resolved manually through interactive conflict resolution.
Conflicts are never detected on parcel geometry edits because parcel geometry is always locked across versions. However, parcel conflicts can be detected on the editable attributes of a parcel and any attributes that you have added to the parcels table.
Conflicts detected in a parcel fabric are defined by row, not by attribute.
Adjustment vectors and overlapping least-squares adjustments
Adjustment vectors are generated between the old and new coordinates of parcel points that have been adjusted with least squares. If versions are posted to default that have fabric least-squares adjustments, overlapping sets of vectors are posted for those parcel points.
In areas with overlapping least-squares adjustments, the adjustments from the most recent version to post to default persist. Similarly, only those adjustment vectors from the most recent version to post to default are maintained. When there are overlapping least-squares adjustments on the same version, adjustment vectors from the most recent least-squares adjustment are preserved.
For example, a least-squares adjustment is run on a set of parcels on version 1. A feature adjustment is then run on associated features on the version. On version 2, a least-squares adjustment is run on a set of parcels that partially overlap an adjustment area in version 1. A feature adjustment is run on associated features on version 2. Version 1 reconciles and posts to the default version. Version 2 reconciles where conflicting coordinate adjustments in the overlapping area are resolved in favor of the child version, which is version 2. Conflicting adjustment vectors are also resolved in favor of the child version, which is version 2. Since associated features in the overlapping area on the default version have already been adjusted with adjustment vectors posted from version 1, a correction vector needs to be generated to move associated features to the adjusted location resulting from vectors posted from version 2.
Associating feature classes on a versioned ArcSDE geodatabase
For a feature class to participate in the parcel fabric feature adjustment, the feature class needs to be associated to the parcel fabric. In ArcSDE, feature classes can only be associated on the default version. Existing child versions need to be reconciled to pick up any new feature classes that have been associated with the parcel fabric.