Parcel fabric attribute rules

Attribute rules are geodatabase rules that can be used to automatically populate attributes, restrict invalid edits during edit operations, and perform quality assurance checks on features. Attribute rules can be used in addition to topology rules, domains, and subtypes to improve data integrity for geodatabase datasets.

Learn more about attribute rules

The parcel fabric uses attribute rules together with geodatabase topology rules to manage data quality. When a parcel fabric is created, the following attribute rules are created on parcel fabric feature classes:

  • The PRESERVE attribute rule
  • The MUST HAVE A RECORD attribute rule.

PRESERVE

The PRESERVE attribute rule is a calculation type attribute rule that contains logic to populate the Preserve field in the Points feature class.

If the Preserve field is set to Yes, the point will not be deleted when its associated parcel or connection line is deleted. The attribute rule sets the Preserve field to Yes if either of the following is true:

  • The point has a fixed shape (the Fixed Shape field is set to Yes).
  • The point has X, Y, or Z attributes that are not null.

To view and configure the attribute rule, right-click the Points layer in the Table Of Contents window, point to Design, and click Attribute Rules.

MUST HAVE A RECORD

The MUST HAVE A RECORD attribute rule is a validation type attribute rule that checks whether a parcel fabric feature is associated to a record. The attribute rule is created for parcel line layers, parcel polygon layers, and the Connection Lines layer.

The MUST HAVE A RECORD attribute rule requires that the CreatedByRecord field on the parcel line layers, parcel polygon layers, and the Connection Lines layer is not empty when attribute rules are evaluated.

Validation type attribute rules are evaluated at a user-specified time using the Error Inspector or the Evaluate Rules geoprocessing tool.

To view and configure the attribute rule, right-click the parcel lines layer, parcel polygon layer, or Connection Lines layer in the Table Of Contents window, point to Design, and click Attribute Rules.

Learn more about evaluating parcel fabric attribute rules

Optional attribute rules

In ArcGIS Pro 2.7, a set of optional attribute rules are available for the parcel fabric. Optional attribute rules are stored in .csv files in the \Resources\AttributeRules\ParcelFabric folder in your ArcGIS Pro installation directory, for example, C:\Program Files\ArcGIS\Pro\Resources\AttributeRules\ParcelFabric\en-US.

Optional attribute rules are available for parcel fabric connection lines, parcel lines, parcel polygons, parcel points, and parcel records.

To import optional attribute rules for a parcel fabric feature layer, right-click the layer in the Contents pane, point to Design, and click Attribute Rules. On the Attribute Rules tab, click the Import Rules tool to import a .csv file of attribute rules. You can also use the Import Attribute Rules geoprocessing tool to import the optional attribute rules.

The subsections below list the optional attribute rules that are available for parcel fabric feature classes.

Connection lines

  • MUST BE LONGER THAN (validation rule)—Connection line must be longer than the specified length.
  • DISTANCE MUST MATCH WITHIN (validation rule)—Line shape length must match the COGO distance within the specified tolerance.
  • DIRECTION MUST MATCH WITHIN (validation rule)—Line shape direction must match the COGO direction and rotation within the specified tolerance (seconds).

Parcel lines

  • MUST BE LONGER THAN (validation rule)—Boundary line must be longer than the specified length.
  • DISTANCE MUST MATCH WITHIN (validation rule)—Line shape length must match the COGO distance within the specified tolerance.
  • DIRECTION MUST MATCH WITHIN (validation rule)—Line shape direction must match the COGO direction and rotation within the specified tolerance (seconds).

Parcel polygons

Note:
Some parcel polygon attribute rules may fail to import if the name of your parcel polygon feature class does not match the hard-coded "Parcels" name in theArcGIS Arcade expression. To modify the expression, open the ParcelPolygons.csv file and in the SCRIPTEXPRESSION field, replace "Parcels" with the name of your parcel polygon feature class, for example "Lots".

  • MUST BE LARGER THAN (validation rule)—Parcel shape area must be larger than the specified area.
  • MUST BE SMALLER THAN (validation rule)—Parcel shape area must be smaller than the specified area.
  • CURRENT MUST NOT OVERLAP (validation rule)—Current parcels must not overlap each other. Current parcels can overlap historic parcels and historic parcels can overlap other historic parcels.
  • NAME MUST BE UNIQUE (validation rule)—Parcel names must be unique for current parcels in the same parcel type.
  • NAME MUST NOT BE EMPTY (validation rule)—Parcel names must be populated and cannot be null.
  • MISCLOSE RATIO MUST BE LESS THAN (validation rule)—Misclose ratio must be less than the specified tolerance.
  • MISCLOSE DISTANCE MUST BE LESS THAN (validation rule)—Misclose distance must be less than the specified tolerance.
  • AREAS MUST MATCH WITHIN (validation rule)—Shape area and stated area cannot differ by more than the specified tolerance.

Parcel points

  • SHAPE IS FIXED (Constraint rule)—Point shape geometry must be fixed and not move.
  • MUST HAVE A RECORD (validation rule)— Point features must be associated with the record that created them.
  • MUST BE IN XY EXTENT (validation rule)—Point's x,y attribute coordinates must lie within the specified minimum bounding rectangle (MBR).
  • MUST BE IN Z EXTENT (validation rule)—Point's z-coordinate must lie within the specified height range.
  • XY MUST MATCH SHAPE WITHIN (validation rule)— Point's x,y attribute coordinates must lie within the specified distance of the point's shape.
  • Z MUST MATCH GEOMETRY WITHIN (validation rule)—Point's z-attribute coordinate must lie within the specified height of the point's shape.

Records

  • MUST NOT RECORD IN FUTURE (validation rule)—Recorded date cannot be a future date.