Latest Contributions by AmirBar-Maor

The COGO functionality in Pro (Traverse tool) is available in every license level. The type of geodatabase (file, enterprise) is one of the key factors to determine the needed license level. The ground to grid corrections functionality is also planned to available for all license levels and is key when precise measurements are used from ground values. ... View more

Thanks Jeff. Good catch - they should be consistent. This happens because some of the fields are controlled by the parcel fabric and the other by editor tracking (if activated). And like you - I don't know that it matters much, certainly does not justify a schema bump. Amir ... View more

Hello Sandie, You'll be happy to learn that the traverse functionality is not complete and that there is a "method to the madness". Beyond the learning curve involved with working with a new software / tool, we are driven by customer feedback and ideas. Our suggestion to use the construct polygon tool or geoprocesssing tools such as feature to Polygon" is an interim solution. If you start your traverse with a curve entry you will have to provide it an orientation (in the direction field). We also recommend that you run the geoprocessing tool "Enable COGO" on your line feature class and then add it to your map to make benefit of the helpful symbology - it helps both data entry and comparing the deed to the traverse. For simple traverse entry by "non GIS experts" you can also try (try it live) the web app called "Parcel Drafter". Thanks for your feedback. ... View more

Hi Matt, The curve begins from the last entered course, use the Curve Overrides which are in this help document topic (scroll down) and you will see the methods in which the orientation of the curve can be defined (tangent bearing / radial bearing / chord bearing...). Enter the appropriate bearing in the direction field. The topic is copy-pasted (might not be formatted as nicely as the help doc) below:: Curve overrides Curves described on a plat or plan may not conform to a single set of curve parameters, such as radius and arc length. In the traverse grid, you can override the Bearing, Radius, and curve parameter fields (Arc Length, Chord Length, and Delta Angle) using the following curve parameter overrides: Override Keystroke Use in grid field Example Tangent bearing tb or TB Bearing 41-56-06-4tb (using quadrant bearing) Radial bearing rb or RB Bearing 41-56-06rb (using quadrant bearing) Chord bearing cb or CB Bearing 41-56-06cb (using quadrant bearing) Chord length c or C Arc Length, Delta Angle 25.01c Delta (central angle) d or D Arc Length, Chord Length 90-59-59d Arc length A or a Chord Length, Delta Angle 25.01a ... View more

Hello Matt, You can already specify right and left curves by entering positive and negative radius values in the traverse grid. If you COGO enable your line feature class you will also get good default symbology and labels in Pro. Read the help documentation and you will find many enhancements that will make entering a traverse even faster, like: Tangency is assumed (default) Use '+' or '-' to enter a 90 degrees angle Use arithmetic operators when entering distance units, no need to pull out an old calculator Use shortcuts for quadrant bearings Much more... Amir ... View more

With the release of the next generation of parcel management, Pro will have the capability to perform ground to grid correction as well as account for a different basis of bearing. The next release of ArcGIS Pro (2.1) will allow you to construct polygons from lines without having to retrace your lines. This is also be part of the core functionality of parcel management when it's released. Until then you can also use geoprocessing tools to generate polygons from selected lines. The traverse tool help document provides examples as well curve overrides for non tangent bearings (delta, chord etc.). Schedule: the parcel manager release date is kept up to date on the ArcGIS Pro Roadmap blog post. Thanks for communicating the gaps that prevent you from using ArcGIS Pro, Amir ... View more

We have documented how to replicate a parcel fabric as part of the 10.5.1 release. You can find it here: Parcel fabric replication workflows—Help | ArcGIS Desktop  Amir ... View more

The geoprocessing tool  "Enable COGO" add the fields as required and the geoprocessing tool "Disable COGO" does not remove those fields. All it does is makes the field not 'required' which means you can delete them. We are working on a script tool for migrating your existing COGO measurements to the new schema. JCamerano-esristaff Once Ground to Grid is implemented we will also pursue a tool to recalculate measurements from geometry. Until then you can use python for that. Thanks, Amir ... View more

The traverse tool in Pro 2.0 will allow you to enter COGO measurements, digitize a natural boundary and modify courses that were entered previously. It will not include ground to grid scaling correction, rotation correction for basis of bearing or ability to import traverse text files fro ArcMap. Please let us know if any of those impede your adoption of Pro.  ... View more

The original thread is from 2013, but it is hard to tell if it is the same or not because you might be using a different version of the software, different DBMS and many other variables could be different. Please open a case and we'll have a look. Your insight about the layer is very valuable. Thanks. ... View more

Please contact technical support to create a case for any unexpected behavior. Cases that are software bugs are reported to the development team. Thanks. ... View more

Hello Matthew, Thanks for the feedback. you can restrict the number of processed features for any geoprocessing tool using selection.  Another option is to modify the script. Here is an example: featuresSelected=len(arcpy.Describe(inputPolygonLayer).FIDSet.split('; ')) if featuresSelected>maxNumberOfParcelsToProcess:     arcpy.AddError("\n\n\nToo many polygons selected. Select less then {0}. \n\n\n Aborting.".format(maxNumberOfParcelsToProcess))     return None Amir ... View more

We can envision using: Different maps for different workflows. e.g. usually it is not the same person that manages PLSS, subdivisions, splits and merges, ownership and easements Each map can show the relevant parcel types. All maps point the same parcel fabric. ... View more