About the parcel fabric tables

A parcel fabric dataset is composed of related feature classes and tables that define and store information about parcels. Each parcel fabric feature class and table contains a set of system attribute fields. Some system attribute fields are editable and some are entirely system managed.

The parcel fabric dataset has the following feature classes and tables:

• Control feature class
• LinePoints feature class
• Points feature class
• Lines feature class
• Parcels feature class
• Plans table
• Accuracy table
• Jobs table
• Adjustments table
• Vectors table

Control feature class

The Control feature class stores and displays parcel fabric control points. The Control feature class is part of the parcel fabric group layer. Control points can be associated with parcel points or connected to parcel points using connection lines. Parcels can be adjusted to control points in a parcel fabric least-squares adjustment. The Control feature class is internally related to the Points feature class.

The Control feature class contains the following system fields:

Attribute field	Description	Editable in attribute table/window
X	X-coordinate. Held fixed in the parcel fabric adjustment.	No. Editable in the Control dialog box.
Y	Y-coordinate. Held fixed in the parcel fabric adjustment.	No. Editable in the Control dialog box.
Z	Z-coordinate. Held fixed in the parcel fabric adjustment.	No. Editable in the Control dialog box.
Name	Control point name. Automatically populated if no name is specified.	No. Editable in the Control dialog box.
PointID	Associated parcel fabric point. (A control point needs to be connected to a fabric point to be used in the fabric adjustment.)	No. Editable in the Control dialog box.
AccuracyXY	Horizontal positional accuracy; metadata only.	Yes.
AccuracyZ	Vertical accuracy; metadata only.	Yes.
Survey Date	Date the control point was surveyed or established.	Yes.
Active	True if control point is active and can be used in a fabric adjustment.	Yes.
Type	Used for adding subtypes.	Yes.

LinePoints feature class

The LinePoints feature class stores and displays line points. The LinePoints feature class is part of the parcel fabric group layer. Line points are added to parcel points that lie on the boundary lines of adjacent parcels. A line point allows a parcel point to lie on an adjacent boundary line without splitting the boundary line. Furthermore, a line point constrains the parcel point to lie on the adjacent boundary line and maintains topological integrity. Through the use of line points, parcel lines can correctly represent the legal record, where each adjacent boundary line stores and displays the correct dimension. The LinePoints feature class is internally related to the Points feature class and the Parcels feature class.

The LinePoints feature class contains the following system fields:

Attribute field	Description	Editable in attribute table/window
ParcelID	ID of the parcel containing the line on which the line point sits.	No. System managed.
FromPointID	From-point of the line on which the line point sits.	No. System managed.
ToPointID	To-point of the line on which the line point sits.	No. System managed.
LinePointID	ID of the parcel point that is a line point	No. System managed.
FlexPoint	True if the line point is a flex point. A line point is a flex point if adjacent parcel lines are moved or bent to the line point rather than the line point being moved to the adjacent parcel lines.	Yes.

Points feature class

The Points feature class stores and displays parcel fabric points. The Points feature class is part of the parcel fabric group layer. Parcel points represent parcel corners, curve center points, and end points of connection lines. Points should be common between shared boundaries and should not be duplicated. The Points feature class is internally related to the Lines, LinePoints, and Control feature classes.

The Points feature class contains the following system fields:

Attribute field	Description	Editable in attribute table/window
X	X-coordinate. Populated when parcels are loaded into the parcels fabric and when new parcels are joined to the parcel fabric. Adjusted in a parcel fabric adjustment.	No. System managed
Y	Y-coordinate. Populated when parcels are loaded into the parcels fabric and when new parcels are joined to the parcel fabric. Adjusted in a parcel fabric adjustment.	No. System managed.
Z	Z-coordinate. Can be populated if a point feature class with a Z attribute field is specified for Input Point Features on the Load a Topology to a Parcel Fabric dialog box.	No. System managed.
Type	Used for adding subtypes	Yes.
Category	Point type, for example, center point. Automatically set to 2 when the point is associated with a control point. Metadata only.	Yes.
Name	Name of corresponding control point if there is one.	No.
Historical	Historic point. True if all lines sharing the point are historic.	No. System managed.
SystemStartDate	Date of database transaction that created the point.	No. System managed.
SystemEndDate	Date of database transaction that retired the point.	No. System managed.
LegalStartDate	Date of legal transaction that created the point.	Yes.
LegalEndDate	Date of legal transaction that retired the point.	Yes.
CenterPoint	True if the point is a center point.	No. System managed.
MaxDN	Maximum northing shift resulting from a fabric adjustment	No. System managed.
MaxDE	Maximum easting shift resulting from a fabric adjustment	No. System managed.

