Traverse tool not accepting Direction

[GISUser74305830]

I'm entering in survey calls into the Traverse tool and I'm running into an issue where the Direction I enter doesn't take and gets changed to the direction of the previous call. It gets preceded by an * which, according to the documentation, indicates it is tangent to the previous direction. I'm not a super-experienced COGO user, but not sure what's going on.

[HeatherWidlund]

This is still happening to me on the latest patch. Also, I tried exporting the traverse to a file, editing the direction in the file and uploading it to the traverse tool in a brand new Pro session. It still adjusts the same row!

Any feedback, @Robert_LeClair ?

[Robert_LeClair]

I'm thinking this is BUG-000173775 - "The Traverse tool in ArcGIS Pro fails to retain new quadrant bearing entries that are within 20 seconds of the previous course, defaulting to the earlier value instead."  It's reproducible in ArcGIS Pro 3.4 and 3.5 (Alpha) and works correctly at ArcGIS Pro 3.3.1.

The workaround seems to be "The direction value is shown as NW instead of the entered SW due to how the label expression handles 90, 180, 270, or 360 degrees. Modifying the direction field in the Attributes "pane by adding a small .00001 value nudges it to the other quadrant, correcting the label.

Not ideal clearly but I think that's what's going on...

[HeatherWidlund]

That workaround doesn't address the problem I am seeing, as it has nothing to do with the label. There is nothing in the attribute table as my working feature class is not COGO enabled.

I have a course S54-03-13W 64.03 ft. The next course is S54-03-11W 12.19 ft. Adding .0001 to the 11 seconds does nothing; it reverts to *S54-03-13W.

If this is the same bug, how do I get added to the stakeholders?

[Robert_LeClair]

Yes, sorry about that as I read that item incorrectly.  I do still think it's related to BUG-000173775 as it tracks with the Support Case I'm reading now.  If you'd like to add your Customer Number to the BUG, I believe you can do this by contacting Support Services and working directly with an analyst.

[HeatherWidlund]

Thanks, Robert!

[HeatherWidlund]

This bug appears to be fixed in 3.5. I just tested it after contacting support and the traverses that were failing before are working now. Here is the bug page.

[ChrisJ_FLDEP]

Just a quick FYI.

I know the bug has already been fixed, but here's another scenario where it pops up. The linked bug report states that the traverse direction is defaulting back to tangent when the new bearing is less than 20 seconds. I'm on 3.4.3 and have two successive directions of N10-56-36E and N11-17-59E (a 21+ MINUTE difference), but the traverse tool is still defaulting back to the tangent when I enter the second call. The two traverse call have distances of 31.81ft and 1.28ft respectively. To troubleshoot, I added 10ft to the shorter (second) traverse call. Now I'm going from N10-56-36E at 31.81ft to N11-17-59E at 11.28ft., and  with the added distance to the second traverse call the traverse tool accepted the new direction. So the length of the following line also played a part in the tool not accepting the bearing.