Latest Contributions by AmirBar-Maor

Hi Tom, Creating records for all your historic parcels should be easy if they can have a field (or combination of fields) that has the name of the legal record. This is done using the geoprocessing tool Create Parcel Records. It is harder to backfill and associate the RetiredByRecord field, but potentially can e deduced using temporal information. If you would like to share a sample data with us we can look into it. Parcel lineage is going to get even better. Amir ... View more

Hi Pascal, the concept of "open parcel" and "Close parcel" is confusing and has been deprecated with the new parcel fabric. You can add boundary lines as well as connection lines as you see fit for your business requirements. You can model road centerlines and any survey measurements (tie lines) that do not create a parcel boundary as a type of 'connection line' = they contribute to the network connectivity but do not form parcels. You can also add boundary lines without creating a parcel polygon. Those lines will appear as topology errors and again you have a choice: either mark those as exceptions or modify your topology rules to meet your business requirements. You can also contact your savvy distributor @Anonymous User @DaveHorwood  Amir     ... View more

Hi Pascal, The Cadastral XML format is no longer supported and failed to get widely adopted. Instead, we are using the superior format of a file geodatabase to exchange data as well as all of the other supported formats in ArcGIS Pro (dwg, dgn, kml...) and ArcGIS Enterprise (WFS, JSON...). You can create features using python, js or .Net depending on the preferred workflow and skills. Attribute Assistant is replaced by Attribute Rules that work on all ArcGIS clients and have many other advantages. There are many advantages to the new parcel fabric information model and you extend the schema of each parcel type as you need to based on your needs with greater ease.  Converting CAD to simple features is also easier and there is no need to first convert to cadastral XML. Why we got rid of Cadastral XML (A few reasons): Low adoption rates in the industry Cannot scale to support large amount of data or parcels with huge geometries Does not preserve geodatabase relationships, topology rules, attribute rules etc. Hard to view in its native format Waste of resources to maintain Only works on the desktop client XML is not very efficient to use over web services Who needs files when you can access the real data using web services in real-time?! ...   Why is a File Geodatabase or a Mobile Geodatabase a better format to exchange data? Support relationships Support domains Support attribute rules Uses the exact same schema - nothing is lost Can use any tool, SDK, Python, API to write to this common format Continues to evolve over time Scalable - can store millions of parcels Content is viewable instantly without any ETL Support spatial references Supports true curves, spirals, natural boundaries,... Can be compressed Has a spatial index Support topology ...       ... View more

@MehdiPira1  Your suggestion would work if the direction is derived from the geoemtry. I believe @IreneHwang  is using an attribute that originates from a legal document and is not guaranteed to match the feature geometry. Common reasons for the mismatch are parcel misclose adjustment, least-square adjustment and ground to grid correction. ... View more

I would start with the User Conference technical session: Parcel Fabric: Migrating and administrating parcels with ArcGIS Pro ... View more

There are tools in the  'Conflation toolset' that generate links based on the geometry of the source and the target datasets like the Generate Rubbersheet Links tool. Branch versioning has temporal capabilities: you can specify any moment in time and view the data in that specific moment (geometry and attributes). Every feature is uniquely identified by a GlobalID. So the "secret sauce" of the tool is basically comparing the point location in 2 moments in time. In the new parcel fabric we do not have any hidden tables and no hidden relationship classes. Links are not created between vertices, only between points. If you have related data it would not be a bad idea to introduce vertices based on the location of parcel points using the geoprocessing tool like Integrate or using geodatabase topology (cracking). This would improve the results of spatial adjustment. ... View more

Thanks for the idea, Frank. In ArcMap, we stored a vector for each time a point moved. The downside was that the vector table gets bloated very quickly. In the new Parcel Fabric, we leverage the temporal nature of Branch Versioning. By comparing the location of each point in 2 different moments in time we are able to generate a 'link' or an 'anchor point' without having to store vectors. File geodatabase does not have any archiving/temporal capabilities. With Attribute Rules you can create a rule on the points feature that will write to your vector table every time a point moves. Or submit another idea to enable temporal capabilities and 'moments' on File Geodatabases.      ... View more

Thanks Sean. This is now in the product plan. We might get in touch for additional clarifications if needed. ... View more

Thanks Sean. I've added it to our product plan. Any idea/preference on which key on the number keypad to use to flip a direction? And yes - there should be also an explicit contextual menu using the mouse. ... View more

Implemented in ArcGIS Pro ... View more

In ArcGIS Pro you can run a geoprocessing tool to validate (check) your parcel fabric. Beyond the rules you can configure to meet your business needs the result are error features that can be inspected visually on the map as well as in the Error Inspector:   ... View more