Latest Contributions by AmirBar-Maor

Thanks @SamMontoia1  I've also added 2 text fields on the parcels and lines to store the record names of the records that created and retired the feature.   It turns out that SQL Server requires the special "@" added. Since parcel lines don't have a relationship class a SQL Filter is used. For the 'CreatedBy' field on the Lines table: var RecordFS = FeatureSetByName($datastore, 'GIS.PF_Records',["GlobalID", "Name"], false); var guid = $feature.CreatedByRecord; var sql = "Globalid = @guid" var Record = First(Filter(RecordFS, sql)); If (IsEmpty(Record)) { return "---"; } return Record.Name; For the 'RetiredBy' field on the Lines table: var RecordFS = FeatureSetByName($datastore, 'GIS.PF_Records',["GlobalID", "Name"], false); var guid = $feature.RetiredByRecord; var sql = "Globalid = @guid" var Record = First(Filter(RecordFS, sql)); If (IsEmpty(Record)) { return "---"; } return Record.Name; In my case I wanted to see the record names in a label, and since labels do not support feature sets in Arcade, I had no choice but to add the fields and use attribute rules to populate them. In my expressions, 3 dashes  '---' are returned if no record name is found (e.g it's NULL).       ... View more

Implemented with ArcGIS Pro 3.4 ... View more

ArcGIS Pro 3.4 ... View more

ArcGIS Pro 3.4 ... View more

@MattSund  The reason organizations adopt the parcel fabric is because they want: Increase their efficiency Assess and improve their data quality Associate all features with the legal record (instrument) they originated from, making the data defendable. Improve their spatial accuracy Maintain historic parcels and parcel lineage ... We would love to help you. You can get in touch with our product manager @DanielStone or with your account manager. The workflow you describe is a core workflow of starting connection lines from the commencement point to the point of beginning (POB). That accounts for any rotation (aka Basis of bearing) and scale factor.  We call that 'ground to grid' correction and this is how to use it. You can also apply rotation interactivity to a group of lines or a parcel after building it. From your description, I can tell that you close your traverse, which means you are already stretching the geometry to distribute the misclose (using the compass method most likely). Assuming you stitch new parcels to existing parcels (alignment) you effectively stretch and bend geometries. That is not different from what the parcel fabric does. We understand that changing from ArcMap to Pro requires adjusting your workflows and it can be challenging.  You can prevent parcel points from moving by simply setting them to fixed. You can easily detect any line that has been stretched or rotated more than you want to allow it.  Your workflow explains why you are currently missing COGO dimensions on your lines which is a shame, because it sounds like you put a lot of effort of creating a nearly survey accurate cadastre, and good COGO values would allow you to run weighted LSA (Least Squares Adjustment) should you decide to evaluate and/or improve your spatial accuracy even further. ... View more

Thanks @MattSund  Are you currently using the parcel fabric? Are you using COGO Enabled lines in ArcGIS Pro? If you use the parcel fabric you can select the parcel polygon and then use the parcel select tool to select the boundary lines. We can also consider improving the 'select by trace' and/or offer another selection method. Would that work? ... View more

@-_Ashley-B-Potter_-  To delete a large number of parcels you can use the geoprocessing Delete Parcels. This tool is smart enough not to delete points and lines that are shared by parcels that are not deleted. It will also not delete any point that is either fixed or XY Constraint (this utilizes the field called 'preserve' on the point table). If you are using a file geodatabase you don't have to concern yourself with versioning, but if you are using versioning you'll have to decide if you want to delete the parcels in a child version, then review the changes before you reconcile and post them, or take the risk and running in the default version without the ability to roll those delete back. After every major change to a table (appending or deleting data) it is recommended to recalculate the spatial indices. If you have an enterprise deployment you probably have a nightly script / job that does that already. I hope this helps ... View more

TBD: 1. Is this idea only relevant to the unique map configuration posted by @MizukiKayano2 or is it also applicable for customers that use a separate layer for historic parcels? 2. What would be the performance impact of setting a definition query to many layers? Please add your comments to help us answer the first question above     ... View more

Thanks for the additional input @MizukiKayano2 . Other options to consider are: The use of Display Filters. Although they have to be applied to each layer individually. A python script that changes the layer definition (CIM) of all the layers in your map.   ... View more

@anna_garrett  If I understand you correctly you are concerned about the performance impact of having multiple maps in a project. The short answer is that it should not have any impact. A map in a project does not impact the performance until it is opened. So you can have a 100 maps in a project but only the one that is open impacts the performance. So just avoid having multiple maps open and drawing at the same time. I would put more attention to making sure each map is optimized: Layers use scale dependency Labels use scale dependency Avoiding too many layers Using definition queries that run on fields that are indexed and are not too taxing ...   ... View more

@melisahansen  We regard any solution that manages parcels outside the parcel fabric as a custom solution. We've made it easy to migrate any data into the parcel fabric and provide additional capabilities to make your parcel maintenance more efficient.  Organizations that want to have their own custom solution can use the rich ArcGIS Pro SDK for their custom workflows. Another capability we are currently working on to make you more efficient is the capability to OCR deeds and create features (with COGO values). Such capability will be limited to the parcel fabric. ... View more

@MizukiKayano2  Did you consider using multiple maps in ArcGIS Pro? You can have a map for LSA, a map for editing etc. ArcGIS Pro 3.4 symbology will allow you to turn on off specific symbol (for the unique value renderer), so if you have different symbol for historic versus current parcels you'll be able to easily turn on and off the visibility of current / historic parcels. Given the 3.4 enhancement, I don't think a new button is needed. What do you think?           ... View more

@LearnThenShare  The parcel fabric connection lines can be used to model any type of line that does not form a parcel boundary, yet has COGO measurements associated with it. We have seen it used by organizations to model things like: Connection lines from the commencement point to the POB Survey tie lines Road centerlines ... It is a business decision to have a 'Connection Type'. It might make sense if you want to be able to symbolize them differently, for example, or only show one type and not the other. I think (and I might be wrong) that most organizations do not try to differentiate between them because of the extra work it would require to maintain it and the little business benefit. IMHO keeping it simple is usually better. So this is your decision to make. I'll be happy if other community members chime in   ... View more

@Syvertson  I am happy it worked. When you have the time, it wouldn't hurt to run the geoprocessing Check Geometry on your feature classes to make sure they are valid. ... View more