Latest Contributions by AmirBar-Maor

@DeanAnderson2  Future plans: Ability to create a version in Tasks without having to select the version in the data source tab in the Contents pane. This would help to create a new version and switch to it using tasks. We will also explore how you can enter a string once and use it to: Create a new version and switch to it Create a new record. You are welcome to enter it as an idea Amir ... View more

@ThijsBriggeman_Tensing  Did you consider using the geoprocessing tool 'Split Features'? If you want to see the vertices you can: 1. Start creating a new feature and press down the T key  2. Create a layer that shows you the vertices. Toggle it on / off as needed. This is how you can create it in the symbology pane: Amir ... View more

@Syvertson Maybe the solution is to identify the cases in which the field alias is not respected. Can you please describe those?  ... View more

@DenverBilling  The vertices actually help with keeping parcels from different types remain coincident. Curves should not get densified. Could you please share the workflow that causes them to get densified? ... View more

@RonSantos @DucksInaRiver  You don't have to use a parcel fabric or a COGO-enabled line feature class in order to use the traverse. If you use a polygon or a line feature class that is not enabled the COG attribute you enter are not saved. This means that: The COGO dimensions you enter are not saved as attributes COGO dimensions are not displayed as labels as you enter each course You have to remember to export your work to an ArcMap traverse text file if you want to be able to modify it in the future. But that will add work since you will have to know which feature to delete. Your work is not associated to the legal document it came from. Misconceptions: The new parcel fabric in ArcGIS Pro uses SIMPLE FEATURE CLASSES FREE when you use ArcGIS Pro Standard /Advanced Supports true curves / spiral curves Works on a file geodatabase, mobile geodatance, and Enterprise geodatabase using web services The new traverse allows you to enter a natural boundary while in the traverse The new parcel fabric supports a 'bounds' legal description: no need to enter boundaries that bound your entered parcel (duplicate lines) When using the parcel fabric you will be able to tell which lines were 'ENTERED' which were 'FROM GEOMETRY' (inveresed) and which were 'CALCULATED" (for example when you divide a line). Why exporting a traverse from a selected polygon is not a good idea? The polygon represents the closed traverse after the misclose has been distributed. The dimensions will have the original COGO + a portion of the misclose  If the appropriate Ground to grid correction is not applied you might export grid dimensions (not the original 'ground') You can only export the correct dimensions when entering the traverse, if you forgot to do that it will be too late as you have no COGO stored as attributes You cannot compare the geometry to the COGO dimensions to find blunders. We have layers and attribute rules to help you identify those.   The workflow to create a polygon outside of the parcel fabric while keeping your COGO is to enter the lines using a GOGO enabled feature class and then press the Construct Polygon editing tool. If you use a parcel fabric the workflow started with creating the Active Record which is the legal document (deed / plat) from which you take your measurements, enter a traverse, Create a parcel Seed and Build. Each line and polygon created will always be associated with the legal record that created them. The COGO Area will be calculated on the calculated area field + the misclose ratio and the misclose distance. If you used a ground-to-grid correction those are also saved on the scale and rotation fields (lines). Spatial Accuracy? Don't get me started 🙂 The parcel fabric is designed to help you evaluate and improve your spatial accuracy using the state-of-the-art Least Squares Adjustment. If you have any surveying / geodetic background you will love it. If not - we made it simple for anyone to use. This includes free network adjustment (no need for control points) ar a weighted constrained LSA.   From the hundreds of users that COGO 'for a living' in ArcGIS Pro, we know this is the fastest and most efficient traverse that ever existed. If you think a feature is missing in ArcGIS Pro, please submit a new idea. If it gets enough votes the Pro team will consider implementing it.   BTW - we know from users that it usually takes a few days to a week to get used to working in ArcGIS Pro. But once you get used and start to discover all the editing efficiencies you are likely to never look back. If you feel like you need training, there are plenty of options (from a 'learn online, tutorials, .. to an 'in class' course)           if you try to modify them in the future you will have to either remember to  ... View more

