Latest Contributions by AmirBar-Maor

Thanks for submitting Mike, Could you please describe what type of COGO update you want? If this is an update of a single COGO value on a line you can use an update cursor. Or do you want to load lines as a traverse and distribute misclose? in that case wouldn't it be better to use the Least Squares Adjustment (available In ArcGIS Pro 2.6 and above)? ... View more

Thanks for submitting your idea Matt. Sharing with Amy Andis‌ and Phil Sanchez‌. The traverse tool assumes you use the '10 key pad' with the 'enter' key to move between values while the editing constraints use the 'tab' key that is not part of the '10 key pad'. A challenge. ... View more

Did you get a chance to see this meetup?  Video Link : 6468  We used an Arcade expression to retrieve the historic parcels in the pop-up. It looks like this: You can create a custom expression in your popup (right-click the parcel layer --> Configure Pop-ups) and paste this: Expression: var RecordID = $feature.CreatedByRecord; var sql = "RetiredByRecord = '" + RecordID + "'"; var fsHisoricParcels = FeatureSetByName($map, 'Historic Tax', ["Name"], false); var fsParentParcels = Filter(fsHisoricParcels, sql); var cnt = Count(fsParentParcels); if (cnt ==0) {return "No Parent Parcels found"} else{ var ParentParcelsNames = cnt + " Parent Parcels = "; for (var HistoricParcel in fsParentParcels){ ParentParcelsNames += (HistoricParcel.Name + "; "); } return ParentParcelsNames; } ... View more

Hi Jamal, I assume you use the editing Divide tool with an active record. If you do it SHOULD create historic parcels and populate the RetiredByRecord with the Global ID of the Active Record. If you are using an old version of ArcGIS Pro (2.4) - you might not get this 'parcel behavior'. Amir ... View more

Adding the ability to create polygons is still in the product plan.  ... View more

Hi John, If you are using the first version of the parcel fabric (version 1 with Pro 2.4 and server 10.7.1) you might have an issue with record features that are associated to too many parcels. To confirm this open the attribute table for the records feature layer and sort them using the Shape_area field. especially if you are coming from ArcMap parcel fabric, you might have a <map> plan that is causing the performance issue. Just delete all records that have a huge geometry, reconcile-post, and recall the spatial index for the records.  If you are seeing general performance issues (drawing, selection etc.) then the problem might be anything from a bad network cable to a bad spatial index. The parcel fabric in Pro uses SIMPLE FEATURE CLASSES - any performance issue is unlikely to be parcel fabric specific. Technical support might also be able to help. Amir ... View more

Hi Mattew, Every use-case is valid, even if you don't; think it is "typical".  For people coming from ArcMap it will take a while to get thinking "simple" - in this case selecting the points you want to delete and press the delete key, then save edits. ... View more

Yes - this is by design. With all geoprocessing tools, you can hover over the 'i' icon to get an explanation or on the help icon This optional parameter can be used to automate a workflow where you only want to build a specific record  - for example - only the lines that were copied from a DWG file. Build Parcel Fabric—Help | Documentation  Looping Christine Leslie‌ ... View more

You might want to follow these steps: Enter a traverse—ArcGIS Pro | Documentation  Amir ... View more