Regressing to Parent parcels

Question

Hello,

After watching the What's New Parcel Fabric @Anonymous User Pro 2 7 - great stuff!!

I did have one question that base based on the time slider of parcel lineage (around 9:50 into the youtube video https://www.youtube.com/watch?v=1O-jDULOMlg) We are looking to move toward Parcel fabric but is there a methodology to create the parents after the children for historical purposes?

Our Community development folks have maintained paper copies of the tax maps for the last 20 years so they can go back to figure out where a permit may have been applied to a parent parcel and how it pertains to the current parcel structure. To support this digitally, I would be looking at backfilling the parcel genealogy as time and staff permitted starting with the current parcel constructs.

Thoughts?

Regards,

Tom

AmirBar-Maor · Answer

Hi Tom,

Creating records for all your historic parcels should be easy if they can have a field (or combination of fields) that has the name of the legal record. This is done using the geoprocessing tool Create Parcel Records.

It is harder to backfill and associate the RetiredByRecord field, but potentially can e deduced using temporal information. If you would like to share a sample data with us we can look into it.

Parcel lineage is going to get even better.

Amir

jcarlson · Answer

We're actually already working on regressing to the parent parcels, which we have been referring to as "backdating the fabric". While there isn't a built-in workflow for this sort of thing, we've got a pretty reliable method worked out. The important thing to keep in mind is which of the editing tools will automatically retire a parcel with a record active.

Backdating a Split

* Create the record.
* Select the child parcels.
* Click Assign Selection to Record in the Manage Records pane (or from the little active record chip)
* Toggle the record mode so that no record is active.
* Use Merge to merge the child parcels into the parent shape.* Be sure to use the New Feature mode
* Check the box to Keep original features
* Set the name and various attributes as needed

* Toggle the record mode so that the record is active again.
* Select the newly-merged parent parcel.
* Click Set Historic, or copy and paste the record globalid into the Retired By field.
* You now have a historic parent parcel and its children correctly assigned to the same record!

By performing the merge outside of an active record, we avoid retiring the child parcels by mistake.

Backdating a Combination

A bit more convoluted, but it still works.

* Create the record.
* Select the child parcel.
* Click Assign Selection to Record in the Manage Records pane (or from the little active record chip)
* Use Duplicate Parcels to create an identical polygon in the same record.
* Toggle the record mode so that no record is active.
* Use Split to cut the duplicated parcel shape in to the parent parcel shapes.
* Toggle the record mode so that the record is active again.
* Select all the newly-split parent parcels.* In the attributes, click the + sign in Created By field to assign a random GUID, or simply leave null if you don't mind the validation error.
* We do this because the initial duplicate parcel has the same record GUID for its retired and created fields, which is incorrect, and one of your split remainders will likely have inherited this value. The other parcels will simply have a null for their created field.

* Click Set Historic, or copy and paste the record globalid into the Retired By field.
* You now have historic parent parcels and their child correctly assigned to the same record!

By performing the split(s) outside of a record, we avoid creating a retired parent for each split performed.

There are other ways to do it as well. You could simply perform the split / combination like it was a current transaction, but then shuffle around this GUIDs in the created and retired by fields, but this seems more prone to error and accidentally retiring something.

Also, boundaries get more complex. We have opted to focus solely on the polygon features, as the lines have a Parent Line ID field that becomes rather cumbersome to keep track of.

Once you get into a rhythm, it becomes quite quick. You can even build these steps into a Task item to semi-automate the record toggling and such. We were able to make quick work of several years' worth of historic parcels.