Load attributes, plans and line points

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.

Additional steps need to be taken when loading attributes, plan data and line points:

Loading attribute fields

There are three types of attribute fields in the parcel fabric:

• Geometry and System attribute fields are read-only and are system managed, for example the Shape, ShpStdErrE, and ShpStfErrM attribute fields.
• Private attribute fields cannot be changed in the Attributes table or in the Attributes window. These attributes are only changed in the parcel editing environment, for example entering a bearing in the Bearing field on the Lines grid after opening a parcel.
• Public attribute fields are available for editing in the in the Attributes table and in the Attributes window, for example Name, StatedArea and Accuracy. Fields that are added when you enable an information model, such as the LGIM, are also public attribute fields.

Learn more about editing attributes in the parcel fabric sublayers

Note:

When migrating attribute fields to the parcel fabric, be aware that many system attribute fields on the parcel fabric tables store common parcel maintenance attributes such as parcel PINS and area. If you maintain attribute fields that are represented by the parcel fabric system fields, you should change the names and types of your attribute fields so that they can be migrated to the correct parcel fabric system fields.

If you are loading parcel data to the parcel fabric Local Government Information Model, attribute field mapping is done in the staging environment.

The parcel fabric Parcels table uses the following system attribute fields:

Attribute field name	Field type	Migrating parcel polygon attributes
Name	String	Fields named Name, PINParcelName, LOT, or APN are migrated to the Name attribute field.
StatedArea	String	Fields named Area or StatedArea are migrated to the StatedArea attribute field.
Accuracy	Long	Fields named Accuracy or AccuracyCat are migrated to the Accuracy attribute field.
Type	Long	Fields named Type are migrated to the Type attribute field.
Historical	Long	Fields named Historic are migrated to the Historical attribute field. Set to true if the parcel is historic.
LegalStartDate	Date	Fields named LegalStartDate or LegalStart are migrated to the LegalStartDate attribute field.
LegalEndDate	Date	Fields named LegalEndDate or LegalEnd are migrated to the LegalEndDate attribute field.

Note:

In a parcel fabric enabled with the Local Government Information Model, some parcel fabric attributes use aliases. For example, the Name attribute uses an alias named Parcel Identification Number on the Tax Parcels layer and uses an alias named Lot or Unit Number on the Lots and Units layer.

If any of the following fields are missing on your source parcel polygons, corresponding fields on the parcel fabric parcels table will have the following values:

• No PIN, ParcelName, LOT, or APN field: parcel is given the name of the polygon feature class suffixed by _1, where 1 is incremented for each parcel, that is _1, _2, _3, and so on.
• No Area field: StatedArea is populated with the area of the polygon shape geometry, provided that Compute Area for New Parcels is chosen on the Load a Topology to a Parcel Fabric dialog box.
• No PlanName field: Parcels are migrated to the default <map> plan.
• No 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.

  If parcels are migrated to the default <map> plan, they will inherit the internal, default accuracy category of 4.

• No LegalStart field: LegalStartDate = NULL.
• No LegalEnd field: LegalEndDate = NULL.

The parcel fabric Lines table uses the following system attribute fields:

Attribute field name	Field Type	Migrating parcel line attributes
Category	Long	Fields named Category are migrated to the Category attribute field. Use a Category field to migrate lines that are not boundary lines, for example, connection lines.
Calculated	Long	Fields named Calculated are migrated to the Calculated attribute field. Use a Calculated field to flag lines that have COGO generated from the shape geometry (and not legally correct COGO).
Type	Long	Fields named Type are migrated to the Type attribute field. Note: The line type should match the type of the line's associated parcel.
Accuracy	Long	Fields named Accuracy or AccuracyCat are migrated to the Accuracy attribute field.

The line type should match the type of the line's associated parcel. If you have not populated this field prior to migration, you can populate this field after migration.

If any of the following fields are missing on your source parcel lines, corresponding fields in the parcel fabric lines table will have the following values:

• No Category field: Category = Boundary line (all lines in your parcel fabric will be set to the Boundary line category).
• No Calculated field: Calculated = NULL.
• No AccuracyCat field: Accuracy category = NULL, accuracy category is inherited from the parcel.

  If there is no accuracy defined for the parcel, then an internal, default accuracy category of 4 is used.

Tip:

If you have no COGO attributes on some or all of your source parcel lines, the data migration process will automatically generate COGO attributes for you by inversing the line shapes. If you have a Calculated field on your source parcel lines, you can set the field value to True for all lines with generated COGO attributes. This will help you distinguish between the lines in your parcel fabric that have inversed COGO dimensions and the lines that have COGO dimensions that match the record.

Additional attributes

If you would like to migrate additional attributes fields that do not match the attribute fields of the parcel fabric or of the Local Government Information Model, then you need to create these same attribute fields on the parcel fabric Lines, Parcels and Plans table for your attributes to migrate across successfully. Additional attribute fields are only migrated to the parcel fabric if the same, corresponding attribute fields exist in the parcel fabric tables.

Learn how to add additional attributes to parcel fabric tables

Loading plans

Plans are migrated to the parcel fabric by populating a PlanName field on your source polygons table. Each parcel polygon can have either a NULL PlanName attribute or a plan name string. When the polygons are migrated, an entry for each unique plan name is added to the Plans table in the parcel fabric. If there is a NULL PlanName attribute, the parcel is migrated to the default <Map> plan. If you are loading parcel data to the parcel fabric Local Government Information Model, a PlanName attribute field is already created in the parcel polygon staging feature classes.

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.