To load clean and validated topologies to a parcel fabric, use the Load A Topology To a Parcel Fabric geoprocessing tool located under System Toolboxes > Parcel Fabric Tools > Data Migration in the Catalog window. You can also open the tool by right-clicking a parcel fabric dataset in the Catalog window and clicking Import > Parcels.
Load attribute fields
There are three types of attribute fields in the parcel fabric:
- Geometry and System.
These attribute fields are read-only and system managed, for example, the Shape, ParcelID, and SystemStartDate attribute fields.
- Private.
These attribute fields cannot be edited in the Attributes table or Attributes window. These attributes are edited in the parcel editing environment, for example, entering a bearing in the Bearing field in a parcel traverse.
- Public.
These attribute fields are can be edited in the Attributes table and Attributes window, for example, the Name, StatedArea, and Accuracy attribute fields.
Learn more about parcel fabric attribute fields
Load attributes to the Parcels table
You can load attributes to the following parcel fabric system fields in the Parcels table:
| Attribute field name | Field type | Migrating parcel polygon attributes |
|---|---|---|
Name | String | Attributes in a Name, PIN, ParcelName, LOT, or APN field are loaded to the Name system field. |
StatedArea | String | Attributes in an Area or StatedArea field are loaded to the StatedArea system field. |
Accuracy | Long | Attributes in an Accuracy or AccuracyCat field are loaded to the Accuracy system field. |
Type | Long | Attributes in a Type field are loaded to the Type system field. |
Historical | Long | Attributes in a Historic field are loaded to the Historical system field. Set to true if the parcel is historic. |
LegalStartDate | Date | Attributes in a LegalStartDate or LegalStart field are loaded to the LegalStartDate system field. |
LegalEndDate | Date | Attributes in a LegalEndDate or LegalEnd field are loaded to the LegalEndDate system field. |
If any of the following attribute fields are missing on your source parcel polygons (polygons being loaded), corresponding attribute fields in the parcel fabric Parcels table will have the following values:
| Missing fields in polygons being loaded | Default values in parcel fabric system fields |
|---|---|
MissingPIN, ParcelName, LOT, or APN field | Name field is populated with the name of the polygon feature class and a suffix of _1, where 1 is incremented for each parcel, that is _1, _2, _3, and so on. |
Missing Area field | StatedArea field is populated with the area of the polygon shape geometry if Compute Area for New Parcels is chosen on the Load a Topology to a Parcel Fabric dialog box. |
Missing PlanName field | Parcels are assigned the default <map> plan. |
Missing AccuracyCat field | Accuracy category of parcels is inherited from their associated plans. If no accuracy is defined for a plan, the internal, default accuracy category of 4 is used. |
MissingLegalStart field | LegalStartDate field is not populated. |
Missing LegalEnd field | LegalEndDate field is not populated. |
Load attributes to the Lines table
You can load attributes to the following parcel fabric system fields in the Lines table:
| Attribute field name | Field Type | Migrating parcel line attributes |
|---|---|---|
Category | Long | Attributes in a Category field are loaded to the Category system field. Use a Category field to load lines that are not boundary lines, for example, connection lines. |
Calculated | Long | Attributes in a Calculated field are loaded to the Calculated system field. Use a Calculated field to flag lines that have COGO generated from the shape geometry (and not legally correct COGO). |
Type | Long | Attributes in a Type field are loaded to the Type system field. |
Accuracy | Long | Attributes in an Accuracy or AccuracyCat field are loaded to the Accuracy system field. |
If any of the following attribute fields are missing on your source parcel lines, corresponding attribute fields in the parcel fabric Lines table will have the following values:
| Attribute field name | Default values in parcel fabric system fields |
|---|---|
Missing Category field | Category field is set to Boundary (0). |
Missing Calculated field | Calculated field is not populated |
Missing AccuractCat field | Accuracy category is inherited from the parcel. If no accuracy is defined for a parcel, the internal, default accuracy category of 4 is used. |
Load additional attributes
To load attribute fields that do not correspond to parcel fabric system fields, create the same attribute fields on the parcel fabric tables. Additional attribute fields are loaded to the parcel fabric if the same, corresponding attribute fields exist in the parcel fabric tables. For example, to load attributes in an Ownership field that exists on your source polygons, create the same Ownership field on the parcel fabric Parcels table. You can load additional attributes to the Parcels and Lines tables.
Learn more about adding additional attributes to parcel fabric tables
Load plans
Parcels are loaded and assigned to plans when a PlanName field is added and populated on the source polygons table. Each unique plan name string creates a single plan in the parcel fabric (a new record is added to the Plans table). Add the same plan name string to multiple polygons to assign them to a single plan in the parcel fabric. Additional information for a plan can be added after the data loading process using the PlanName field to join to another table and calculate field values.
If there is no PlanName field or NULL PlanName attributes, parcels are assigned to the default <Map> plan.
Line points
Line points are not detected during the data loading process. You can use the Merge Parcel Courses tool to merge collinear line segments (within a specified tolerance) into a single line. Once lines are merged, any adjacent parcel points sitting on the line become line points.