Lines feature class

The Lines feature class stores and displays parcel fabric lines. The Lines feature class is part of the parcel fabric group layer. Parcel lines store COGO dimensions, which should ideally or eventually match recorded dimensions on the record of survey or plan. Parcel lines are boundary lines, connection lines, and radial lines. The Lines feature class is internally related to the Points and Parcels feature classes.

The Lines feature class contains the following system fields:

Attribute field	Description	Editable in attribute table/window
Calculated	Set this field to true if dimensions are generated from the line geometry. Use this field to indicate calculated versus legal dimensions. Metadata only.	Yes.
ParcelID	ID of parcel that contains the line.	No. System managed.
Sequence	A number indicating the order in which the line was entered in the parcel traverse.	No. System managed.
FromPointID	ID of the from-point of the line	No. System managed.
ToPointID	ID of the to-point of the line	No. System managed.
Bearing	Direction of the line. If dimensions are empty during loading, the bearing is calculated from line geometry.	No. Edited in the parcel traverse.
Distance	Length of the line. If dimensions are empty during loading, the length is calculated from line geometry.	No. Edited in the parcel traverse.
Type	Used for adding subtypes.	Yes.
Category	Category of the line, for example, connection or radial line	Yes.
Radius	Curve radius. If curve dimensions are empty during loading, the radius is calculated from the curve geometry. The Bearing field is populated with the chord bearing, and the Distance field is populated with the chord length.	No. Edited in the parcel traverse.
ArcLength	Curve arc length. If curve dimensions are empty during loading, only radius, bearing, and distance are generated from curve geometry. Arc length is entered in the parcel traverse.	No. Edited in the parcel traverse.
Delta	Curve delta. If curve dimensions are empty during loading, only radius, bearing, and distance are generated from curve geometry. Delta is entered in the parcel traverse.	No. Edited in the parcel traverse.
CenterPointID	ID of the point that is the center point of the curve	No. System managed.
Historical	True if the line's associated parcel is historic.	No. System managed.
Radial Bearing	Bearing of the curve radius.	No. System managed.
Tangent Bearing	Bearing of the curve tangent line	No. System managed.
Line Parameters	Indicates what parameters were used to enter the line or curve, for example, bearing and distance.	No. System managed.
Accuracy	Accuracy category of the line.	Yes.
ComputedMinusObserved	Difference between the line shape length (computed) and the line Distance attribute multiplied by the ground-to-grid correction (observed). For curves, the chord length is used.	No. System managed.
Internal Angle	The internal angle between traverse lines. Populated when a traverse is defined using internal angles.	No. Edited in the parcel traverse.
Reference Object	The to-point of a backsight line. Used when adding a connection line to a parcel traverse using internal angles.	No. Edited in the parcel traverse.
IsMajor	Used for storing and displaying curves greater than 180 degrees.	No. System managed.
Hide	True if the line dimension is a duplicate of overlapping line. (Duplicate label will be hidden.)	Yes.
SystemStartDate	Date of database transaction that created the line.	No. System managed.
SystemEndDate	Date of database transaction that retired the line.	No. System managed.
LegalStartDate	Date of legal transaction that created the line.	Yes.
LegalEndDate	Date of legal transaction that retired the line.	Yes.
DensifyType	Used for storing natural boundaries.	No. System managed.

ComputedMinusObserved field

The ComputedMinusObserved field stores an internally calculated value. The value is the difference between the line shape length (computed) and the line Distance attribute multiplied by the ground-to-grid correction (observed). The formula used to calculate the ComputedMinusObserved value is [Shape_Length] - ([Distance] * scale factor), where scale factor is the ground-to-grid correction obtained from the parcel fabric projection. For curves, the chord length is used. The ground-to-grid correction value is reported by the Point Report tool. Use the Point Report tool on the Parcel Editor toolbar to generate a report for one point. Click either the start or end point of the line to see the ground-to-grid scale for the point.

Parcels feature class

