The parcel fabric provides a comprehensive framework for managing, editing, and sharing parcel data in both a multiuser (ArcGIS Enterprise) and single-user environment. In a multiuser environment, the parcel fabric can be edited and maintained using a services-based architecture. A services-based architecture allows you to share the parcel fabric across all platforms (desktop, mobile, and web) and different workflows can be enabled on different clients in the field and in the office.
In a single-user editing environment, the parcel fabric is administered and edited on a file geodatabase or mobile geodatabase.
A parcel fabric stores a dataset of connected parcels or parcel network. Parcels are composed of polygon features, line features, and point features. Parcel polygons are defined by lines that store COGO dimensions from the recorded, legal document. Parcels are added to the parcel fabric as parcel types. A parcel type is composed of a polygon and line feature class and is defined by your organization. For example, your organization may manage both ownership/tax parcels and subdivision parcels. You can add as many parcel types as necessary for your organization.
When a parcel fabric is created, a geodatabase topology is also created. The parcel fabric uses a set of predefined geodatabase topology rules and attribute rules to define parcels and model parcel behavior. Geodatabase topology rules define the spatial relationships between parcel features, and attribute rules define behavior that is specific to parcel features.
The parcel fabric topology is validated using the predefined set of geodatabase topology rules and attribute rules. You can define additional topology rules and attribute rules to enforce data quality standards in your organization.
Use record-driven workflows
The parcel fabric is a record-driven system. The parcel fabric organizes parcel data based on the form in which it was originally recorded. Parcel data is recorded on legal records such as plans, plats, deeds, and records of survey. Parcels are created and edited in response to changes in the legal record, and parcels are edited using record-driven workflows in the parcel fabric.
Configure a flexible data model
The parcel fabric stores parcels as separate parcel types. Each parcel type can be modeled differently and have its own schema and rules.
In addition, you can extend the parcel fabric information model in the following ways:
- Add related tables and additional attribute fields to parcel fabric feature classes.
- Configure layers and maps.
- Use groups in Portal for ArcGIS to manage access privileges.
- Configure workflows using tasks.
- Work in both two-dimensions (2D) and three-dimensions (3D).
Administrators can define behaviors for parcel types by applying different topology rules and attribute rules to the parcel types. For example, overlapping parcels can be configured as an error for certain parcel types but allowed for other parcel types. The parcel fabric topology can be validated using these rules to assess data quality. Topology rule errors are visualized on the map as error features.
Branch versioning enables enhanced editor tracking, in which every edit is tracked by date and time including which users delete features in a version. In addition, edits can be validated using topology rules and attribute rules.
Least squares adjustments can be run on parcels to detect mistakes in line dimensions and to compute updated, more accurate coordinates for parcel fabric points.
Track history and parcel lineage
Parent parcels are saved as historic after edits such as splits or merges. In addition, by capturing the legal record that created or retired a parcel, parcel lineage can be tracked in both directions.