Latest Contributions by AmirBar-Maor

@jcarlson  Thanks for sharing. I think we can improve build to search for any points that are only connected to retired lines and make them historic. So maybe a better title for this idea should be "Build should mark points that are (only) connected to historic lines as historic"? ... View more

@AlanStearns1  You could create an attribute rule that deletes a parcel as soon as it becomes historic. You could also create an attribute rule that copies it out of the parcel fabric and deletes it. But you do lose the parcel lineage...   What kind of topology rules are you currently using that make historic parcels an issue? If you are using MUST NOT OVERLAP and/or MUST NOT HAVE GAPS I recommend you take a look at the Highlight Overlaps and Gaps tool. It highlights overlaps and gaps WITHIN TOLERANCE - which means you can define the width of a valid gap (like roads) or overlap (like condo units). ... View more

@jcarlson  Can you please describe when and why you set a point as historic? I ask because when you set a parcel as historic, any point around it that is not shared with a current parcel will be marked as historic. Thanks. ... View more

@PascalVezina  It's great to see you make strides in Arcade and thank you @DrewDowling for sharing the link to Husseins' blog.  Here is an example of updating a line geometry based on a point location: https://community.esri.com/t5/arcgis-parcel-fabric-blog/using-attribute-rules-to-update-the-line-geometry/ba-p/1103947   Another example (that had a scalability issue) is where an update to a smaller US PLSS 'intersected' polygon updates a section by selecting and dissolving all other 'intersected building blocks'.   This is the expression used var twpNo = $feature.TWNSHPNO var twpDir = $feature.TWNSHPDIR var rangeNo = $feature.RANGENO var rangeDir = $feature.RANGEDIR var sectionNo =$feature.FRSTDIVNO //The attribute rule is added to the Intersected polygon class on the FRSTDIVNO field on update //select all other intersected polygons that belong to the same section //construct a sql query for intersected and sections var sql = "TWNSHPNO = '" + twpNo + "' And TWNSHPDIR = '" + twpDir + "' And RANGENO = '" + rangeNo + "' And RANGEDIR = '" + rangeDir + "' And FRSTDIVNO = '" + sectionNo + "'"; //dissolve all intersected polygons in the section to get a polygon geometry var fields = ['TWNSHPNO','TWNSHPDIR','RANGENO','RANGEDIR','FRSTDIVNO', 'GlobalID']; var intersected = FeatureSetbyName($datastore, "Intersected",fields, true); var fsIntersected = Filter(intersected,sql); var SectionGeometry = Geometry($feature); for (var interPoly in fsIntersected){ SectionGeometry = Union(SectionGeometry, Geometry(interPoly)); } //find the corresponding section geometry feature var sections = FeatureSetbyName($datastore, "Sections",fields, true); var fsSections = Filter(sections,sql); //get the section row (we should only have one ) var sectionToUpdate = first(fsSections); var sectionGlobalID = sectionToUpdate.GlobalID; return { //we want to just return the value of field `FRSTDIVNO` no change require "result": $feature.Field, //this keyword indicates an edit that need to happen, its an array since we can make many edits "edit": [ { //the other class we want to edit "className" : "Sections", //the type of edit, in this case we want to update so we say `updates`, its an array since we can make many updates "updates" : [ { //what feature we need to update? we can either find it by the globalid or the objectId "globalID" : sectionToUpdate.GlobalID, //what do we want to update (we can optionally add attributes property and update properties there) "geometry": sectionGeometry } ] } ] }   Once you have a your expression working, please share. ... View more

Hello Valerie, The parcel fabric can be deployed for a single user using a file or mobile geodatabase or as enterprise deployment to support multiuser editing. If you want to use ArcGIS Pro 2.9, you will need ArcGIS Enterprise 10.9.1 as this table shows: You can find more about it in this help link. As for your DBMS compatibility - see this table. Can an ArcMap client access Pro parcel fabric the data in SDE using direct connect? No. Can an ArcMap client access the Pro parcel fabric feature services (view only)? Yes. Amir           ... View more

