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.
@DanielStone Yes my legal descriptions are very lengthy at times easements, right of ways, drain agreements, leases etc. We probably process between 20-50 conservation easements a year. The tool I was using was in ArcMap and a plugin for that. It allowed for COGO to read the description and the users to click on the meets and bounds and distances and that mapped them in Arc. We then take these and produce maps for staff and to update our open data portal layers. I worked with ESRI on a project to replace our existing tool about a year and a half ago using EAP funds. The existing tool seems to be working well, however needing to set up a parcel fabric, etc. instead of just maybe a file geo-database to store the information is a bit cumbersome.
This would be an amazing change! I run many legal descriptions and none of them are inside a parcel layer or fabric. The current model makes it very time consuming and honestly annoying to have to set that all up to use the cogo reader.
What this boils down to is that ESRI wants people to use the parcel fabric, and some of us just don't want to. Honestly, for the handful of times I have a complex legal description, it's simply not worth the effort for me to implement the parcel fabric for my features and workflow. Perhaps my successor will feel differently.
I guess to put a point on my question, we haven't converted to the 'new' user types yet and can't. If a Creator with a Pro Standard or Advanced add on is trying to do this Workflow on PF Services, in Pro it would let them? We are doing our Pro licensing through AGOL, the Portal where the services are would be a 'viewer' and the AGOL login, where there is no data or service, would be a creator w/ add on.
@EllenEndebrockCOM
We do some of that as well. I forgot about that. We do a lot of 'proposed' things that aren't always permanent.
To add to this, I'm often asked to verify legal descriptions. I'm not permanently mapping them, just using the Line Notes to draw them and make sure they match our geometry. I suppose I could create a dummy parcel fabric just to use this tool, but that seems needlessly complicated. I only get really complicated legals a handful of times a year.
For the editing question, I think what was making me think more licensing was required was addressed in 12.0(and 11.5 patch) for us. The ability to make basic edits without the license that Trace and UN was rolled in to changes things, along with Professional(desktop Standard) and Prof Plus(desktop Advanced) being able to edit parcel fabrics. We haven't converted our Pro/Desktop licenses to the new types yet. Do you know if the Standard/Advanced license equivalents honor the same rules outlined here? arcgis-enterprise-functionality-matrix-current.pdf Our users with 'advanced' licenses are still considered 'creators'.
@DanielStone
An example of this would be a Permit or Lease area inside of a parcel. Our Permits and Leases can and do overlap with each other and sometimes could even be covering multiple parcels. Easements spanning multiple parcels are also what we work on. We don't really care too much about the 'parcel' portion of parcel fabric as we don't manage parcels, we manage things on land we own.
These layers exist in an EGDB and are edited via direct connection to the database using traditional versioning. My understanding is, for us to publish those layers to ArcGIS Enterprise we would need an Enterprise license for parcel fabric, is that not correct? I believe we would also need an extension (that we also have very little use for) for every user to be able to edit the 'parcel fabric' enabled layers via branch versioning. Perhaps the paywall isn't on the Pro side, but it certainly is on the Enterprise side. My users that do these workflows really do only care about the 'drafting' portion of Pro. This would be useful for them to do their drafting workflows to get things into our EGDB or CAD.
Like many others have said, we don't manage parcels that would lend to the concept of parcel fabric. We have a lot of legal descriptions that are not parcels or whole chunks of land. Locking this tool behind an irrelevant Parcel Fabric paywall is unbelievably short sided and sloppy on ESRI's part. Forcing entities to buy a whole platform they do not need to use this drafting tool is silly.
@DanielStone I understand wanting to try to have people migrate to the parcel fabric where applicable or where there is desire by the user. We are not however being given any real reasons why the tool could not be used outside the fabric by those people who do not wish to use the fabric for whatever reason.
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!"
Please add ability to use for non parcel fabric users.
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!
@GordonCourtney
We are unable to provide a concise timeline at this time. Not in the next year.
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.
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/
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.
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 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.
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 totally agree! It would be very helpful for users to use COGO Reader in other types of metes and bounds polygons.
@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.
@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
@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.
If you wonder how difficult it is to migrate to the parcel fabric, this short video will give you an idea:
@BillFox
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).
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 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.
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
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
Melden Sie sich an, um zu posten, Inhalte zu folgen und mehr. Neu hier? Kostenlos registrieren.