Hello @DucksInaRiver  Since this post was created hundreds of 'COGO editors' has been providing great feedback that is reflected in the software improvements. This post is very old and does not reflect the current release of ArcGIS Pro. To your questions: 1. You can use the traverse tool to enter a polygon and save a traverse text file. The polygon can contain true curves. Why do we recommend using COGO Enabled lines? when using lines the COGO measurements are saved as attributes. If a mistake has been done they can be traced into the traverse grid and modified. You also get to see the COGO labels as you enter the data. 2. The traverse misclose ratio, distance, and COGO area are displayed regardless if you are using lines or a polygon to enter your traverse.   To find more information please read the help documentation and/or view the parcel fabric meetups/blogs that relate to entering a metes and bounds description. Amir ... View more

@Lebowski  This us the expected behavior. To understand why vertices appear when validating topology you can learn more about it here: https://pro.arcgis.com/en/pro-app/latest/help/data/topologies/topology-in-arcgis.htm http://downloads.esri.com/support/documentation/ao_/J9880_ArcGIS_CoordMgmt_Geometric_Processing.pdf https://proceedings.esri.com/library/userconf/proc17/tech-workshops/tw_228-608.pdf   These vertices often help prevent small gaps and overlaps from appearing. In other words - they help maintain the spatial integrity. Even in ArcMap we added vertices (cracked) any location of a 'line-point'. Why are you trying to get rid of this vertex?  Thanks, Amir   ... View more

@AlanStearns1  That's great to hear. We always welcome ideas about how to enhance the parcel fabric capabilities. @jcarlson can attest to that 🙂 Also - make sure you really need 'Geodatabase subtypes' - those should only be used if you have different topology rules or attribute rules. If they all have the same rules it is simpler to just use a field called something like 'MyTaxParcelType' and use it for symbology, feature templates etc. Good luck Amir       ... View more

In ArcGIS Pro you do not have to "declare" that you start a new parcel. A typical workflow might look like this: Create a new Active record Create the boundary lines using the traverse tool, or any other editing tool such that it forms a closed loop Create a parcel seed Build Active Attribute the new parcel Typically, the new parcel might be used to Clip and retire parent parcel (split metes-and-bounds), or you can set any parent parcel(s) historic using the 'Set Historic' command. ... View more

@MeleKoneya  This capability has not been implemented yet. If interested, please vote on this idea: https://community.esri.com/t5/arcgis-pro-ideas/hard-code-a-definition-query-clause-when-using/idi-p/971527   Amir ... View more

@anna_garrett  Thank you for submitting a ticket. In the future, as you encounter a 'data specific' issue, you can simply reduce the amount of data by selecting the parcels in your map extent and then running the geoprocessing tool 'Copy Parcels'. It will create a small file geodatabase with an identical schema of the selected parcels. As for this specific error message, the error message is not always correct - so turning off the 3rd dimension might not solve this problem + might cause new issues.       ... View more

@Paul_Christensen  We will need to look into your data to reproduce and understand the issue. Please submit a technical support case and provide your data. We are now all busy getting ready for the user conference, so it might take a few weeks until we get a chance to look into it.   ... View more

These types of error messages are usually very low level coming from the geometry engine or geodatabase. By the time they trickle up to the error message they are vague. We can only fix such cases if we can reproduce the issue. The good news is that we have a customer who provided us with a reproducible case and that we have fixed it for the next release of the software (3.1). We will examine if the fix can be ported back to ArcGIS Pro 3.0. Our request: please submit bugs like this to the technical support   ... View more

@JoeGuziStarkCountyOH  Assuming you checked the Validation capability when you published, you should be able to see the validation REST API exposed on your server:   The first thing I did was to verify that the Evaluation service REST API supports a selection set. It does 🙂   To use the geoprocessing tool Evaluate Rules you will need to supply the 'Feature Server' URL of your published map. It will end with '...FeatureServer' and will look like this: Also notice it is set to Calculation rules. Now you can run it on a selection for the 'default extent' (all of the data). To see the update (another 'gotcha'), you will have to select the version in the contents pane \ data source tab and then hit refresh. I have verified that only the selected features are updated. However, getting a 999999 error is always a BUG.               ... View more

@JoeGuziStarkCountyOH  Last try 🙂 I've created a new batch rule and it is working. I think the reason it is failing is because you might not have the error layers in your map. Here are a few steps: 1.  Before publishing the map make sure to add the error layer to it   2. Once you have published your map and added the parcel fabric to a new map, right click on the parcel layer and add the error layers to the map.    3. Open Error Inspector and switch from the parcel fabric controlled topology to the Attribute Rules   4. You can check the Batch Calculation and evaluate the rules. It worked for me. I hope this works for you too     ... View more