Latest Contributions by AmirBar-Maor

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

Hi Jason,  Are you trying to merge two curves into one feature + eliminate the point between them? If yes try this: Make sure you have an active record, preferably of the record that created the curve. select the curves you want to merge Launce the merge tool and merge into 'Existing Feature'   Before Merge:   After Merge:   There is also an idea to interactively fix densified curves (by tracing them).   ... View more

@MizukiKayano2  LSA uses 'direction sets' as input so it's not that easy just to run a pre-process that flips lines. If you have 5 wrong directions + a few true blunders I would not expect LSA to converge and as @TimHodson has suggested, it would be best to identify and fix those blunders before running LSA. Then you'll be able to catch the 'real' outliers. A simple Attribute Rule calculation rule can detect and fix those blunders for you without any extra user work: the rule can either flip the geometry (SHP field) or add/subtract 180 degrees from the 'direction' (direction field). Where do those '5 blunders' come from? I suspect from an external source like a digital submission process. If that is true - why not improve the digital submission process? You can either reject lines that have the wrong direction or fix them as they come into the system?     ... View more

@MizukiKayano2  One of the uses of LSA is to detect blunders. Having the wrong geometry, even when flipped, is wrong, and ignoring it can cause downstream effects in other areas. So it would be best to fix those bad geometries.  What's the best way to correct the geometry by flipping them? Use the geoprocessing tool Flip Line Use an Attribute Rule (calculation) on the SHP field.   ... View more

Do you use the attribute rule 'DIRECTION MUST MATCH WITHIN' that is shipped with the parcel fabric before running LSA? What would be the tolerance to consider a line as 'flipped'? (+-180 +???)   ... View more

@MarkWasdahl1  If you export to a feature dataset in a file geodatabase you are constrained to the spatial reference of the feature dataset. But if you export to the root level of the file geodatabase you can use any spatial reference. You can always keeping tidy by creating a feature dataset that matches the spatial reference of the source data and then export to it. ... View more

@MarkWasdahl1  It's great to hear you solved the issue. I would recommend not to use SHAPE files. They will densify your true curves, truncate long field names, have no concept of domains and the list goes on... Instead always export to a file geodatabase. If you have corrupted your true curves you can either repeat the process using a file geodatabase or use the geoprocessing tool Simplify by Straight Lines and Circular Arc (AKA 'SLACA'). Just make sure to supply all polygons and lines as input in the same run to avoid creating a topological mess.   ... View more

@Michele  Data Reviewer has a community place - https://community.esri.com/t5/arcgis-data-reviewer/ct-p/arcgis-data-reviewer.  It includes videos and useful resources and I am sure they can answer your question. While some Data Reviewer checks leverage attribute rules, most Data Reviewer checks do not.  ... View more

@Michele  The first release of the Highlight Gaps and Overlaps contained some bugs that we fixed in later releases. This included allowing the tool to work on non-parcel features. Since then we have also enhanced the tool to work on multiple parcel layers, check between different parcel layers and added a geoprocessing tool for automation. The parcel fabric is designed to manage 'parcels' in the broader cadastral sense. Those are often referred to as the 3 'R's = Rights, Restrictions, and Responsibilities. They are used to manage things like ownership, leases, encumbrances (easements), zoning ... as well as administrative parcels. If your data falls into one of those categories you'll be happy to learn that migrating your data to the parcel fabric is an easy process and that any editing tool you already use can be used against the parcel fabric + (as you have found the hard way) many more useful tools can capabilities. Apologies for not locking that tool in our first release. We did not expect non-parcels users to find and utilize it. ... View more