Latest Contributions by AmirBar-Maor

@JasonFuller  We appreciate your candid and direct feedback. When we developed the traverse tool in ArcGIS Pro we had to choose between 2 ArcMap traverse tools as well as the ArcInfo way. From your perspective, it seems like we chose the wrong one. We understand that the ArcMap COGO Traverse tool is more explicit and relies on fewer key shortcuts, but it also suffers from: Required a lot of mouse clicks, which is not efficient Requires 2 hands If the app crashed or you forgot to create the features you would lose your work. We have plans to develop something more explicit for those who want more explicit UI and a sketch, but that is not high on the priority list. If you see performance issues for creating issues, we recommend that you look into them regardless of the traverse tool. Migrating to the parcel fabric is actually easy.  Where do you see the challenges? How can we make traverse data entry easier? it's not by trying to improve your data entry speed but by eliminating the need to enter them. In the 'near term' we will release 'COGO Reader'. A tool that uses OCR and extracts all the courses from your deed. It will be part of the parcel fabric functionality and will focus on US deeds containing 'metes' descriptions.     ... View more

@-_Ashley-B-Potter_-  Thanks for the explanation. The purpose of "Shrink to Seed" is to be able to preserve the parcel attributes, modify the line boundaries, and then use 'Reconstruct from Seeds' to create it again. If you manipulate the boundary lines such that they do not close, the parcel cannot be reconstructed (but you can always use undo). It would help if you could please include some screenshots to make sure we understand your situation correctly.    ... View more

Implemented with ArcGIS Pro 3.5 ... View more

@AbigailSmith18  ArcGIS Pro 3.5 will display the misclose direction and distance: Tip: you can always right-click to copy this information for 'safekeeping'.   ... View more

@NabilDroby1  thanks for confirming that the misclose as X & Y is not crucial. From our perspective, adding information that cannot help only clutters the UI and adds confusion. The direction and distance, on the other hand, can help identify the course in which the blunder might have occurred. ... View more

Hello @NabilDroby1  With the traverse pane in ArcGIS Pro you can set the start and closing location. You can define the location by snapping to an existing point or right-clicking on the map and entering the coordinates values.   Use the traverse settings to enter Set your desired closure tolerance.   You can also consider using the options to force closure or you can simply enter an asterisk ('*') after the last distance to force it (even if you're outside the tolerance. The traverse courses are numbered using Pro 3.4.   Do your deeds include coordinates? If yes you can also start by entering that location as a point. We also recommend reading the help documentation and/or taking a course to learn how to maintain parcels in ArcGIS Pro efficiently.     ... View more

See the workflow above. You cannot use the geoprocessing Truncate table on a feature class that participates in a topology. ... View more

The parcel fabric uses the standard geodatabase topology. If you see any bugs related to geodatabase topology like validation or error inspector please submit a case with technical support. You are welcome to DM me with your case number. ... View more

@MyEthiopia  I recommend that you contact technical support and have them look into your specific configuration (DBMS, Enterprise, Pro) and the workflow. Many things might have caused it and we haven't seen that before. Did you calculate a field on a lot of features? could it be that your server timed out? Do you have any attribute rules that might have failed and caused it? Did you check your DBMS logs to see if it failing? ... View more

If anyone else is following this thread and encountered that the geoprocessing tool 'Update COGO' does not recognize the feature class as 'COGO Enabled' here is the workaround. Instead of copying the data from the CAD layers to a new feature class append the CAD features to a COGO-enabled lines feature class. You can use these steps: If you are using the parcel fabric the line feature class is already COGO-Enabled. Else create a line feature class with the correct spatial reference and run the geoprocessing tool 'Enable COGO' Right click on the feature class and Export the feature class as a XML Workspance Document' (schema only).  Every time you import a CAD file use the geoprocessing tool 'Import XML Workspace Document' to create a new COGO Enabled line feature class (or an entire feature dataset containing your staging parcel fabric).   Use the geoprocessing append to append the CAD features to the COGO-Enabled line feature class. Steps 1 & 2 are only performed once. Steps 3 & 4 for each CAD file you process. ... View more

@kkoffi_crcjv  The right thing is of course to open a technical support case... For a feature class to be deemed 'COGO Enabled' all the COGO fields have to exist AND the all have to be 'required'. Could you please open the attribute table of the feature class that got created and hover over the field name? You should see all COGO fields as 'Required': Please also check that the feature layer properties show that it is 'COGO Enabled':   If they are not 'required'  that is why the Update COGO tool refuses to process them.  If it is not COGO Enabled the next step will be to figure out if COGO Enable fails or if they become non COGO Enabled by the Delete field tool. Please share your findings.  You can also welcome to DM me and send me your model so we can look closer. I   ... View more

@JasonBessert  Thanks for the clarification. That makes sense. ... View more

@kkoffi_crcjv  What is the error tooltip that you get when you hover over the "CAD Reduced Fields"?   Could you test if it works when you supply it the previous 'Output Feature Class'?   Can you check that the created feature class is indeed 'COGO Enabled'? ... View more