Latest Contributions by AmirBar-Maor

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

Implemented with ArcGIS Enterprise 12.0. This capability is now exposed as a REST API and runs on the server. ... View more

Implemented with ArcGIS Pro 3.6 ... View more

Implemented with ArcGIS Pro 3.6, but will be provided to selected customers. ... View more

@MizukiKayano2  The Calculated Area field is designed to calculate the area from the COGO measurements, if they all exist. The COGO measurements are usually in 'ground' units and reflect the real ground area. For quality assurance purposes, this area  can be compared with: Shape Area - which is calculated from the feature geometry in the spatial reference (grid) using the spatial reference units.  Stated Area - which is the legal area of the parcel, as stated on the legal document, and using the legal area units.   Questions: How would the system identify a 'natural boundary'  from a line that was cracked and has additional vertices? When calculating an area for a natural boundary, should we internally inverse the COGO values for each small line segment? Wouldn't that mix valid 'ground' COGO with an invalid 'grid' COGO? Why is this needed? Do the legal documents not contain the legal area that should be populated in the 'Stated Area' field? Should we consider extending the schema to classify lines as 'natural boundaries', 'Road Frontage', ...?     ... View more