Backdating Parent Parcels
How do I get the parcel lineage to show multiple records, and which parcels they retired. I am confused on how a retired parcel can be shown as the result of one record and then shown as the parent of the next record, as you cannot set a parcel to be a part of two records (unless you can). I found this section on the ArcGIS Blog but cannot get my parcel lineage to show the same and do not want to continue recording these parcels if I am doing it incorrectly. I now think I should keep my record names as the control # so that the lineage shows which division created and retired which parcels.
TLDR; how do I properly assign my parcels to my records to get this result?
It is going to depend on how the record is executed. If the record is not assigned (check the show only active) then it will not be associated with the record.
Thank you for responding! I think the issue might be that the retired parcels are not showing up in my lineage? This is the result I get: I started with the larger parcel and the parcel in the bottom right. I created a record and then assigned them. I then turned off that record and merged them and then turned the record back on and set the merged parcel as historic. This gives me the result I want when I view the lineage.
Instead of populating the record name (control #) on the parcels, you can add fields and attribute rules that will populate the record name.
To populate the Record the created the parcel you can use this Arcade expression (just change the table name):
var Record = First(FeatureSetByRelationshipName($feature, 'GIS.RecordHasParcel', ['Name'], false));
If (IsEmpty(Record)) {
return "---";
}
return Record.Name;
To populate the record that retired a parcel you can use this expression:
var RecordFS = FeatureSetByName($datastore, 'GIS.PF_Lineage_Records',["GlobalID", "Name"], false);
var guid = $feature.RetiredByRecord;
var sql = "Globalid = @guid"
var Record = First(Filter(RecordFS, sql));
If (IsEmpty(Record)) {
return "---";
}
return Record.Name;
If you are using 3.4 or higher you can make use of the new triggering fields capability:
Back capturing
I believe there are a few methodologies:
- Working backward: assuming your current data is great, in theory, you can try to merge historic splits and split historic merges. It will also involve reversing historic parcels into current and vice versa. you are likely to run into issues with boundary lines and points that became historic and should be current. This method is prone to manual errors and I would avoid it.
- Working forward: I believe this is the common case. You come across an area that requires good historic data and because it is missing, or because it is questionable, you decide to capture historic records, and work chronologically through the transactions. This is the safer approach.
- Only care about parcel polygons and lineage: if you only care about the parcel polygons and linage, and most of your transactions are 'splits', you could just use the Create Features to digitize missing historic parcels and then manual populate the CreatedByRecord and RetiredByRecord globalID fields (GUIDS).
Quality Assurance
- Parcel Lineage depiction: create a link chart to QA that the lineage is correct.
- Parcel Count: the record feature keeps count of the parcels it created and retired. This field get's updated after operations like Build, Merge, Split, Divide.
- Highlight Gaps and Overlaps: make sure you don't end up with overlapping current parcels by increasing the maximal width tolerance and finding overlapping current parcels.
With ArcGIS Pro 3.4 we have improved the link charts visualization.
I hope this helps.