The Parcels feature class stores and displays parcel polygons. The Parcels feature class is part of the parcel fabric group layer. Parcel polygons store information about the parcel, such as the parcel identification number and the parcel area. Parcel polygons can be multipart, singlepart, or donut/island parcels. The Parcels feature class is internally related to the Points, LinePoints, and Lines feature classes.

The Parcels feature class contains the following system fields:

Attribute field	Description	Editable in attribute table/window
Joined	True if the parcel is joined to the fabric.	No. System managed.
PlanID	Object ID of the parcel's associated plan.	Yes. Use this field to assign plans to parcels.
Name	Parcel name or parcel identification number (PIN).	Yes.
Type	Used for adding subtypes.	Yes.
Stated Area	Legal area of the parcel. Automatically calculated if the field is empty and if the misclose ratio is less than 1:500.	Yes. Once you populate the field with an area, the value is never overwritten.
Compiled	Set this field to True if the parcel is compiled from other parcels, for example, a merge or subdivision. If the parcel accuracy category is left null, a default accuracy of 3 will be used in the fabric least-squares adjustment.	Yes.
Historical	True if the parcel is historic.	No. Right-click a parcel and click Historic to flag a parcel as historic.
SystemStartDate	Date of the database transaction that created the polygon.	No. System managed.
SystemEndDate	Date of the database transaction that retired the polygon.	No. System managed.
LegalStartDate	Date of the legal transaction that created the parcel; should match the plan date.	Yes.
LegalEndDate	Date of the legal transaction that retired the parcel; should correspond to the plan date of the replacing parcels.	Yes.
GroupID	If the parcel is part of an unjoined group, this field is populated with the unjoined group ID.	No. System managed.
Accuracy	Accuracy category of the parcel.	Yes.
Rotation	Angle the parcel is rotated to be joined to the parcel fabric layer.	No. System managed.
Scale	Amount the parcel is scaled to be joined to the parcel fabric layer.	No. System managed.
Unclosed	True if the parcel is unclosed. Unclosed parcels allow features such as street centerlines to exist independently in the parcel fabric and not have to be dependent on another parcel.	No. Edit this field on the Properties tab on the Parcel Details dialog box.
MiscloseRatio	Ratio of the parcel's misclose distance to the parcel perimeter.	No. System managed.
Misclose Bearing	Bearing of the line between the start point and end point of the parcel.	No. System managed.
Construction	True if the parcel is a construction. A construction parcel is unjoined and composed of construction lines.	No. System managed.
ShapeStdErrorE	Easterly shift or distortion in parcel shape after the parcel fabric adjustment.	No. System managed.
ShapeStdErrorN	Northerly shift or distortion in parcel shape after the parcel fabric adjustment.	No. System managed.
BacksightBearing	Populated when a parcel is traversed using internal angles.	No. The backsight bearing is defined when entering the parcel traverse.
ConstructionData	Blob field. Stores information for an unjoined parcel or construction parcel.	No. System managed.

Plans table

The Plans table stores information about a parcel's record of survey, plat, or plan. Parcels are created and edited in response to changes in the plan or legal record. In the parcel fabric, parcels are contained by plans, and the plan defines the record format, units, and accuracy.

The plans table is available under the parcel fabric dataset in the Catalog window. The Plans table is internally related to the Parcels feature class.

The Plans table contains the following system fields:

Attribute field	Description	Editable in attribute table/window
Name	Plan name.	Yes.
Description	Plan description. Can include a metes and bounds description.	Yes.
Surveyor	Name of the surveyor on the plan. Metadata only.	Yes.
Company	Name of the survey company. Metadata only.	Yes.
SurveyDate	Date of the survey. Usually stated on the plan.	Yes.
LegalDate	Date the plan was recorded. If a LegalDate attribute is specified, the date is copied to the LegalStartDate attribute of all the new parcels created in this plan.	Yes.
AngleUnits	Angle units used on the plan, for example, degrees-minutes-seconds.	Yes.
AreaUnits	Area units used on the plan.	Yes.
DistanceUnits	Distance units used on the plan.	Yes.
DirectionFormat	Direction or angle type of the dimensions used on the plan, for example, Quadrant Bearing.	Yes.
LineParameters	Indicates what parameters are used to enter lines or curves, for example, bearing and distance.	Yes.
DistanceAtGround	Set this field to True if record distances are at ground. Metadata only.	Yes.
CombinedGridFactor	Scale factor used if distances are at grid. Metadata only.	Yes.
TrueMidBrg	Set this field to True if astronomic azimuths are used. Metadata only.	Yes.
Accuracy	Accuracy category of the plan. All parcels will inherit this accuracy unless the accuracy category is overridden on the parcel.	Yes.
InternalAngles	True if the plan uses internal angles.	Yes.
SystemStartDate	Date of the database transaction that created the plan.	No. System managed.

