Latest Contributions by AmirBar-Maor

Hi Jeff, This is an interesting idea. We usually try not to alter the recorded COGO dimensions and instead update the 'Rotation' and 'Scale' fields on the lines.  The Ground to Grid correction can yield similar results but it would not change the COGO fields, and you might already be using it for the real ground to grid corrections. Is there a case where you would want to use the Rotate tool and NOT update the COGO dimensions? To be consistent, should the Resize tool update the linear dimensions?   ... View more

@SamMontoia1  Thanks for the quick response. When developing and testing COGO Reader we tested with deeds from many states, but not all them, and surely not with enough deeds from Colorado. I've created a bug for missing out on those directions. The words 'bears' and 'running' are throwing it off. If you remove those words it will pick it up correctly, including the connection line:     ... View more

@SamMontoia1  The first release of COGO Reader does not support PLSS. Thank you for attaching the deed - it let's us see that it failed to read cardinal directions ('running north', 'running south'). We consider COGO reader missing reading the directions as a BUG and recommend opening a technical support case for those.  Is your idea about pointing out to where COGO Reader has failed? Like selecting the text, right clicking and choosing 'Add as direction' or 'add as distance'? Or is the idea about teaching COGO Reader that 'running south' means 180 degrees (north azimuth format)? ... View more

@DucksInaRiver  If you can share your plat we can record a video showing how to enter it.  Please also supply the spatial reference and the combined scale factor.  We will also show how easy it is to create a new parcel fabric and migrate to it (it takes less time than entering a plat) ... View more

@ThomasHoman  In that case, this might also be a good source: https://pro.arcgis.com/en/pro-app/latest/help/editing/direction-formats-for-editing.htm   ... View more

@ThomasHoman Thanks for sharing. Dumb question... Did you create it to use with paper maps? Hang on the wall to get the new user used to the quadrant bearing? or as an image to insert in a layout? Other? ... View more

When the data is copied from a file to an enterprise geodatabase, the table names used in the expressions should be swizzled to the new names. If the rules use table names that are not available in the source and target, I would disable those rules. If that approach fails, you will quickly find out. BTW - if you want to create an empty schema quickly, instead of using delete rows, you can export an XML workspace (schema only), delete the data, and then import the XML Workspace to create an empty schema. ... View more

If you are using an enterprise deployment (feature services) and would like to see the name of the record in the popup, you will need to update the name of the relationship class with the name of the relationship between the 'layers'. You can find that name in the layer properties 'Relates' tab:   Once you have updated the pop expression with the relationship name you should be good:         ... View more

@RobertChaney  If I understand correctly, you want to hide the trailing zeros if the distance ends with '.00' . Is that also true for Radius and ArcLength? The label expression we ship with the software has many options you can tweak. This could be another option. If you think many other organizations will want that please submit an idea for it. Thanks, Amir ... View more

@BobNoyes  In general, we recommend performing large data manipulations on a file geodatabase. Why? Performing such manipulations in a named version increases the feature table size and might not perform as fast. The reason you cannot use the Truncate tool is because the feature classes participate in a topology. If you want to run ist faster start by running the geoprocessing tool Disable Parcel Topology and once you are done with the data manipulation, run Enable Parcel Topology. You will notice that every command runs faster when the topology is turned off as there are no need to update dirty areas. The price to pay for that is having to validate the entire data extent again. It will create a dirty areas for the entire data extent once you enable the toplogy again. Personally, I would: Copy the data to a file geodatabase and save a copy as backup Run Disable Parcel Topology Run Truncate table Append the updated data Run Enable Parcel Topology Perform Quality Assurance Make sure there are no open versions with pending edits  Delete the feature dataset containing the old data on SQL Server  Copy and paste the feature dataset with the updated data to the enterprise geodatabase (SQL Server) Enable versioning  Open the publication map Overwrite the published services Test  Such an operation should be carried out in the test environment first.   I hope this helps. ... View more

@DianeBaker  We understand why this can be frustrating and it is concerning that other mappers have encountered it. Unfortunatly I was not able to reproduce the issue 😞 You write that this happens 'on occasions' - can you provide any hints?  Always with curves on exit direction Does this happen after the traverse closes? Does this happen with traverse that have multiple curves? just one curve? Do you use ArcGIS Enterprise? Or a file geodatabase? If you enter an asterisk ('*') in the direction to force tangency again, does the cell become editable again? Or is the cell completly lockd out? Any other hints are greatly appreciated. If you can reproduce the issue, please contact technical support and DM us with the case number. ... View more

Thanks for the clarification  @JesseCloutier  The idea is 'open' for voting again @CathyAppleton  ... View more