Update COGO attributes when using the rotate tool.

[GIS-Chops]

I'm entering some condos and quite often I will copy lines that make up an identical building, move them and rotate them. I calculate the rotation angle and enter it in the rotate tool. It would be nice if Pro would update the COGO attributes of those lines based on the rotation angle that I enter in the rotate tool.

[AmirBar-Maor]

Hi Jeff,
This is an interesting idea. We usually try not to alter the recorded COGO dimensions and instead update the 'Rotation' and 'Scale' fields on the lines. 
The Ground to Grid correction can yield similar results but it would not change the COGO fields, and you might already be using it for the real ground to grid corrections.

Is there a case where you would want to use the Rotate tool and NOT update the COGO dimensions?

To be consistent, should the Resize tool update the linear dimensions?

[BillFox]

If I remember correctly,

after entering a tract map using cogo and closing up everything nice

then rotating (before moving) it to match the particular bearing of the line of the chess-board of township/section/range,

we have to run the update cogo lines tool as a reality check that we rotated it in the correct direcction/amount before moving all the line-work of the tract map into place in the parcel layer

if that is still so, it would be nice to have the cogo attributes auto-update themselves with the rotation

probably similar needed for reference frames / vertical datums with the upcoming NATRF 2022 / ITRF2020

[TimHodson]

In general, the goal is that bearings and distances stored on the COGO attributes match the record found on the original document. If there are a set of condo footprints on a document that are identical in all respects aside from their orientation, then it makes sense to be able to make a copy of one "footprint template" and then after moving and rotating the copy by a specific angle, update the bearings from the copied lines using that entered angle in order to match the record on the document for that newly positioned condo footprint.

[GIS-Chops]

I see what you mean @AmirBar-Maor about cases where you wouldn't want to update the COGO attributes. Is there a way to create a tool in the modify features pane in the parcel fabric group that duplicates the rotate tool but will update COGO attributes and call it condo rotate or template rotate as @TimHodson suggests? Either by entering the rotation angle or clicking a line and a dialog box opens and you specify the new bearing of that line, then the selected lines are rotated and attributes are populated? Still having the anchor point available of course.

Here's my imagined workflow -

Copy and paste the lines of a condo building, while those lines are selected, move them to the new location using the anchor and snapping to the end of a connection line. Activate the Rotate Condo tool and enter the rotation angle - positive numbers for clockwise rotation and negative numbers for anti-clockwise rotation. Maybe provide an angle calculator for bearing to bearing angles when it rotates to another quadrant - that way I wouldn't have to do any math. Then the tool rotates and updates the COGO attributes.

[AmirBar-Maor]

@GIS-Chops 

In general, we only create parcel tools for tools that are specific to parcels and leverage existing editing tools as much as possible. The editing tools (such as merge, clip, divide, etc.) can exhibit different behavior when parcels are being processed, making it easier for new editors to learn and edit parcels.

So would something like this work?

 

[IvanSpencer]

Amir, while reading this post I had envisioned your solution and then there it was. I think that would work. Make it so, please.

[AmirBar-Maor]

@IvanSpencer  thanks for your feedback.

If you would like to see this idea implemented I recommend that you give it a kudo (it currently has 0 kudos).

[Crinoid]

Kudos can't be added to this suggestion because it was assigned a status of "Needs Clarification."

[AmirBar-Maor]

Thanks @Crinoid  - I was not aware of that limitation. It explains the low number.
Changed the status to 'In Product Plan'.
No more kudos needed.

If you have a different use case, it's always good if you can add them in the comments.