idea Enhancements to the Merge Parcel Points tool in ArcGIS Parcel Fabric Ideas

Enhancements to the Merge Parcel Points tool

SusanHenton — Thu, 19 Oct 2023 14:20:13 GMT

With the ArcGIS Pro parcel fabric, control is no longer stored separately from regular parcel points.

When we integrate a new survey plan, often the first thing we do (after creating a new record) is import control. Sometimes this is done manually, sometimes this is done via a script in a task. The control points we are importing usually do not sit on the parcel corner they represent. In the ArcMap world, we would link the control point to the parcel point it represents using Match Control Point. In ArcGIS Pro, what we need to do is merge parcel points.

In our case, we typically want to preserve the attributes of the control point but the geometry of the parcel corner point so as not to skew the geometry. This means that this is now a 2-step process. Either:

Move the control point (either with the Move tool, or the Edit Verices tool) to snap to the parcel corner it represents
Merge points and preserve the control point

Copy and Paste Attributes from the Control point to the parcel point it represents
Merge points and preserve the original parcel point that now contains the control attributes (we would do this in cases where publication systems are dependent on preserving original features so as not to introduce unnecessary changes in publication).

It would be ideal if the Merge Parcel Points tool offered a way to do this with only 1 step. For example: editors could choose the preserve the geometry from point 1, but the attributes from point 2. This would allow us to tie the new control into the parcel fabric with only 1 tool, instead of using 2 tools. Or, when they preserve the geometry from point 1, provide an option to transfer attributes from point 2 before the points are merged. Any of those enhancements would make this a 1 step process for us.

Also - the Merge Parcel Points tool only displays some of the attributes (for example ObjectID is missing). Currently, this makes it difficult to figure out which point to preserve if we've already copied and pasted attributes from the control point. So, if all point attributes could be included in the Merge Parcel Points window, that would be ideal.

Re: Enhancements to the Merge Parcel Points tool

MizukiKayano2 — Thu, 19 Oct 2023 21:36:07 GMT

Editor tracking fields are also not displayed in the Merge Parcel Points tool in enterprise. These fields would similarly be helpful in determining which point to preserve.

Re: Enhancements to the Merge Parcel Points tool - Status changed to: Needs Clarification

AmirBar-Maor — Wed, 25 Oct 2023 15:10:56 GMT

Did you consider using the geoprocessing tool Import Parcel Fabric Points?

It allows you to match new points with existing points and choose the type of update:

For example - only update the geometry but preserve the attributes of the target point.

Re: Enhancements to the Merge Parcel Points tool

SarahSibbett — Thu, 26 Oct 2023 14:40:26 GMT

Hi @AmirBar-Maor - thanks for the suggestion.

I'm not sure I totally understand what you are recommending. In this scenario, the new points are not a separate feature class - they are added to the parcel fabric points as new points via the Create Features> Absolute XYZ functionality.

I tested the Import Parcel Fabric Points tool out and it looks like it is possible to set the input as the parcel fabric points. I tried with a few different options and it always identifies the match, but nothing actually is moved or updated. I'm not sure if that is because my input is the fabric points...

Also - since in this scenario, I can only match based on proximity (the name nor globalID do not match), I would have to first select the points I want to matched, since otherwise there is a chance many other points could move that I don't want to move. I'm kind of thinking nothing actually happens in the tool because of the selection I have set, but I can't run the tool without a selection since it would then process all points in my fabric...

Have I totally misunderstood what you are suggesting?

Re: Enhancements to the Merge Parcel Points tool

AmirBar-Maor — Fri, 27 Oct 2023 07:57:21 GMT

@SarahSibbett

@SusanHenton writes that "The control points we are importing usually do not sit on the parcel corner they represent."

Are they imported or entered manually?

Assuming you read the XY coordinates from a spreadsheet you can automate this process and string the Geoprocessing tool mentioned above.
Importing points from the same source to the same target is not supported and is not really an 'Import'.

Re: Enhancements to the Merge Parcel Points tool

SarahSibbett — Fri, 27 Oct 2023 15:57:03 GMT

@AmirBar-Maor I see the confusion - sorry about the terminology mix-up. The control points are entered manually based on XY coordinate information provided on a survey plan.

Re: Enhancements to the Merge Parcel Points tool

AmirBar-Maor — Mon, 30 Oct 2023 13:02:31 GMT

@SarahSibbett

Does the editor know which point they are going to update?

If yes: would improving the Edit Vertices tool such that after updating a point XY coordinates it maintains the parcel topological integrity make sense? (one step instead of 2 step process)

Re: Enhancements to the Merge Parcel Points tool