Really old stuff. Some might say nostalgia, some ... ... View more

@PeterSchoenfield  To your second question, there are many information models used against the parcel fabric, beyond the Local Government Information Model (LGIM) used in ArcMap. If we implemented auto-assignment for the  LGIM it will require us to map which fields belong to which parcel type. But... we could never know how to associate your extended fields. So it is easier and safer to delete them after reviewing the results. I wonder how many customers find it challenging to delete those fields? ... View more

@PeterSchoenfield  @TedCronin  Since we cannot tell which fields were used by different customers, for the most part, we treat the old ArcMap fields the same as we treat fields that were extended by the customer and/or added as part of the Local Government Information model, which is: we bring them over. No brainer - if you have fields in the ArcMap parcel fabric that you have never populated, I would start with deleting those.   Parcels These are the new system fields in Pro. They always appear on the top and you cannot delete them: Carried over fields:     Parcel Lines (and connection lines) New system fields:   Carried over fields:       Points New system fields   Old ArcMap Fields - consider deleting the fields that were never used. Some fields such as Category, CenterPoints should be deleted. If you ever maintained the point accuracy using the MaxDN and MaxDE fields you can move translate these to the XYAccuracy new field.     Records ArcMap 'Plan' fields These are the old ArcMap 'Plan' fields, most customers never maintained the surveyor name, company and SurveyDate. If you did you can keep them and continue to do so. COGO accuracy is now maintained on the lines and points that are created by the record (plan). TruMidBrg (True Mid Bearing) can be deleted and/or moved first to the new 'direction type' field. This is only used by federal agencies that maintain old PLSS or fake modern GNSS measurements to look like old theodolite observations.           ... View more

When a task step opens a view from a closed or minimized state it will return that pane to the original state when it moves to the next step. Views (e.g. map view, layout view, catalog view,  attribute table view...), as well as other controls, are not included. If you see a different behavior with panes please report a bug. Many panes can be embedded in the task itself which reduces the "pane clutter". ... View more

If very small lines are the culprit, we introduced the ability to detect very small lines using a layer in ArcGIS Pro 2.9. From the quality tab you can add the 'Too Short' layer and view any small lines that should be eliminated. The Merge Parcel Points tool is a useful tool to use for that process (just make sure to check the option to remove lines in the bottom of the tool)   And as always, the development team can only hypothesize - if you think you encounter a bug it would be best to content technical support and provide them a sample data.   ... View more

The only cases I can think of where features would appear in the attribute table but not in the map are: 1. A display filter is applied - but this should not occur if you added a parcel fabric to a new map 2. The record features have no geometry - you can select a row in the attribute table, right click and zoom to it. If you cannot zoom to it and if it has no shape area it means it has no geometry. 3. A bug - contact technical support You can also try to add the feature service of the record feature layer. You can do it through the Add Data and add the URL - it usually ends with '/0' ... View more

@Lebowski  You cannot change the parcel type from Administrative to regular parcel type. If you wanted to change them you can create a new parcel type, copy over the schema, append the data and make sure all association to record has been maintained. TEST!. then remove the old parcel type and delete the feature classes that were associated to that parcel type. Can you add topology rule to the parcel fabric topology - YES you can. You bring a great use case to extend it. Once you solve the misalignment issue you can consider removing the topology rule. There could be some creative ways to use geoprocessing tools to automate fixing the misalignment between your administrative parcels and the non-administrative parcel data. We can set up a meeting if you want us to have a look  ... View more

@Lebowski  If this is a 'Split from Parent' workflow the steps will look like: Create a new record Select parent parcel Copy line to the active record Split the 500' line as needed and add new lines Create parcel seeds Build Active record Attribute new child parcels Where did the 500' line go?  It became historic along with the parent parcel. And if you look closely at the new split lines you have created you will notice that the ParentLineID field is populated with the ID of the parent line.   To your question, if one feature can hold 2 sets of COGO attributes the answer in 'No' . That is true for every feature and even if you duplicate the COGO fields it would be very hard to label them in the correct location. ... View more