Accuracy table

The Accuracy table stores the accuracy categories used by the parcel fabric. Accuracy categories are assigned to plans, parcels, and lines and act as weights in the parcel fabric least-squares adjustment. Accuracy categories are classified by date, with 1 being the highest accuracy and assigned to the most recently surveyed or most reliable data. The lowest accuracy is 6 and is assigned to older or unreliable dimensions.

Learn more about accuracy categories

To add the accuracy table to the Table Of Contents window, use the Make Parcel Fabric Table View geoprocessing tool located under System Toolboxes > Parcel Fabric Tools > Layers and Table Views.

The Accuracy table contains the following system fields:

Attribute field	Description	Editable in attribute table/window
BrgSD	Standard deviation of bearings in seconds.	Yes.
DistSD	Standard deviation of distance (m/ft).	Yes.
PPM	Parts per million.	Yes.
Description	Level of the accuracy. Classified by date.	Yes.

Jobs table

The Jobs table stores and tracks edits to the parcel fabric. Each time a parcel is edited, a job is created and saved with the date, time, and editor. Jobs on a parcel fabric can be viewed by opening the Job Book dialog box from the Parcel Editor menu.

The Jobs table contains the following system fields:

Attribute field	Description	Editable in attribute table/window
Name	Job name. System generated.	No. Right-click the job in the Job Book dialog box to edit the name.
Description	Describes the type of edit. System generated	No. Right-click the job in the Job Book dialog box to edit the description.
Locked	True if there are locked parcels in the job. Parcels are locked when edited on versions.	No. System managed.
CreateDate	Date the job was created in the database.	No. System managed.
ModifiedDate	Date the job was last edited.	No. System managed.
CommitDate	Date the version that contained the job was posted to the database.	No. System managed.
Owner	Name of the editor who created the job.	No. Right-click the job in the Job Book dialog box to edit the owner name.
Status	Status of the job. Active or committed.	No. Right-click the job in the Job Book dialog box and click Properties to view the job status.
SystemState	System managed job state.	No.
Version	The name of the version on which the job was created.	No.
LockMachine	The name of the machine currently editing the job on a version.	No.
LockPID	Lock ID	No.
CommittedObj	A blob field storing information about a committed job.	No.

Adjustments table

The Adjustments table stores information about groups of adjustment vectors. Adjustment vectors are generated when points are moved in the parcel fabric. Points are most commonly moved by a parcel fabric adjustment. Each time a parcel fabric adjustment is run, a group of adjustment vectors is generated for all the adjusted points, and the group is flagged with a date, time, and adjustment level. The parcel fabric feature adjustment uses adjustment vectors to adjust and realign features to the parcel fabric.

The Adjustments table contains the following system fields:

Attribute field	Description	Editable in attribute table/window
AdjustmentDate	The date the adjustment vectors were generated.	No. System managed.
VectorCount	The number of vectors generated from this adjustment.	No. System managed.
JobID	The ID of the job that contains the adjustment.	No. System managed.
AdjLevel	The adjustment level. The sequential order of this adjustment relative to other adjustments.	No. System managed.

Vectors table

The Vectors table stores the adjustment vectors. Adjustment vectors are generated in groups at different points in time when points are moved or adjusted in the parcel fabric. Each group of adjustment vectors has an adjustment level, which is the sequential order of this vector group relative to other groups.

The Vectors table contains the following system fields:

Attribute field	Description	Editable in attribute table/window
FromX	The X-coordinate of the from point of the vector.	No.
FromY	The Y-coordinate of the from point of the vector.	No.
ToX	The X-coordinate of the to point of the vector.	No.
ToY	The Y-coordinate of the to point of the vector.	No.
PointID	The object ID of the point that was adjusted by the vector.	No.
AdjLevel	The adjustment level. The sequential order of this adjustment relative to other adjustments.	No.