Latest Contributions by AmirBar-Maor

@LukeRipple Can you please confirm: You are using the parcel fabric You can see the feature templates visible in the Create Features pane? ... View more

@HeatherHanson  COGO Reader does support non-tangent curves. But in some states/descriptions are written differently and COGO Reader fails to process them. The best thing you can do is contact technical support and provide a few examples of deeds with non-tangent curves that fail to process. If this occurs a lot, we can consider adding it to one of the 3.5 patches, once fixed.  ... View more

@ClayNorris  I have tested the suggested workflow  - it works. Here is how I did it - does this meet your requirements?   ... View more

@GIS-Chops  In general, we only create parcel tools for tools that are specific to parcels and leverage existing editing tools as much as possible. The editing tools (such as merge, clip, divide, etc.) can exhibit different behavior when parcels are being processed, making it easier for new editors to learn and edit parcels. So would something like this work?         ... View more

@ClayNorris  Changing an attribute does not create a duplicate historic parcel. FWIW - if you are using ArcGIS Enterprise, branch versioning allows you to view historic moments in time. For example: you can have 2 maps side by side, one pointing to the current time and one to an historic moment.   As for your workflow here is a shorter version: 1. Create record. 2. Select parcel. 3. Duplicate parcel 4. "Set Historic" the source parcel If you do a lot of those, you can consider using a task that will automate this process. ... View more

@ClayNorris  The workflow is (if I understand it correctly): Create a new active record for the quit claim Select the parcel or parcels that need to be retired and press the Set Historic button Does this work for you? ... View more

@GordonCourtney  @CFMGIS  COGO Reader is designed for parcels of any kind (lots, subdivisions, tax parcels, ROWs...) that are based on a metes-and-bounds legal description. The parcel fabric controls simple feature classes and has many benefits for cadastre / land records: Every feature is associated to the legal record it came from Historic parent parcels are created when parcels are split / merged Parcel Lineage is maintained and can be depicted to support chain of title research Dedicated tools that save you time Quality capabilities that can be configured to help you evaluate your data + tools that help you fix common issues Easy to migrate and deploy on a file GDB or ArcGIS Enterprise many more... So what keeps your organization from migrating to the parcel fabric? Is it because your organization still uses GIS software as a drafting tool (like CAD)? Or reluctant to adopt a web service-based architecture and improve collaboration between departments and stakeholders?         Given that it takes minutes  ... View more

I have modified your expression Account for the situation in which CreatedByRecord is empty = NULL. For example, if someone forgot to create an active record. Use the IsEmpty method instead of checking for 'null' Only create a FeatureSet if the CreatedByRecord is not empty A bit of cleanup For better performance, you can use the triggering fields to only trigger the rule when the CreatedByRecord field is changed. Let us know if this helps var sourceTable = FeatureSetByName($datastore, "ParcelFabric_Records", ["SubYear"], false) var createdBy = $feature.CreatedByRecord If (!IsEmpty(CreatedBy)){ //if the CreatedByRecord is not empty var fabricRec = First (Filter (sourceTable, "GlobalID=@createdBy")) if (!IsEmpty(fabricRec)){ //If the returned record is not empty = record was found return fabricRec.SubYear } } return "No Sub Year found" ... View more

@HeatherHanson  Shape files do not support true curves so I recreated them as part of the data migration process. A file GDB is a much better format. Here is a glimpse of the migrated data. You can see the true curves in orance (using the 3.5 new Vertices and Nodes toggle):   As you can see, Build did not collapse any curve. If you would like we can setup a meeting to review your migration process and figure it out. To schedule, please DM me. Otherwise technical support is always there to help.       ... View more

@NateArnold  With branch versioning a version can only be edited by one editor. The editor who is the first to start the edit will be able to edit it and anyone else will be locked out. Did you check the locks? Locks are explained in this help topic -administrators can 'purge' the lock (any unsaved edits will be lost) by disconnecting the user. if this is not the issue, and/or if you can reproduce it, please contact technical support ... View more

The reason you would want the administrative parcels in the same parcel fabric is to keep the datasets coincide with each other.  When a point moves, you want it to update all the parcel features it is shared with, which means one group will effectively update parcels of another group. And that is something we want. So how do we prevent people from one group create or update parcels of another group?  The answer depends on the level of trust between the groups. Here are a few solutions to consider based on the trust level: Trustworthy - prevent accidental edits: each group works with a map that does not contain the feature templates of the features that are maintained by the other group. So they cannnot create parcel types they are not supposed to create. Less Trust - you can create groups on your portal and associate users to each group. Arcade allows you to find which group a user belongs to: // find which groups a portal user belongs to. Returns an array. var myPortal = Portal("https://galileo.esri.com/portal/"); var currentUser = getuser(myPortal); return currentUser.groups​   You can use Arcade to create a validation rule that checks if a parcel from a given type was created by a user from the wrong group. This can also be a constraint rule. Make sure to use the triggering fields and allow parcels from the wrong type to have their geometry updated by the other group (e.g. - when a point is moved it should update all parcel types). If you want to get fancy you can also consider user the Arcade method $OriginalFeature to allow geometry updates to pass and prevent attribute updates. 3. No Trust - with this method you can create 2 parcel fabrics, one for each group and use the geoprocessing Import Parcel Fabric Points to TRY and keep them in sync. It will never be perfect, but if you start from the same parcel fabric, then delete the parcel type that is not needed for each group, you should have all the common points between the parcel types.  This approach is likely to be used between 2 organizations that have 2 different networks that cannot be shared. I hope this helps Amir ... View more

@-_Ashley-B-Potter_-  Do you use Attribute Rules that use the SUB_YEAR field? Perhaps they expect a value that does not exist (e.g. 'NULL'). Technical support can also help here.   ... View more

@Jessica_Watson That makes sense. We will look into it ... View more

@MichaelVolz  The parcel fabric controls SIMPLE feature classes. So there is nothing SPECIAL for curves that participate in a parcel fabric. Like any boundary line, you can have another line break the curve into 2 seperate features: Or not:   That is a business decision. For example, you might want to be true to the 'System Of Record' for surveyed lots, but show the Tax Parcels differently in the Tax Map.   ... View more

@MichaelVolz  Yes - From the quality tab you can use the parcel layers to show line or polygon vertices   Densified curves will look like this:   And for those using 3.5 (or higher) you can use the Vertices and Nodes display   That shows 'true curves' and vertices:   You can use the Simplify By Straight Line and Circular Arc geoprocessing tool to process polygons and lines (together) in order to convert them to true curves (within a fitting tolerance) And the result for that example:         ... View more