In our organization, we manage an enterprise parcel fabric service within a branch versioned database.
Currently, the Merge Parcel Points tool takes anywhere from 2.5 to over 10 seconds per point, depending on the complexity of the merge—for example, the number of connected lines. When integrating survey parcel plans, there can be hundreds of points to merge, and at nearly 3 seconds per point, this becomes a major bottleneck in our workflow, significantly reducing mapper productivity.
In contrast, in a File Geodatabase environment, the same tool completes in approximately 0.3 seconds, highlighting a stark performance gap. While we understand that service-based editing has its own overhead, the current implementation of the tool doesn’t appear to scale well in an enterprise setting.
Example:
We recently performed a merge where:
The existing point had 103 connected lines.
The new point had 2 connected lines.
We retained the attribute from the existing point (which is a Control Point) and used the location of the new point.
The Merge Parcel Points tool took 16 seconds to complete this single operation. Below is the relevant output from the Diagnostic Monitor (Task tab):
Task # Queued time Total time Task time Resume time Wait time Function
18127 10:49:43:782 16301 16300 1 0 ArcGIS.Desktop.Editing.EditOperation.ExecuteAsync
Our parcel fabric will continue to grow as new survey parcel plans are added, introducing more points and linework. For long-term viability, it's critical that merging points can be done in a reasonable and scalable timeframe.
