Select to view content in your preferred language

Have you seen COGO Reader?

7393
33
06-27-2025 08:19 AM
DanielStone
Esri Contributor

 

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

 

33 Replies
LeeGravel
Emerging Contributor

Hi, Dan - 

Are there plans to make COGO Reader available as a widget for use in Web App Builder maps? 

0 Kudos
AmirBar-Maor
Esri Regular Contributor

@LeeGravel 

Web App Builder is being deprecated - see announcement here.

It is being replaced with the Experience Builder, which is based on a newer version of java script (4.x).

Do we have to make COGO Reader available to parcel fabric users on the web? yes

When? not in the 'near-term'. We want to release the parcel fabric on ArcGIS Online first.

0 Kudos
LeoDCG
by
Occasional Contributor

is there any way to change the target layer of the COGO reader to a scratch workspace?  We don't necessarily want to be modifying the fabric parcel lines even though it's versioned.

0 Kudos
AmirBar-Maor
Esri Regular Contributor

@LeoDCG 

The issue of using a 'scratch' or 'construction' layer outside of the parcel fabric are:

  1. You cannot use many tool, including COGO Reader
  2. Features you create are not associate to the record. You cannot use 'Show only Active' for example
  3. Inefficient - it introduces more steps, as you have to copy or append the features to the target layer
  4. Schema - as schema might be different, some of the attribution, such as COGO might be lost 

BUT...

If you insist of using a different layer you can always add a parcel type called 'scratch' or 'construction' and COGO Reader will be able to write to those. You can make the layer look exactly as it looks now, so no major change from the user perspective.

Would that work for you? If not please explain why not.

0 Kudos