ArcPro Traverse tool needs "Jump to" setting for a line to retrace a path without duplicating a segment.

[JimP-notUniqueAtAll]

The Modify/Traverse tool needs a feature where you can backtrack over a previous segment without duplicating the line. This is especially important when you export and import Traverse.txt files and you want all the lines to be in one file.

ChatGPT seems to think this is a GO and TO feature in create/Traverse. But since initial placement is most likely being done in Modify/traverse in arcPro- It would be great to have there.

If I want to cogo more than one adjoining parcel at a time, it is impossible to digitize without going over a previous path. (like working with an etch-a-sketch). 

All you need is an option to "Jump to" in the boxes on the left- where you <RC> and have "reverse" etc. and it will move the start of your next line there without producing a duplicate line.

The export and import features will need to honor this new functionality. Thank you

[AmirBar-Maor]

Hello @JimP-notUniqueAtAll 

You write "If I want to cogo more than one adjoining parcel at a time" - why don't you set the starting point (POB) on the adjoining parcel common boundary and close the traverse at the other end of the common boundary? Is it because you are trying to produce a traverse text file for each parcel?

Could you please clarify the workflow you are trying to acheive? 

[JimP-notUniqueAtAll]

The method that you describe would produce one txt file for each parcel. But I would like to produce one txt file for a whole block of adjoining parcels and we can't do that unless we "retrace" over cogo to position our cursor to continue more adjoining parcels. 

Since my original post I discovered that the best practice is to have a start point and a force close point for each parcel, (and then export .txt) .  That is the only way that we are guaranteed the open and closed points are snapped upon subsequent imports. (Because those coords are then hardcoded into the .txt file )

Thank you

[AmirBar-Maor]

@JimP-notUniqueAtAll 

So if I understand correctly, your goal is to produce a traverse text file for each parcel in a group of parcels - is that correct?

And if so, why do you need a traverse text file? Wouldn't it be nicer to have a 'parcel report' that is better formatted with the list of lines, their COGO values, COGO area, and parcel name?

[JimP-notUniqueAtAll]

No, you are misunderstanding.  I would have liked to have one .txt file for a whole neighborhood of parcels.  But I have since given up on that idea because it seems to be important to start and force close each parcel in order to get xyCoords printed in the .txt file.

I need .txt files for the client to import into their system.

I am finished with this topic as thru extensive research/experimentation- one parcel per .txt file is the most realistic.

This "parcel report" that you mention. Is that available in arcPro? Sounds interesting.

Thank you

[AmirBar-Maor]

@JimP-notUniqueAtAll 

A 'closed traverse' can only contain one loop of lines (or start from a known locaiton and end in another known location).

It cannot contain multiple loops (parcels).

About Parcel Report:

You can use the geoprocessing tool Export Sequenced Parcel Features to export the lines and points of the selected parcel to a file geodatabase.

Then you can create a layout pointing to that exported data, which will refresh everytime you select another parcel and export again. 

The layout can contain a 'Dynamic table' element that would list the point and/or lines and the attributes you want to expose.

You can see this pattern in the title map video recording: https://community.esri.com/t5/arcgis-parcel-fabric-videos/parcel-fabric-2torial-create-a-title-map-f...

Would that work?

[JimP-notUniqueAtAll]

No the "Export Sequenced Parcel Features" would not work. The client wants to utilize the Traverse tool in arcPro with the imported .txt file from me to finish editing the editing of their parcel layers. They'll just have to import them a closed parcel at a time to have a clean and consistent result.