I do not maintain parcel data and do not need to use the Parcel Fabric for my work but frequently deal with surveys none the less. It would be helpful to be able to use the COGO Reader tool outside of the Parcel Fabric to scan a deed and push the result into the normal Traverse tool.
Please consider having this tool outside of the fabric. We have multiple people in my organization that would benefit from this, but we have no need for a parcel fabric as we do not map assessment parcels. @AmirBar-Maor
This would be extrememly useful for those that have a need to run legal descriptions but have no need for the fabric!
@GordonCourtney @CFMGIS
COGO Reader is designed for parcels of any kind (lots, subdivisions, tax parcels, ROWs...) that are based on a metes-and-bounds legal description.
The parcel fabric controls simple feature classes and has many benefits for cadastre / land records:
So what keeps your organization from migrating to the parcel fabric? Is it because your organization still uses GIS software as a drafting tool (like CAD)? Or reluctant to adopt a web service-based architecture and improve collaboration between departments and stakeholders?
Given that it takes minutes
@AmirBar-Maor Thank you so much for your response. The Parcel Fabric is very valuable and our property appraiser office does use the Parcel Fabric; however, I am part of separate organization that verifies and maps legal descriptions for a different purpose other than mapping lots, subdivisions, tax parcels, and ROWs.
The new COGO Reader tool is amazing and we plan to use it regardless just to map the descriptions and then paste into a COGO line outside of a fabric, but it would be great if it is made available outside of the Fabric. I have multiple users in my organization that will benefit from this amazing tool; however, none of us map legal descriptions for lots, subdivisions, or ROWs that would benefit using the Parcel Fabric.
I look forward to attending some sessions at the UC and speaking with some of the team to see if it will ever be considered outside of the Parcel fabric as this new tool is beneficial to all of us that need to verify and map legal descriptions for a wide variety of reasons.
Good morning,
I understand that the COGO Reader is designed for parcels. However, my organization is not responsible for maintaining parcels in the traditional sense (lots, subdivisions, tax parcels). My organization is responsible for maintaining zoning, future land use, special development areas, etc. using ArcGIS Pro. Given that the Parcel Fabric can manipulate the polygon geometry, this is not well suited for individuals that need view the mapped legally described boundaries as they truly are. Nor is it beneficial for organizations that have a need to run spatial queries against these polygons (E.g. to determine the FEMA flood zone) as doing so may generate false negatives or false positives, adversely impacting the development and other processes, costing customers and staff valuable time and money.
The point being made here is that this is an opportunity for ESRI to provide its customers with a useful/ time saving tool in the simplest way without forcing them to implement something that they may not need/want (prior experience with parcel fabric has taught me to be very leery of it). We are simply asking for a tool that can read and map metes-and-bounds legal descriptions without having to develop a fabric and all that entails.
Thank you
@AmirBar-Maor I frequently work with historic data while doing title investigation. The results might be used for an overlay and do not need to be incorporated into a larger cadastral dataset. I have punched in adjacent parcel descriptions to a subject parcel just to add context and compare boundary alignment between descriptions with no need to permanently maintain those additional boundaries. I recently worked through multiple versions of the same description and did not need all of them so I drew them into a temporary working file as the concept was refined. Having to push those into a Fabric dataset as I worked would have been unnecessary. I worked in local government and see the benefits of the Parcel Fabric to that industry but other industries use cadastral data without needing to maintain that sort of large combined cadastral dataset. I am going to be at the UC and might find some time to sit down with someone to discuss it.
@AmirBar-Maor
We do use the Parcel Fabric, but I would much prefer that COGO Reader did not have that as a prerequisite. I often plot legal descriptions from deeds on a temporary layer.
I agree with other people's comments. I work for a water district that has no need for creating a parcel fabric because that's not our line of work. Having said that, we do process legal descriptions on a regular basis, and it would be great if we could use COGO Reader's capabilities to read / OCR a document and have it create geometry for us. As a professional land surveyor, I can assure Esri that having a tool like this would present ArcGIS in a new light within the survey industry. Esri, please give this idea consideration for an upcoming version, hopefully sooner rather than later.
Same in my work. Don't have a need for a parcel fabric, but it would be very helpful to have this tool work with the Traverse tool to read legal descriptions and create geometry from it.
This could be useful or creating polygon and line easement records.
This webinar will be dedicated to COGO Reader.
We will also show how easy it is to migrate your existing data to the parcel fabric (it only takes a few minutes)
You are welcome to join
https://www.meetup.com/esri-parcel-fabric-meet-up/events/308788324/?eventOrigin=group_events_list
esri's cogo has always been a separate tool so why is this reader enhancement being deployed differently?
for the "required" parcel fabric, here we go again?
Migrating Data From ArcStorm or Map Librarian (Coverages) to the Geodatabase
and,
Arc/Info
https://www.loc.gov/preservation/digital/formats/fdd/fdd000284.shtml
@BillFox
We implemented and released the COGO tools in ArcGIS Pro (like Traverse and COGO enabled feature classes) before releasing the parcel fabric. That was done in part because we know that COGO tools are used outside of land records to create geometries from measurements.
For parcels (Land Records /Cadastre) this is the evolution of esri technology:
The parcel fabric offers many advantages, some of which are:
Coverages and ArcStorm are examples of great technology for that time. We also get nostalgic for a good BUILD and CLEAN 🙂
We do not prevent organizations from managing their land records outside the parcel fabric, but we consider those types of solutions as custom solutions. Most customers, however, prefer COTS and configuration over a custom solution.
If you are attending the UC we will love to talk with you in person.
not this year, but that made me remember this from a few years ago:
..."Machine learning might offer additional opportunities... "Alexa: enter my traverse" Am..."
We actually thought about that. You have providers like Google, Amazon and others that will turn voice to text, but they all require sending your data to the cloud and a paid subscription.We also experimented with AI, including the leading players, and found out:
That said, I agree - AI/ML will offer some opportunities, and we have implemented some parcel fabric capabilities with the ArcGIS Pro AI Assistant (not released yet).
If you wonder how difficult it is to migrate to the parcel fabric, this short video will give you an idea:
@BillFox @AmirBar-Maor "You have providers like Google, Amazon and others that will turn voice to text, but they all require sending your data to the cloud and a paid subscription."No need for that, tools like Whisper can be run on nearly any modern machine locally and produce great results. Check out GitHub - Purfview/whisper-standalone-win, GitHub - kaixxx/noScribe, GitHub - CheshireCC/faster-whisper-GUI for example.
@SimonSchütte_ct
Thanks for sharing.
Do you use Whisper to enter metes and bounds descriptions?
I ask because:
Since COGO Reader can process a deed faster than reading it outload, I don't think that's a direction we'll be exploring anytime soon
@AmirBar-Maor I use it to collect data in the field. From the auto-transcription, data can be pulled easily. Different use case, but just wanted to point out that not everything has to be linked to the cloud.Maybe I´ll write a post on the topic over in a dedicated thread.
I totally agree! It would be very helpful for users to use COGO Reader in other types of metes and bounds polygons.
Cogo reader is great. Please make it available outside of the Parcel Fabric because users find it more efficient to "pre build" data in a file geodatabase prior to adding data into the authoritative data set. When we are redrawing a large area to improve spatial accuracy we will do this in a separate file geodatabase prior to committing to our final database. There is lots of fussing with data that is best done in a separate (non-fabric) work space.
I would also like to have the Cogo Reader available outside of Parcel Fabric. I work in a County appraisal district. Using Replication in a disconnected environment, our office exchanges data with the local City office. Our data is used in processes throughout their office. We cannot migrate to Parcel Fabric without breaking the replica which is not an option. We also cannot force the City office to migrate their data.
Please allow COGO reader to be available outside of the parcel fabric. My office routinely draws special assessment district boundaries, easements, and stormwater route/courses. We also have interest in historic parcel descriptions as they relate to our easements (drawing the old parcel boundaries in order to know where to place an easement). It seems like the COGO reader is a tool to populate a traverse, which we can already do in Pro. Allowing us to use the COGO reader in Pro would save me and my technicians a lot of time.
Pretty please with data-sprinkles on top!
I was so excited to see the COGO Reader, and so disappointed that I can't use it because I have no need for parcel fabric. Please don't tell me how easy it is to use parcel fabric. I do not maintain parcels! That is done by a separate group. I read legal descriptions for proposed annexations and subdivisions. I have no need for parcel fabric because I do not edit/maintain our parcels.
Hello @EllenEndebrockCOM
You will be happy to learn that the parcel fabric is used for 'parcels' in the broader sense. This means it is also used to maintain simultaneous conveyances (subdivisions, condominiums) and administrative boundaries (for annexations).
There is also functionality that will help you perform annexation workflows where land is being transferred from one administrative boundary to another (city/county boundaries, special districts etc.)
In the future, we plan to expose COGO Reader as a web app for parcel fabric users. The parcel fabric uses simple feature classes. It is a data controller (just like geodatabase topology) - so minimal effort to migrate your existing data.
If you "bring" your data to this meetup, we'll walk you through the process: https://www.meetup.com/esri-parcel-fabric-meet-up/events/308790854/
Hi @AmirBar-Maor
Is there a time frame for exposing the COGO Reader as a web app? Do you have any more information regarding this? Thank you.
@GordonCourtney
We are unable to provide a concise timeline at this time. Not in the next year.
My organization also does not use Parcel Fabric, but we would use the COGO reader in ArcPro. Even better would be to add it to ArcGIS for AutoCAD!
Please add ability to use for non parcel fabric users.
I have responded to many of you on this thread and never receive a response. I invite you to read a blog I just posted on our community site.
https://community.esri.com/t5/arcgis-parcel-fabric-blog/broccoli-cogo-reader-and-the-parcel-fabric/ba-p/1663797
"Thank you for taking the time to read my thoughts!"
Connectez-vous pour publier, suivre du contenu, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
