Traverse Tool - Closure Direction

[AbigailSmith18]

ArcGIS Pro Traverse Tool does not give the Misclose Direction if a survey entered in the Traverse Tool does not close. The ArcMap Traverse Tool generated a Closure Report containing Misclose Distance and Direction. Could a Closure Report containing both Misclose Distance and Direction be automatically generated by the ArcGIS Pro Traverse tool? Or could Misclose Direction be added to the Misclose information box in the Traverse Tool?

[AmirBar-Maor]

@AbigailSmith18 

When examining which misclose information to display we could not find any justification for showing the misclose direction.

Could you please explain why you need to see the misclose direction and how you use this information.

If it is really important you can still review it by switching to the CLOSURE tab and setting the Closure method to 'Snap last line to close'. The last course shows the misclose direction and distance.

You can copy past the misclose information by right-clicking in the traverse misclose area and pressing 'Copy text'. Most organizations do not use this functionality because it is already stored as a parcel attribute that can be used for QA (Quality Assurance).

[AbigailSmith18]

@AmirBar-Maor 

I reached out to my client for clarification on how they use it in their current workflows in ArcMap the response is below: 

"I have attached a screenshot of an example I used today. This error in closure of N 7-56-22 W 4.86 feet had to be communicated with an attorney’s office. Not only do we use it when new surveys or splits come through the system that do not close, the direction helps us verify if the problem is an existing call or not.

When the planning department sends the GIS plats to review, the specific direction and distance is then sent back to the surveyor to address. We also traverse the lines twice to ensure it is not a human error on our part. There have been times when the error in closure distance remains the same when the direction has changed meaning it is not the same error in closure as previously traversed. Showing both ensures that the correct parties are contacted with all of the information that will be needed. We are able to communicate with other departments and outside the organization exactly where the error lies."

[AmirBar-Maor]

Thanks for the quick feedback @AbigailSmith18 

There are a few methods to try and detect blunders in a traverse as described in this slide deck.

It is also possible to detect a single-direction blunder in a closed traverse using this method: 

Would improving blunder detection in the traverse pane make more sense than exposing additional information?

[RachelBaca]

The directional information is standard surveying info as well as a standard practice.   If I have to contact the PLS of record due to an error, the misclosure distance and direction are expected.   If I cannot do this in ArcPro, I'll be forced to use AutoCAD or another traverse software.    In fact, there other functions that ArcPro does not have that even ArcInfo had that helped when trying to deal with non-tangent curve errors:  bearing\bearing, bearing\distance and distance\distance intersections.  Those are invaluable functions.

[AmirBar-Maor]

Hello @RachelBaca 

You will find the command you refer to in the editing toolbar. Those are 'intersection tools' and you can learn more about them in the help documentation.

ArcMap and ArcInfo included functionality that was never used and not needed, so we must examine 'why...?' a capability is required before adding it to ArcGIS Pro. That includes understanding the workflows. 

What do you do when a recorded document has an error?  Can you reject it and have the surveyor correct and resubmit it?

[AmirBar-Maor]

We plan to display the misclose direction in the near term

[AbigailSmith18]

@AmirBar-Maor 

I will pass along the information provided above to my clients, but it would be more streamlined for their workflows that the additional information (Misclose Direction) be exposed in the Traverse Tool verses having to manually generate it/go to additional windows. 

[AbigailSmith18]

@AmirBar-Maor 

Thanks for the update!

[TimHodson]

In the ArcMap Traverse tool, the misclose information includes the difference in XY.

We are looking for feedback from everyone on whether or not to include it in the Pro Traverse.

Is there value in representing the closure as X and Y differences as well, or is Direction and Distance enough?

Please let us know if the XY representation gives you additional capabilities\business value that the Direction and Distance does not.

Thanks.

Option 1:

Misclose: N7-56-22W, 4.86 ft
Misclose XY: -0.671, +4.813
Misclose Ratio: 1 : 89
Calculated Area:
Closure Method: Compass (default)

 Option 2:

Misclose: N7-56-22W, 4.86 ft
Misclose Ratio: 1 : 89
Calculated Area:
Closure Method: Compass (default)

[NabilDroby1]

@AmirBar-Maor @TimHodson 

I use traverse tool in my daily work for parcels and other related work, and I can't imagine doing any without this tool, and I save my traverses all the time and load them when needed. The misclosure report in ArcMap is crucial in my work; it helps me to get a cogo quick check on which call has the potential error, e.g. when displaying a misclosue bearing error like N 52-10-43 W, 10.00 I can quickly check all the calls and see if I have this bearing and then check the distance and often times I would have the distance typo by 10.00. Another useful thing in the traverse tool in ArcMap is when I start creating a new feature from a point that has coordinates and after entering some cogo lines, I can click anywhere while I'm cogoing to get the end coordinates to make sure they match the provided ones by the surveyor in the plat, and sometimes I don't have to do all the cogo because when clicking on some existing points, I can immediately know if the cogo closure is good and I'll just end at this point, and then the misclosure report in ArcMap is helping me reducing the work time.

I hope that you can add the same report in Pro to include the Misclosure As Direction/Distance, Misclosure As X/Y, and the End field so we can check the misclosure along the way.

Thank you