Latest Contributions by AmirBar-Maor

@MDB_GIS  This feature still exists for ArcGIS Pro 3.6. You will see the popup message when you create a new record with a name that already exists. It looks like you are looking for a similar UX when you try to change an existing record name to a record name that already exists. Maybe this capability, to merge records together should be exposed on the Manage Records pane?   ... View more

Working with @DaveHorwood to use direction constraints during the LSA to achieve the desired result ... View more

@BaileyGlassford1  FWIW - to view which lines are associated to the record you can use one of these methods: 1. Press the Show only Active 2. From the active record HUD press Select Features in Active Record and choose lines         ... View more

@MattMattWard  The record geometry can be easily updated by using running Build Extent once you have updated the parcel geometry, which is the real issue. How to update the Parcel geometry? It looks like once you have move the parcel to the correct location it leaves a hole behind. You can easily fix that by shrinking that parcel to a seed and then run reconstruct from seed. That will fill the hole. Does this work for your use case? ... View more

@BaileyGlassford1  Make sure you are using a compatible client and have the appropiate licensing (Advanced user type extension - included in 'Professional' and 'Professional Plus'). For more information see help documentation: https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/deploylicenseparcelfabric.htm        ... View more

Hello @JamalNUMAN  The parcel lineage shows the issue. You use record '17' and split the historic parcel twice using the split tool. The issue is with the worklow. I belive this is the result you want to get:   Prep: you should use Build Extent on your data - this will create missing parcel lines and is part of the data migration process. Then follow these steps: Create or activate record '17' Select parcel 17  Press Copy Lines to Active Record.  Use the Create Features pane to create the splitting lines Create Parcel Seeds and make sure every loop has 1 parcel seed Build Active Observation: it looks like parcel 17 was created and retired by record 17. In real life this does not usually happen. Parcel 17 has likely been created by another record (e.g. "digitized 2005' or 'DWG file ....') and then split by a new record. ... View more

@BaileyGlassford1  Does this happen everywhere in your data or only on those specific parcels? Does the parcel Shrink to Seed if you select it and use Shrink to seed? Do you use the default symbology?   There are many things to examine, the best would be to submit a case with technical support and provide them a sample data to reproduce the issue. You can use the geoprocessing tool 'Copy Parcels' to extract a portion of selected parcel to a file geoedatabase. You are welcome to send me the case number so I can have a closer look. Copy Lines To Active Record should work and is a very valuable tool for many different workflows.   ... View more

@SeanLyons  Did you try selecting all the lines with high accuracy (posting plan) as input for LSA? ... View more

@SarahSibbett  While reading your reply I was thinking to myself: "Sarah really gets LSA. She must have taken some classes or she is spending too much time with Dave 😉 "... until I saw the last comment. There could be multiple approaches: Introduce constraints within LSA. Providing different weights as proposed. At some point, if the distances do not fit, line will start bulging. We can also identify lines that have the same bearing before LSA and 'merge' them into a single line prior that will be used as input for the LSA , then decompose the on the way out. You can think of it as LSA filtering to  skelaton network. After LSA we can move the points using the parcel move point 'stretch' behavior. Post Processing - such a method could be applied to any data regardless of what caused the line to become wiggly (LSA, transformation (rubbersheeting), alignment, ...). Such a method could use the COGO direction to determine tangency or an offset tolerance. I wonder what other customers like BLM need. @MikeZummo ... View more

Hi @SeanLyons  I am going to ask some annoying questions in order to understand the business justification: If LSA moved data by up to 10 cm you would not notice it on the map - right? How much did the data move in the image you shared? Could it indicate that the data is of poor quality and should have never been adjusted to start with? Let's say you ran LSA and the maximal shift was 10 cm - what tolerance would you use to straighten up the lines?   We are dealing with 2 conflicting requirements: Improve spatial accuracy - move the data to the most probable location. Improve cartographic representation - the eye is sensitive to wiggly lines. Make it look better. One has the potential of cancelling the other. And if you run around a block of parcels, making parcel road frontage straight, you will accumulate an error that is similar to traverse misclose. How should that misclose be distributed?    ... View more

@MizukiKayano2  What is the expected behavior for points? Should it use the same logic? = Select the historic points first and then 'supplement' with current points? If we had a tool that filters and only shows historic features, would you expect current parcels to be selected as well? Can you explain why / when you would use the tool to select historic features?   ... View more

Thanks for the clarification @MizukiKayano2  @SarahSibbett    The only sticky point is how to identify a 'Natural Boundary'. While guessing it on your data might work, it might fail for other datasets and create many false positives.   We might need to add an optional field to account for boundary type. Such a field can be used for other use cases: symbology, labeling, zoning and planning, dedicated tools to update natural boundaries, special behavior (for example - after LSA), ... The new Traverse SDK (3.7) might be useful for the short term ... View more