ArcGIS Parcel Fabric Blog

The previous blog shows how you can keep a line as fixed, while still being able to add vertices to it.

But can you use attribute rules to prevent lines from bending?

The answer is yes. 

The Arcade method Generalize removes vertices within a giving tolerance. So we can compare the geometry of the feature to the generalized geometry to find out if they are different.

In this example, lines are allowed to bend up to 1 meter, but you can change that to your desired tolerance.

 This is the Arcade expression:

var MaxOffset = 1;
Var OffsetUnit = 'meters';
if (Equals(Geometry($feature), Generalize($feature, 1, true, 'meters'))) { return false; } 
return true;

Simply create a constraint rule and set it to be triggered on 'update'.

If you are using ArcGIS Pro 3.4 or above, only trigger it when the shape is updated:

Disclaimer: This example  is the first draft that has not been thoroughly tested. You can add the logic to only constraint the update for specific lines, else you'll not be able to align any parcel to each other.

Please leave comments if this is useful, thoughts etc.

Amir

Can I keep lines fixed?

The simple way to keep a line fixed is to make sure the line is attached on both ends to a point that is fixed. As long as the topology is on in the editing tab, a fixed point will prevent any attached line or polygon from moving.

But what if you wanted to keep specific lines as fixed based on an attribute?

We can try to copy the attribute rule constraint that is used in the point feature class to the lines. That rule  is triggered on 'Update' and compares the geometry of the feature before and after the edit using the arcade method Geometry($OrigianlFeature).

But topology validation should be able to add a vertex in that line (cracking and clustering), so we should instead only make sure the end points of that line do not move.

Can this be done using Attribute Rules for specific lines?

Yes - here is a sample you can use. It checks that the start vertex and the end vertex do not changes during an edit by comparing their X and Y coordinates.
You can probably condense this expression and adjust it to your specific lines:

var IsSameFromX = (Equals(Geometry($feature).paths[0][0].x, Geometry($originalFeature).paths[0][0].x));
var IsSameFromY = (Equals(Geometry($feature).paths[0][0].y, Geometry($originalFeature).paths[0][0].y));
var IsSameToX = (Equals(Geometry($feature).paths[-1][-1].x, Geometry($originalFeature).paths[-1][-1].x));
var IsSameToY = (Equals(Geometry($feature).paths[-1][-1].y, Geometry($originalFeature).paths[-1][-1].y));
// if $feature.LineType == 1){ //comment out
    if (!IsSameFromX) return false;
    if (!IsSameFromY) return false;
    If (!IsSameToX )return false;
    If (!IsSameToY )return false;
//} //comment out
 return true;

To use this in an attribute rule make sure to only trigger it on 'Update'. If you are using ArcGIS Pro 3.4 and above, limit the attribute rule to get triggered when the SHP field is modified.

Intended for database administrators as recommendations for establishing the product workspaces in an Enterprise Geodatabase (Oracle®, SQL Server®, PostgreSQL®).

Mapping & Charting Solutions (MCS) Enterprise Databases Best Practices

Intended for database administrators as recommendations for establishing the product workspaces in an Enterprise Geodatabase (Oracle®, SQL Server®, PostgreSQL®).

Released with Pro 3.2 is the ability to read and update the active parcel record in a map containing a parcel fabric.

It's great to see a new system deployed in 4 months. This includes training and system integration. But they are not done yet, this is just "one piece in the puzzle" says the GIS coordinator Vyla Grindberg.

We had consistently been five to six weeks behind in making updates to parcel data for a long time. Working in Parcel Fabric has streamlined the process to the point that we will never be behind again. Our colleagues in Planning and Zoning, Emergency Management, and other departments can count on us to provide accurate data that enables them to work efficiently and meet important deadlines.

Bailey Banks, GIS Technician

Migrating our parcel management to the Parcel Fabric has been a game changer. It’s transformed our internal processes, drastically reducing the time it takes us to make updates, but it’s also making a difference far beyond our team and department. We are now supporting multiple departments who recognize the value of up-to-date parcel data and, because it’s in the Fabric, are able to use it with their own systems and workflows.

Tim Conner

Tutorial series describes the full branch versioning process.

ArcGIS 10.6 and 10.6.1 (Desktop (ArcMap) and Enterprise) will be RETIRED on January 1, 2024.

Please refer to the Product Life Cycle on the Esri Support site.

Enterprise PLC - https://support.esri.com/en-us/products/arcgis-enterprise/life-cycle

ArcMap PLC - https://support.esri.com/en-us/products/arcmap/life-cycle