Latest Contributions by AmirBar-Maor

@SarahSibbett  Logging a case with technical support is always recommended. Thank you ... View more

@SarahSibbett  It looks like we have a regression with all of the Editing Modify panes, This includes the Align Parcels pane which is part of the modify tools. Thanks for reporting ... View more

It all depends on your business requirements and how you want your parcel lineage to look like. If you want your data to be defendable in your 'system of record' it should be tied to the source it came from. You can create a Parcel Lineage Link Chart to determine if what you've done makes sense for you or not. ... View more

The first version of the Parcel Fabric, Parcer Fabric version 1, did not have the ParcelCount field on the records, which meant the 'one record' approach would take a very long time to process. Since parcel fabric versions 1, 2, and 3 have all been deprecated, using a single record will not take a longer time to process. If you want to use the Parcel LIneage depiction using link charts, you probably want to use records that make sense (not just create one for each parcel).   ... View more

@MikeZummo might be able to share some of his experience . Before running any adjustment make sure your data: Has good COGO measurements: use the 'Distance Mismatch' layer and the attribute rules to identify and correct any lines that have wrong COGO. Use the parcel fabric layers on the quality tab to detect and fix any small lines - those can cause topological issues. Run the Highlight Gaps and Overlaps tool to detect any topological issues and fix them. if not fixed small gaps and overlaps will become bigger as LSA is applied. Good network connectivity - if you don't have road parcels, consider adding connection lines across roads. Run adjustment in Consistency mode first to detect and fix any outliers. ... View more

@Bud  FWIW I was able to run this expression as an attribute rule calculation to identify features with no vertices (empty geometry) using ArcGIS Pro 3.2.2: if (IsEmpty(Geometry($feature))) return null;   ... View more

@RobertChaney  The purpose of having a record is to know the source of a parcel, and to make the data in the 'system of record' defendable. Using the parcel name to create a record for each parcel, does not make any sense to me. It would be better to create a record called 'unknown' or 'legacy data' or 'Digitized from paper maps 1995'... something that would make sense when you identify a parcel. If you've already migrated the data and already started creating real records, you can still recover: Select all the parcels that were migrated (you can use 'Select by Attributes' and use the editor tracking fields). Use the geoprocessing Create Parcel Records' and use the expression option to enter the name of the record. For example 'Legacy data - source unknown', and run it. Open the attribute table of your records feature layer and make sure all the parcel based records are deleted (you can use the same method above to select them) As for record geometry: Record geometry will only be created or updated when the number of parcels associated with the record is less than 2000. This is done for performance and you can change this setting in the parcel fabric properties. The record geometry is the union of the retired and created parcel geometries, as it is the footprint of the legal transactions and impacts both. For example: we have organizations that create a record to retire a lease - in that case they only retire parcels and do not create any new child parcels. Certain operations like Build, Merge, Clip, Divide, Split ... will update the record geometry when you have an Active Record. Alignment workflows do not do that but you can always use 'Build Extent' to trigger an update.   I hope this helps, and more importantly, makes sense. Amir ... View more

@Bud  If you consider using a task here are a few things to be aware of: A task can select features from different feature layers A task can 'verify' a certain amount of features are selected and prevent the user from proceeding to the next step (making sure there are no features selected, for example) A task can save a selected in one step and restore it in a subsequent step A task can clear the selection and set which layers are selectable. A task can call any command (e.g Select By Rectangle) and any geoprocessing tool. A task get get values from users and later apply them as part of a field calculation. To learn more about tasks: https://pro.arcgis.com/en/pro-app/latest/help/tasks/whatistask.htm   ... View more

Marking this idea as implemented. You can use newer ArcGIS Pro releases against older ArcGIS Enterprise releases.  Since data migration is done in a staging environment using a file geodatabase, the version of ArcGIS Enterprise is not discoverable when running the geoprocessing tool Create Parcel Fabric and you are expected to read the documentation compatibility section referenced below. ... View more

The parcel fabric compatibility is well documented here: From version 10.9.1 we do our best to support older versions of ArcGIS Enterprise. We are conscious that upgrading ArcGIS Enterprise is not as easy as upgrading ArcGIS Pro to the next version and we'll continue this approach going forward. That said: Please be aware that some new capabilities that modify the ArcGIS Server REST API might be disabled in ArcGIS Pro if you happen to use an older Enterprise version (those are usually very minor). Encourage your IT department to upgrade ArcGIS Enterprise just like they would with other server products (DBMS, email server...), or ask to have your own portal and server on a dedicated machine.   ... View more