Latest Contributions by AmirBar-Maor

@BillFox thanks for reporting. Sometimes it takes a while for the video file to get processed... could you please try again? ... View more

@DeanAnderson2  If your task does control any layers, meaning it does not change any contents settings and has no action associated with any of the layers, than you should be able to "fool" it by changing the map name as @JasonCamerano  suggests. However, if you do control\use a layer, then it would fail. That is because you might have 2 or more layers with the same name in a map, and we use the layers unique identifier (CIMPath). Maybe what you are looking for is a new capability to use Python to set configure/map the task items' resources?!   While you might be able to "fool" tasks to use a s ... View more

@WalidAlmasri1  If you moved to the parcel fabric 6 years ago you must be  referring to the ArcMap Parcel fabric. We made migrating to the new parcel fabric (released with ArcGIS Pro 2.4 in 2019) much easier. We also made it easier to adopt: With the new parcel fabric, you can use any editing tool It comes with better defaults It uses simple feature classes It comes with Tasks that can provide 'step by step' instructions Not many have the resources (time & money)  to COGO all their legal documents from scratch. That is a lot of work and most organizations cannot afford it. If your organization can afford it you should consider yourself lucky. If your organization migrated from lines that came from CAD drawings I am sure you might have encountered many topological and edge match issues. Maybe they were not even georeferenced. In that case the I would not consider the effort to create a seamless and topologically correct network of parcel part of a 'parcel fabric migration' effort. That effort would still exist regardless if you migrated to ArcInfo, SHP files or any other technology. For the reasons above most organizations can only afford a 'day forward' approach, which means they move their data in their current state and start to accumulate historic parcels and create parcel lineage going forward. Some organizations take it a step further and enter historic records when working on a new transaction.   I wish you success in your new position.  ... View more

@Anonymous User  The new parcel fabric is a 'data controller' which controls SIMPLE FEATURE CLASSES. The controlled feature classes are not different from any other 'normal' feature classes. The Parcel Fabric REST API can only be used against a parcel fabric. These tools are specifically made for parcels. If you take 'merge' for example, we know that you are not merging 2 polygons but 2 parcels, which will: Mark the parent parcels as historic Mark the shared boundaries as historic Combine the legal areas with a new legal area (sum) Update the record for the merge transaction with the number of child and parent parcels + update its geometry. Maintain parcel lineage between parent and child parcel Migrating to the new parcel fabric is easy. So can you please explain why you are trying to avoid leveraging those capabilities? ... View more

@jcarlson well earned and well deserved! This slide shows your contributions are not limited to helping other community members but helping shape the product. A big thank you from the parcel fabric development team!   ... View more

@m3 The intent was not to confuse you but to: Identify business requirements (storage, format) Show that while the problem sounds simple its implementation is not. Thanks for your comments - they are valuable to us. Amir ... View more

@DeanAnderson2  You have plenty of great ideas. It would be great if you can enter them: one idea in the parcel fabric community for setting the Active Record using python for a given map. Another idea in ArcGIS Pro Geodatabase for being able to change the version of a map. ... View more