SarahSibbett — Tue, 31 Oct 2023 13:30:42 GMT

@AmirBar-Maor

"Does the editor know which point they are going to update?" - as in, instead of creating a new control point and then merging it, they edit the existing parcel point the new control would ultimately be merged with? So, add XY attributes, relate it to the active record, fill in all other control point information the customer happens to have. Is this what you mean? I'm not super clear on where the Edit Vertices tool comes into play here, though - can you elaborate?

Re: Enhancements to the Merge Parcel Points tool

AmirBar-Maor — Tue, 31 Oct 2023 13:39:54 GMT

@SarahSibbett

If the editor knows which points need to be updated they can:

Select the point
Update its geometry using the Edit Vertices tool (note: the tool needs to be enhanced. Currently it moves the point but does not update the parcel and its lines)
(optional) update any other attribute and/or associate to a record

We can also prevent/warn the user if this movement breaks the data integrity of the parcel.

Re: Enhancements to the Merge Parcel Points tool

SarahSibbett — Thu, 02 Nov 2023 01:08:48 GMT

@AmirBar-Maor I see where you are going with this now. I think it could work, but still not sure this going to be 1 step. You'd have to select the point, update geometry/attributes, then make sure the point gets associated with the active record. Do you think this is better than what Susan was suggesting with enhancing the Merge Parcel Points tool?

Re: Enhancements to the Merge Parcel Points tool

AmirBar-Maor — Thu, 02 Nov 2023 11:47:07 GMT

@SarahSibbett

These are the 7 steps required if using the Merge Points idea:
1. Create an active Record
2. Create a new point and enter the XY Coordiantes
3. Attribute the new point
4. Launce the merge points tool
5. Set the merge points settings (preserve attributes, only geometry)
6. Select the points to merge - must be only 2 - right?! What if there are 3 or more?
7. Press Merge Points

These are the 5 steps required if using the Edit Vertices idea:
1. Create an Active Record
2. Select the point to be updated
3. Launce the Edit vertices tool and enter the XY coordinates
4. Attribute the point
5. Associate the point to the active record

Did I get it right?

Re: Enhancements to the Merge Parcel Points tool

MizukiKayano2 — Tue, 07 Nov 2023 17:07:19 GMT

Hi @AmirBar-Maor

Here at LTSA we also see value in what Susan has suggested for the Merge Parcel Points tool. In our case, it is not necessarily always new points that are being creating into the parcel fabric, but existing points. Take this scenario below, with three points already in the fabric:

In this case, we want to keep the attributes from 1 and merge all points to 2 (because 2 has the oldest objectid, which is important for our publication system, and because we don't want to distort the current fabric). I see the Merge Parcel Points tool as being the most straightforward way to do this. Would you agree or do you have a different approach?

Zoomed out view, for context:

Re: Enhancements to the Merge Parcel Points tool

AmirBar-Maor — Wed, 08 Nov 2023 10:33:26 GMT

@MizukiKayano2

Part of my job description is to ask "why?" - please take no offense.
Regardless of how points are created, the scenario in which you want to use the geometry of one point and the attribute of another is legitimate.

If there are more than 2 points, could you please confirm that LTSA does not expect attributes to be merged from more than one point?

Re: Enhancements to the Merge Parcel Points tool - Status changed to: In Product Plan

AmirBar-Maor — Wed, 08 Nov 2023 10:36:19 GMT

Re: Enhancements to the Merge Parcel Points tool

SarahSibbett — Wed, 08 Nov 2023 14:15:53 GMT

@AmirBar-Maor thanks for outlining the end to end with Edit Vertices vs. Merge Parcel Points. Certainly a workflow to consider depending on which customer and what requirements we are dealing with!

Re: Enhancements to the Merge Parcel Points tool

MizukiKayano2 — Wed, 08 Nov 2023 18:23:24 GMT

@AmirBar-Maor

We totally understand your need to ask why - we are always open to thinking of new ways of approaching workflows, especially since we are moving to a new software platform - so we appreciate all the consideration!

The attribute we want to keep is always of the Ground Control Point (which has 20+ fields populated). We would merge this with regular points when:

we notice mis-joins from the ArcMap days and see a cluster of points near a GCP that should all be one point
an existing parcel corner is surveyed and we receive a new GCP with 20+ attributes pre-populated

So if there are more than 2 points (one point with attributes of a GCP, and other points with no additional attribute), LTSA does not expect attributes to be merged from more than one point.

Thank you!

Re: Enhancements to the Merge Parcel Points tool - Status changed to: Implemented

AmirBar-Maor — Tue, 12 Mar 2024 16:03:06 GMT

Implemented in ArcGIS Pro 3.3