Have you seen COGO Reader?

[DanielStone]

Good day Parcel Aficionados,

With the release of ArcGIS Pro 3.5, the parcel fabric team has introduced the COGO Reader Tool.   COGO Reader is a new tool designed to assist editors that enter metes and bounds to describe land boundaries.  

Here is a short video of Jason Camerano demonstrating the advantages this tool can provide when entering deeds. 

https://link.esri.com/ParcelFabric/COGOReader

Enjoy

Dan Stone

[ArizonaGIS2]

Hey Dan, I'm not sure if I am missing something, but I can't for the life of me get the parcel courses | Template to populate. We don't manage parcels but regularly digitize easements and zoning cases, and this tool would be great to incorporate into our workflow.

[ArizonaGIS2]

Disregard. I found the missing step.

[LukeRipple]

Hello, I am also having issues with the Template portion of this tool. Could you tell me what you did to fix it? Thanks.

[AmirBar-Maor]

@LukeRipple Can you please confirm:

1. You are using the parcel fabric
2. You can see the feature templates visible in the Create Features pane?

[EMCAdministrator]

I had the same problem, but ChatGPT helped me. I had to go to the catalog pane, right-click on the parcel fabric -> Manage -> Add Parcel Type. This creates a parcel line layer inside the fabric that can be used as a parcel course layer in the COGO reader.

[LukeRipple]

Hello EMCAdministrator, I just tried this and it worked! Now when I open the COGO Reader tool, the connection lines template and the parcel lines template sections are populated. Thank you for suggesting this!    

[Fabian_Shenk]

Just for knowledge, what was the missing step?

[HeatherHanson]

We have been testing it as we prepare for the transition to Pro.  Is the capability of handling non-tangent curves in the works?  This seems to be the most consistent error we've encountered.  Being able to send it to traverse and then modify is helpful at least.

[AmirBar-Maor]

@HeatherHanson  COGO Reader does support non-tangent curves. But in some states/descriptions are written differently and COGO Reader fails to process them.

The best thing you can do is contact technical support and provide a few examples of deeds with non-tangent curves that fail to process. If this occurs a lot, we can consider adding it to one of the 3.5 patches, once fixed.