Latest Contributions by AmirBar-Maor

@jcarlson  Very interesting idea and use of group templates for parcels! It will have to be specific to Lines in a group template that are both COGO Enabled. Q: What would happen to attributes that are your lot lines and are also on the ROW lines? Should these be copied if the fields match the name and type? Any fields that do not match will not get copied over. Q. Any attribute rules that conflict with copying the COGO values will take precedence - is that OK?   ... View more

@Eroberts  Instead of populating the record name (control #) on the parcels, you can add fields and attribute rules that will populate the record name. To populate the Record the created the parcel you can use this Arcade expression (just change the table name):   var Record = First(FeatureSetByRelationshipName($feature, 'GIS.RecordHasParcel', ['Name'], false)); If (IsEmpty(Record)) { return "---"; } return Record.Name;   To populate the record that retired a parcel you can use this expression: var RecordFS = FeatureSetByName($datastore, 'GIS.PF_Lineage_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;   If you are using 3.4 or higher you can make use of the new triggering fields capability: AmirBarMaor_0-1731920231051.png Back capturing I believe there are a few methodologies: Working backward: assuming your current data is great, in theory, you can try to merge historic splits and split historic merges. It will also involve reversing historic parcels into current and vice versa. you are likely to run into issues with boundary lines and points that became historic and should be current. This method is prone to manual errors and I would avoid it. Working forward:  I believe this is the common case. You come across an area that requires good historic data and because it is missing, or because it is questionable, you decide to capture historic records, and work chronologically through the transactions. This is the safer approach. Only care about parcel polygons and lineage: if you only care about the parcel polygons and linage, and most of your transactions are 'splits', you could just use the Create Features to digitize missing historic parcels and then manual populate the CreatedByRecord and RetiredByRecord globalID fields (GUIDS).    Quality Assurance Parcel Lineage depiction: create a link chart to QA that the lineage is correct. Parcel Count: the record feature keeps count of the parcels it created and retired. This field get's updated after operations like Build, Merge, Split, Divide.  Highlight Gaps and Overlaps: make sure you don't end up with overlapping current parcels by increasing the maximal width tolerance and finding overlapping current parcels. AmirBarMaor_1-1731921128721.png   With ArcGIS Pro 3.4 we have improved the link charts visualization. I hope this helps.         ... View more

@Jessica_Watson  I am curious about which organization you belong to because not many organizations manage point lineage. Regardless: Object IDs (or GlobalIDs) are used in relationship classes. So if your points feature class have attachments or any other relationship class, it will use the primary key of the point to establish the relationship. That means that if you choose one point over the other, you effectively choose to maintain its related data as well(if it has a relationship class). In general, we favor keeping the oldest point. Why? The Generate Parcel Fabric Links geoprocessing tool compares the location of the same point in 2 different moments in time. For it to be the same point it needs to be the older point that survives workflows like alignment. The ability to preserve one point and use the attributes from a point that will not be preserved is already supported from version 3.3 and was demonstrated in this meetup. Does this meet your requirements? Did you consider using the geoprocessing tool Import Parcel Fabric Points?       ... View more

@Jared_Baloun  There are a few ways to split a parcel using COGO measurements that are more efficient and maintain parcel lineage (historic parcels) in the parcel fabric. You write " I know this could be done in the parcel fabric but I do not want to utilize the parcel fabric because of the automated shifting that occurs" The parcel fabric does not perform any "automated shifting"  - did you one a case for that? Please describe when and how you see this "automated shifting"?  While it might be possible to manage cartographic representation of parcels outside of the parcel fabric we regard that type of solution as a custom solution.  ... View more

@MarkWasdahl1  The "geometry has null Z values" error message has nothing to do with a missing Z Attribute value. It is hard to speculate and would be best to examine the data, environment, and workflow. Please contact technical support and submit a case.   ... View more

We plan to display the misclose direction in the near term ... View more

Hello @RachelBaca  You will find the command you refer to in the editing toolbar. Those are 'intersection tools' and you can learn more about them in the help documentation. AmirBarMaor_0-1731484534204.png ArcMap and ArcInfo included functionality that was never used and not needed, so we must examine 'why...?' a capability is required before adding it to ArcGIS Pro. That includes understanding the workflows.  What do you do when a recorded document has an error?  Can you reject it and have the surveyor correct and resubmit it?     ... View more

Thanks for the quick feedback @AbigailSmith18  There are a few methods to try and detect blunders in a traverse as described in this slide deck. AmirBarMaor_1-1731400967455.png It is also possible to detect a single-direction blunder in a closed traverse using this method:  AmirBarMaor_0-1731400674459.png   Would improving blunder detection in the traverse pane make more sense than exposing additional information?   ... View more

@MarkWasdahl1  Is this an ArcMap Parcel Fabric you are trying to project? If yes: this is not supported. Please make sure to provide the FEATURE DATASET as input and not the parcel fabric data controller. If this is a feature dataset that contains an ArcGIS Pro parcel fabric it should work. If it doesn't;t work with your data please contact technical support. In this example, I've used ArcGIS Pro 3.3 and accepted the defaults. Make sure to select the  AmirBarMaor_0-1731315654802.png   ... View more

@AbigailSmith18  When examining which misclose information to display we could not find any justification for showing the misclose direction. Could you please explain why you need to see the misclose direction and how you use this information. If it is really important you can still review it by switching to the CLOSURE tab and setting the Closure method to 'Snap last line to close'. The last course shows the misclose direction and distance. AmirBarMaor_0-1731313271446.png You can copy past the misclose information by right-clicking in the traverse misclose area and pressing 'Copy text'. Most organizations do not use this functionality because it is already stored as a parcel attribute that can be used for QA (Quality Assurance). AmirBarMaor_1-1731313371781.png     ... View more

Help documentation: Find Gaps And Overlaps ... View more

To learn more and make an educated decision it is important first to review these resources: Parcel fabric deployment functionality matrix Publish the parcel fabric to ArcGIS Online     ... View more