nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Backdating Parent Parcels

Eroberts

ArcGIS Pro 3.4

I recently started a new job working as an analyst for a county. I have only worked with ArcMap prior to this position, and I am the only analyst for the county, so have been doing a lot of self-teaching as I am learning ArcPro. I have been tasked with backdating all of the land divisions we have on file (decades worth) for the county. The analyst before me did not use a parcel fabric, which from my research, I think is the best method for this project. I am starting with a (almost current) map of tax parcels that I have used to generate a parcel fabric for the entire county and am going through the land divisions year-by-year.

I have come across another post on here about the method for backdating and have been successful so far in creating the record of a split and getting the parcel lineage feature to properly show the split. Within the record I have created fields to enter the information the director has asked me to keep (i.e., parent parcel #, control #, acreage, proposed and maximum splits, DOA). When I am merging the two child parcels back into the parent, I enter the parent parcel # and acreage into the attributes. My issue is that as I work backwards through the divisions, I am coming across land divisions that are dividing fractions of the original parent parcel and am unsure of how to deal with these. If I create a record for a split that took place in say 2023, and merge those parcels back to their "parent" and then come across an earlier split from when that "parent" was originally split, how would I get the record to properly show the lineage of those parcels? Should I retain the information for each split in the attributes of the parcels or is it okay to keep it in the record?

An example for clarification: I have a division in front of me that shows a 5.17-acre parcel to be released, and a remainder parcel of 19.83 acres. The total parent parcel acreage is 112 acres. If I create a record to show this split from 2022 and enter in the information for this division into the record (I am now thinking I should enter the division information into the parcel attributes not in the record as each division will have a different control #, date of approval, etc.?) what would the steps be when I come across an earlier division of the same parent parcel to ensure that the parcel lineage is properly shown?

TLDR; I am working through land divisions starting with the most current year and working backwards. As I come across land divisions that are splits of fractions of the original parent parcel, what steps should I take to ensure I am properly tracking the records when I eventually come across an earlier split of the same parent parcel?

I apologize for any run-on sentences or if anything is unclear. I will be more than happy to clarify anything. Thank you in advance.

Find more posts tagged with

Accepted answers

All comments

Eroberts

I am thinking I have solved my own issue but would like some insight if this is correct.

I have been naming the records based on the control # which is the departments unique identifier for the land division. As I regress to the parent parcel there will be multiple control numbers as there are multiple divisions. I am thinking I should transfer the control # and other information I was asked to keep, to the attribute field of the historical parcel that was retired by that control #, so when viewing the historical parcel my director (we do not have a GIS department I am under P&Z fyi) and any others will be able to view which division (designated by control#) retired that parcel. I should then give the record the name of the parent parcel, so that as I come across earlier land divisions for that parent parcel I can just add the other parcels that are contained within that parent parcel to the record, which would then all be contained under that parent parcels record.

I am still unsure of how to get a record to show that one parcel was retired by a division which then that child parcel was retired by another division? I am starting with the current state of the parcels and I have tried to merge the two parcels created from a split to make the parent. And then merge that parent with the parcel it was split from to create that parent, but when I open the parcel lineage it is not showing the proper flow. It should show ex: Parent --> Parcel A and Remainder and then Remainder--> Parcel 1, 2, and 3. But it is only showing Parent --> Parcel A, Remainder, 1, 2, and 3. Do I need to manually adjust the lineage flow chart to show the proper history? Or does this mean that the record is tracking it incorrectly, and if so how do I get the record to properly track two historical parcels and their respective child parcels?

Eroberts

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? Screenshot 2024-11-15 134920.png

-_Ashley-B-Potter_-

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.

Eroberts

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.

Screenshot 2024-11-15 151355.png However when I do the split of the child parcel, the lineage does not show the first split. How do I properly use the records to have it show both splits in the lineage? Screenshot 2024-11-15 145857.png

AmirBar-Maor

@Eroberts

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.

DianeBaker

I found it difficult to go backwards in the ProFabric. What I do instead is start drawing from the beginning and work to the current.

AdamHart1

I am slowly doing this exact same project in my county. I am mostly using the #3 method that Amir suggested above especially for the parcels that didn't exist in the fabric before it was created. I have a couple of attribute rules set up to automatically create record names.

If you would like to know more about my workflows, feel free to message me.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.