Latest Contributions by AmirBar-Maor

@mcguerd  Because both COGO schemas use the same field name ('Direction')  but one is a String and one is a Double, it will not be possible to use both ArcMap and ArcGIS Pro against the same feature class as I have wrongly suggested. I would recommend moving to Pro following the steps above. It is still a simple feature class that can be viewed in ArcMap. ... View more

@jcarlson this is very sweet of you. But there are many customers that don't have the knowledge, need, and IT support to set up an enterprise environment. @JasonMcKeefry this is and has always been part of the long-term vision for parcel fabrics. It aligns well with the global trend of moving IT infrastructure to the cloud. There are software engineering challenges to solve - but that is ours to figure out 🙂 When people upvote this idea, please drop a note what is your motivation? simplicity? cost? IT support? small organization?     ... View more

Good catch Josh. We are targetting ArcGIS Pro 3.0 to implement it = replace the standard selection tool with the editing  selection tool that will only select  points ... View more

@THOYSophon  There are so many differences that I'll do my best to keep it high level. We preserved the name 'parcel fabric' and the concepts that work well: - Historic parcels - Points as 'glue' between parcels - Association to the legal record (plan) - Ability to represent the legal and the physical world - Parcel capabilities such as LSA to improve and evaluate spatial accuracy - Tasks to replace parcel workflows   This table shows the differences and some of the confusing and departed concepts: High level advantages of the new Parcel Fabric: - Uses simple feature classes and simple layers - You can use any editing tool - Works using web services and can be maintained from different clients - Parcel lineage (each parcel is associated to the record that created it and retired it) - Improved and configurable information model - Easy to configure quality rules using topology and attribute rules that meet your organization's business requirement - Improved capabilities that will save you time. From LSA, to validating quality through parcle alignment - Automation capabilities exposed in geoprocessing tools, arcpy python methods and arcgis python methods and of course .Net SDK for the 'real developers'.   On top of the list above (from the top of my head), you can leverage all the great functionality that ArcGIS Pro offers: Attribute Rules, Branch Versioning, Tasks, multiple Layouts in a single project, editing capabilities... I am sure different types of customers have different reasons of why they upgrade to ArcGIS Pro Parcel Fabric. Keep in mind that in a few years there will be only one type of parcel fabric... It will be good to get other customers to share the main benefits they see from moving to ArcGIS Pro parcel Fabric.  ... View more

This Story Map is another great resource if you want to learn more about the Mississauga project.  ... View more

@WileyBogren  Great to see you are making good use of the geoprocessing framework. You are free to choose between a geoprocessing model or a geoprocessing script tool to automate and test your migration process. If build is failing please submit a technical support case. Other tips that come to mind: 1. If you have densified curves on your lines and polygons, process them TOGETHER using the Geoprocessing tool Simplify by Straight Line and Circular Arc before you run build. 2. Run Geoprocessing Check Geometry and/or Repair Geometry to make sure the cause for any failure is not a bad geometry. If I had to transfer attributes from one feature to another I would consider using a spatial join. I am not sure you will get a 'one to one' relationship between source and target. As for not duplicating fields when using the transfer attributes if the fields are marked as 'required' - that is a good find and I would log it with technical support.   ... View more

Hello @WileyBogren  If you are migrating your legacy data and have both polygon and lines, simply append them both. Is this is what you are trying to achieve? The steps would be: Create a new parcel fabric in the correct spatial reference Add parcel types, extend schema as needed (fields, domains,...) Use geoprocessing Append to append legacy polygons Use geoprocessing Append to append legacy lines Use geoprocessing Create Parcel Records to create records Build parcel fabric If you know all your legacy COGO dimensions were entered from legal records you can also set the COGOType field on your lines to 1 (entered). Does this accomplish what you are trying to do? All of the above can be run manually or chained in a geoprocessing model or a script tool (if automation is needed). Why are you scripting it? isn't the data migration a 'one-time' event?   A ... View more

@AndrewWallick It is this tool: Merge Parcel Points   ... View more

@PaxtonRountree-jablin I moved this question to the correct location... this is why no one has responded to your question. Did you figure it out or do you still need assistance? ... View more

@Syvertson  Did you submit this with technical support?  Which version of ArcGIS Pro are you using? Please submit any suspected bugs with technical support ... View more

@MARIUSGLOVACI  We improved the performance of the Merge Parcel Points tool in Pro 2.9 ... View more

@RachelFanch  Can you please share the legal document containing the easement? ... View more

@MARIUSGLOVACI  Please submit general ArcGIS Pro questions to the ArcGIS Pro community question or ideas boards. BTW - great idea ... View more

@LeLuong  You can format your labels (color, font, font size...) in ArcGIS Pro. More information in this help topic ... View more