Community
Select to view content in your preferred language

Spatially attribute Null data in the fabric to a record

684
1
10-08-2024 07:47 AM
Status: Needs Clarification
JasonBessert
by
Regular Contributor

I have an idea for a new tool to assist with data cleanup/validation.  It doesn't necessarily have to be a new tool, it could be an added functionality or check-box parameter within the "build parcel fabric" geoprocess.  Given the default attribute rule MUST HAVE RECORD creating a need for all data to have "created by record" field populated, as we compile or convert parcel fabrics, we typically go out of our way to bind all polygons to record polygons, by building records for subdivision polygons, but it's rather challenging to get all lines associated with records, especially lines that are along the boundary between two record polygons, hence the reason why such a tool idea may have its own challenges. 

The suggestion would be to use record polygons and find points, lines and/or polygons of all types that are NULL and populate the "created by record" field with the GUID of the intersecting record polygon, as a quick fix means of getting all data within compliance of the "MUST HAVE RECORD" attribute rule.

We see a need for this, not just with conversions, but also in live parcel fabric editing, where users tend to create data outside of active records, if they are not careful, and this would aim to be a useful tool for keeping errors from emerging off of data validations of attribute rules.

 

(I meant to post this here, in parcel fabric ideas, but I originally added it to the parcel fabric questions, my bad)

0 Kudos
1 Comment
AmirBar-Maor
by Esri Regular Contributor
‎10-23-2024 05:35 AM
Status changed to: Needs Clarification

@JasonBessert 

In this post you can learn how to modify the MUST HAVE A RECORD rule such that it only errors for parcel features that were created after the migration date.

Another thing you can do is create a geoprocessing model that iterates on the record features:

  1. Use the  geoprocessing tool Select By Location to select all the parcel features that 'have their centroid within
  2. Use the geoprocessing tool Select Parcel Features to select parcel features (lines and points)
  3.  Use the geoprocessing tool Select By Attributes to remove features that are already associated to a record
  4. And finally, calculate the record GlobalID as a GUID on the CreatedByRecord field

Let me know if this would work and if you need help with the geoprocessing model

Amir