Latest Contributions by AmirBar-Maor

@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

@anna_garrett  We understand your frustration about having to redo your edits. The best thing is to create a technical support case. Are you using ArcGIS Enterprise? If yes - older versions like 10.9.1 are no longer supported - see help documentation for further details.   ... View more

@FrankConkling  - inspired by you! ... View more

@MizukiKayano2  Guessing natural boundaries can be problematic for many customers who have data quality issues: polylines that have many vertices. For example, curves that got rubbersheeted over the years, or cadastral agencies that use polylines instead of 2 point lines.   'Original Area' LSA strectches the natural boundaries to the new point location as you can see here. Before:    After applying LSA (red is the original location): That means that if you run LSA and then use Build Extent, the calculated area will change from the "original" area.     ... View more

@MarkWasdahl1  In that case you can lower that number: In the Catalog pane, right-click on the parcel fabric Open Properties  In the General tab, expand 'Parcel Fabric' and type the new value. A 100 parcels that are very large, along a natural boundary, can also take their toll. Why do we have a geometry for the record?  It is designed to be the 'footprint' of the record, allowing users to easily understand which legal transaction took place in a given location. It is also used to navigate to the work area. Do you have other use cases for the use of the record's geometry? ... View more

@MarkWasdahl1  Generating the record geometry can be expensive in terms of performance. Imagine there are 1999 parcels associated with the record, and you only moved one parcel. So not all operations will trigger a record geometry update (Move, Align Parcels, ...) - in those cases @pt_instructor  is correct, simply use Build Active or Build Extent. For performance optimization, you can also consider reducing the maximum number of parcels from 2000 to a lower value.   ... View more

@MizukiKayano2  What is a 'Natural Boundary? Since the 'CPDM_LineType' is specific to your information model, we could: Try to guess which lines are a natural boundary: every line that has COGO value and a 'bend'. Would this work for LTSA? Another option is to add a field: for example, 'IsNaturalBoundary' or 'BoundaryType' that could be set by every organization. That way we can apply the special logic only to 'natural boundaries.   Area Calculation Since COGO values are assumed in 'Ground', and inversing the natural boundaries will be in 'Grid', we could rely on the 'Scale' field to reduce the dimensions to theoretical 'ground'. Would this work?   'Original Area' concern What would prevent the area from being calculated again, after you run LSA, if you were to fix a data issue and build that extent again?  ... View more

@ThomasHoman  After consulting with the experts: The best approach for identifying performance problems is to first identify where the time is “going” (and capturing this information before adding more cores). You can start by capturing a SQL Server profile while the user performs the slow operation. If you don’t have the ability to capture, the second option would be using Pro’s ArcGIS Monitor and the log to see which call is consuming the time… this is a little more advanced. You can always contact technical support and open an incident reporting command or workflow xyz is extremely slow and they should be able to provide guidance on how to identify the root cause. ... View more