ArcGIS Pro 3.1.0: What is the best practice to display the tree of a parcel lineage history particularly in case of parcels merge? For example, in the screenshots below, parcel#888 has the following transactions: * it is divided into two parcels: 888/1 and 888/2 * parcel 888/1 is divided into two parcels: 888/1/A and 888/1/B * parcel 888/1/B is merged with 888/2 to form 888/1/B + 888/2 Now as the parcel 888/1/B + 888/2 is identified, it provides different history depending on where we click. What could be the best practice to display the tree of the history of parcel888/1/B + 888/2?

@JamalNUMAN You might want to invest the time and watch this recording of "Introduction to Record-Driven Workflows". It explains concepts and demos of: * Record-Driven workflows * Active record * Merge * Split using different methods * Parcel Lineage and historic parcels We can also contact your distributor @MichaelYounan

I follow the steps below to ensure the lineage is correct: * The record named 129 is created and made active. * While the record named 129 is active, parcel 129 is digitized, and the name is filled with the number 129. * While the digitized 129 is selected, the lineage icon is pressed to retrieve the parcel lineage. * Parcel 129 is then split, and each part is named (129/1 for the upper and 129/2 for the lower). * While 129/1 is selected, the lineage icon is pressed to retrieve the parcel lineage. * Before splitting 129/1, a record is created for it and made active. * Parcel 129/1 is split, and each part is named (129/1/A for the right and 129/1/B for the left). * Before merging 129/1/B with 129/2, a new record is created and made active. * Parcels 129/1/B and 129/2 are merged, and the lineage icon is pressed to retrieve the parcel lineage. T.gdb.zip

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; } } }

ArcGIS Pro 3.1.0: What is the best practice to display the tree of a parcel lineage history particularly in case of parcels merge?

JamalNUMAN

ArcGIS Pro 3.1.0: What is the best practice to display the tree of a parcel lineage history particularly in case of parcels merge?

For example, in the screenshots below, parcel#888 has the following transactions:

it is divided into two parcels: 888/1 and 888/2
parcel 888/1 is divided into two parcels: 888/1/A and 888/1/B
parcel 888/1/B is merged with 888/2 to form 888/1/B + 888/2

Now as the parcel 888/1/B + 888/2 is identified, it provides different history depending on where we click.

What could be the best practice to display the tree of the history of parcel888/1/B + 888/2?

Find more posts tagged with

Accepted answers

All comments

ChristineLeslie

Hi Jamal

In Pro 3.2 you will be able to view a Parcel Lineage tree for parcels in the parcel fabric using the Link Chart functionlity.

Christine

JamalNUMAN

when is the Pro 3.2 expected to release? Can you provide some screenshots how will the tree look like?

AmirBar-Maor

ArcGIS Pro 3.2 planned release date is around the end of October / beginning of November.

Here is a glimpse:

Parcel Lineage Merge.gif

JamalNUMAN

Eagerly waiting to see the enhancement in Pro 3.2!

Thank you

JamalNUMAN

Not sure if this is already implemented in Pro 3.2.1

As per the screenshot below, I tried to plot the history, but the tree doesn’t appear as expected

The test data is attached

T.gdb.zip

AmirBar-Maor

Looking at your data it looks like you forgot to create records.

Parcel 333 was created and retired by record 333.

Unless this is an interim parcel, we would expect a parcel to be created by one record, and retired later by another.

The same applies for parcel 333/1.

A normal workflow look like this:

Record A created parcel 333
Record B splits parcels 333 and retires it. It also created 2 new child parcels 333/1 and 333/2
Record C ....

You can see the problem if you analyze the CreatedByRecord and RetiredByRecord fields on your parcels.

The record-driven workflows are well documented.

The link chart is showing the correct results for a broken lineage.

JamalNUMAN

In order to illustrate my workflow, lets assume that new parcel is added to the fabric (screenshots are added to better explain the steps)

The parcel is digitized. Its number is attached in the Name field (which is 129)
Its record is created along with its number (which is129)
The parcel is linked to its record (as shown in the screenshot)
Now2, the parcel#129 is split into two parts. Each part is given a number (129/1 and 129/2)
Two records are created along with their numbers (129/1 and 129/2)
Each parcel (of the 129/1 and 129/2) is linked to its corresponding record

What’s could be wrong in this workflow?

ChristineLeslie

It seems you are doing a 1 to 1 relationship between parcels and records. If thats the case, your lineage will only ever show 1 parcel in a record - since that is what you are explicitly doing. 1 parcel for 1 record.

This is how I see the correct workflow:

Parcel 129 is assigned to an existing record A. You now want to split parcel 129 (this comes from a new record B that shows the split)
So assuming parcel 129 is assigned to its original record A, you go and create a new record B to represent the split and put it active in the map.
Perform the split
Do a parcel lineage for Record B and you will see an appropriate lineage diagram. Simirlarly if you do a parcel lineage for Record A, you will also see the appropriate lineage diagram.

So, in summary, parcel 129 must be assigned to its original record. Then the new record that represents the split is created and put as active in the map. The split is performed. Parcel lineage is tracked for both the records.

I hope this helps

JamalNUMAN

I follow the steps below to ensure the lineage is correct:

The record named 129 is created and made active.
While the record named 129 is active, parcel 129 is digitized, and the name is filled with the number 129.
While the digitized 129 is selected, the lineage icon is pressed to retrieve the parcel lineage.
Parcel 129 is then split, and each part is named (129/1 for the upper and 129/2 for the lower).
While 129/1 is selected, the lineage icon is pressed to retrieve the parcel lineage.
Before splitting 129/1, a record is created for it and made active.
Parcel 129/1 is split, and each part is named (129/1/A for the right and 129/1/B for the left).
Before merging 129/1/B with 129/2, a new record is created and made active.
Parcels 129/1/B and 129/2 are merged, and the lineage icon is pressed to retrieve the parcel lineage.

T.gdb.zip

AmirBar-Maor

@JamalNUMAN

You might want to invest the time and watch this recording of "Introduction to Record-Driven Workflows".

It explains concepts and demos of:

Record-Driven workflows
Active record
Merge
Split using different methods
Parcel Lineage and historic parcels

We can also contact your distributor @MichaelYounan

ChristineLeslie

Hi Jamal

The data attached did not contain parcel 129. So I just created an approximation. Here Parcel129 is assocaited to RecordFor129. To associate a parcel to a reacord, create the record, set it as active in the map and then select the parcel and assign it to the record you created:

Now to split this parcel, create a new record for the split and set it as active. With the record as active, split the parcel

Now to merge one of the split parcels with another parcel - make sure that other parcel is already associated to its original record. Then create a NEW RECORD for the merge and set it as active. Perform the merge.

Now a lineage for the original record of parcel 129 shows this

RecordFor129 created Parcel129, which was retired by record Split. Record Split created two new parcels Split1 and Split2. Split2 was retired by record Merge, which created MergedParcel.

Please see the help docs and videos for more information on how to create and manage records.

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.