Latest Contributions by AmirBar-Maor

@HeatherHanson  That does not look right! Are you able to upload a few polygons to this thread and/or open a technical support issue? It is also a good practice to run the geoprocessing tool 'Check Geometry' or 'Repair Geometry'. I am curious if that was really a true curve and why it transformed into a straight line. Does this happen in more places? ... View more

@ScottSweet2 Mahalo for sharing a deed from Hawaii. There are a few things that prevent COGO Reader from succeeding: Scan quality - the document is poorly scanned and there are many text extraction issues (OCR). Use of north azimuth - is this common in Hawaii? AFAIK all other states use quadrant bearings. The word 'Thence' is not used Once those 3 issues were addressed, and assuming I haven't made a mistake, the misclose was 0.5'   ... View more

@ZachBodenner  Interesting idea! Would you expect the parameters to be populated or not? Would you expect the tool to be embedded? Or should we pop up a dialog to let the task designer make those decisions? For this to work, and the command to be enabled, does task designer has to be open and a step be selected in a task? ... View more

@HeatherHanson  You can use the move, scale and rotate tool on your entered lines after you close the traverse. Since all the lines are associated to the Active Record, you can press the 'Show only Active' if you only want to see the new lines and/or use it to select all the features in the active record. The parcel line feature class is just a simple feature class.  In order to align the new entered traverse you can start by using the move/rotate/scale tool if it is really far off. If it's within a reasonable tolerance you can use the Align Parcels tool, and if you add 2 links manually it will use those to transform the new parcels to the existing one. Before you try to align your traverse create a parcel (create seeds, and build). If you need more control over what moves to what, you can also use the Align Features tool. I hope this helps, Amir ... View more

@ScottSweet2  - the link to the pdf file you provided is not reachable. Can you please add it as an attachment instead? ... View more

@SamMontoia1  To your question: "Ideas of how to add to the training/testing data to the CogoReader's understanding may belong in a different place on this community.  I guess I wish I knew how I could contribute; ..." You are already contributing. THANK YOU! We could not test all the permutations in all the states, so this is very helpful and helps us improve COGO Reader. The best way is to submit a technical support case with the deed attached and the information you provided in this thread. In future releases,  we are thinking of letting you add your keywords ... View more

Hi @Hedstrom_Jeff  The Attribute Rule I mentioned does not exist. It needs to be a calculation rule. The parcel fabric assumes that the direction of the line (geometry) and the COGO direction match each other. If one is +- 180 degrees to the other (+ some tolerance), the calculation rule can either flip the geometry or flip the COGO direction attribute. Which one is would you flip? (geometry or COGO direction) I can help with creating such a rule ... View more

@DucksInaRiver  Migrating to the parcel fabric is easy, but to make it even easier you I have zipped the map package with the georeferenced plat. I'll find how to upload it later today   ... View more

One idea that comes to mind is: Adding a field, for example, called 'DeleteOK' Adding an Attribute Rule constraint rule that is triggered 'on delete' operations and only allows features to be deleted if they have $feature.DeleteOK ==1 This will prevent any feature from being deleted accidentally as you have to set DeleteOK to '1' in order to be able to delete it.   Would this work?   ... View more

@DucksInaRiver  I had time yesterday to look into it. Apologies for the wait time. This is a challenging plat:  No coordinates or control point to tie to making it hard to georeference No surrounding parcels to tie to Poor spatial accuracy Natural boundaries without COGO dimensions --> no misclose information to detect blunders Missing COGO information   For example:  There is a missing course  in this location    But I assume you are used to that reality in VA. When you use parcel fabric lines to enter the data, you can switch to digitizing mode which allows you to enter natural boundaries by digitizing them. You can even prepare different boundary line types to distinguish between natural boundaries, road frontage, side lots lines etc. I decided to start with Parcel A with the point marked as '1', encountered a missing course marked as point '2', and never reached the water with the course of 470' (+/-) marked as '3'.     Maybe the course going to the river should have been 870' instead of 470'?   You can see in the screenshot about that when you use lines to enter the traverse: Your edits are saved as individual features - making it easy to stop, save edits and return to it at a later time. Labels show you the COGO attributes you have entered - making it easy to compare to the georeferenced dimensions on the plat. You can switch to digitising mode for natural boundaries. You can maintain different boundary line types, which have an impact on zoning. When you use the parcel fabric you have additional benefits in the context of entering this plat: All the features you create (boundary lines and parcels) are associated to the 'Point Of Rocks Park' record. You can filter the data to only see the features associated with the 'Active Record' = 'Point Of Rocks Park' record. You can use the Align Parcels tool to align the newly entered parcels with the surrounding parcels / subdivisions. You can maintain historic parcels. You can run a LSA to detect blunders in your COGO. I hope this helps Amir         ... View more

Ideas for ArcMap and Attribute Assistant will not be implemented ... View more

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