Latest Contributions by AmirBar-Maor

‎04-20-2023

@SarahSibbett We will look into supporting additional matching options for imported points. You can create as many layers from any table using a definition query. If you have points that you designate as 'control points' you can populate an attribute and apply a definition query. Think of 'control point' as how a point is used. Some organizations might call certain points 'control points' while others organizations would not consider those points as valid control. The point is that a control point is a business decision. In a GNSS era many parcel corner points are more spatially accurate than many 'control points' and the real control is the satellite constellation and its control segment. Please note that if you store points in the wrong location, they will still impact the performance regardless if they are being filtered by the layer (definition query). Once you run LSA any point that has XY coordinates will move to that location, especially if used to constrain the LSA. We do not recommend having points with coordinates that do not match the geometry and having an attribute rule to catch such errors (within tolerance). Either fix the point location or the coordinates. If the coordinates are wrong a simple fix would be to delete them. Sounds like we need to meet in the next UC in San Diego to discuss this 🙂

‎04-18-2023

@JessicaM We are still planning to implement a new geoprocessing tool that would make it easier to create a (name pending) 'Parcel Lineage Map' (AKA 'before/after', 'is/was'...). Could you please share an example of the map you want to produce?

‎04-14-2023

This seems like a common requirement that we can consider shipping an attribute rule with the parcel fabric for it. The increments are done within a 'book' and 'page' or within some other cadastral administrative division. Because of the parcel name prefix components the Arcade NextSequenceVelue method might not work here though. Should we (esri) try to come up with the Arcade expression or does anyone already have it implemented and can share it with the community?

‎04-14-2023

@SeanLyons Thanks for submitting the idea. The import parcel fabric points geoprocessing tool is designed to import thousands of points. If you have any performance issues, please submit a technical support case so we can look into it. If I read between the lines, you are promoting the idea that the points' coordinates (XYZ attributes) do not have to match the points' geometry. Is this true? why would you want that? can they be a cm apart? a meter apart? a km apart? In the past, we had organizations import points that fell outside the spatial reference. This impacts the spatial index and degrades the performance. For that reason we ship the parcel fabric with the rule that the coordinates, if they exist, should match the geometry and that the point should fall within a user-configured bounding box (MBR). In a versioned environment, you can always compare the child version to the default version to identify the changes. Wouldn't this be better than a log?

‎04-14-2023

‎04-13-2023

If you are a .Net developer, you will find this recording useful. Learn how to: Automate the creation of a Parcel Fabric Record and set a version that’s associated with it, edit and add new parcels through code, and reconcile/post the version. Navigate the parcel boundary lines and points to create tools such as for generating custom parcel reports, or for targeted parcel editing workflows unique to your organization. Presenters @TimHodson & @KenGalliher1 Hosted by @DanielStone

‎04-12-2023

@SeanLyons Did you consider using a task for this? A task can: Copy the GlobalID of the active record as a variable Make sure you are selecting the correct lines from the correct layers Set the map as active (this is the second reason why paste special is sometimes greyed out - the map has to be in focus) Paste or append into the correct layer Calculate the 'createdByRecord' field to associate with the active record A task can improve efficiency, promote best practices and prevent mistakes (like selecting features from multiple layers)

‎04-12-2023

@SeanLyons If you want to copy & paste lines into any parcel fabric layer you can simply use the Copy and Paste Special command. This will allow you to preserve the source attributes and will not create seeds. However, since your digital submission users a structured CAD file, in which you know what each CAD layer contains, you can automate the process and append the data to a named version. You can see an example of ingesting a CAD file in this post. We are working on new geoprocessing tools that would make this even easier than it is now. If your lines are not boundary lines, they should be modeled as 'connection lines' You can extend the connection line feature class with a field called 'ConnectionType' (for example) and have different non-boundary types: posting, tie lines, road centerlines... You can display them all in the same layer or separate certain values to different layers using a definition query. Would this work for LTSA?

‎03-30-2023

You can create a Record called "Unknown" or "Unknown - Research Required" and then copy the GlobalID of that record to all the features (polygons and lines) that have the 'CreatedByRecord IS NULL' field. This record will likely be associated with more than 2000 parcels, so it will not have any geometry created for it. For those that migrated from ArcMap, you can also change the record called '<map>' to something more meaningful like 'Unknown'.

‎03-30-2023

The recommended way for this scenario of creating a duplicate (e.g. between different environments of production, staging, dev) is to Copy and paste the feature dataset that contains the parcel fabric.

‎03-23-2023

@RobertChaney You are correct. When the service was initially published this capability was not exposed on the parcel fabric REST API. I am happy this resolved your issue. Amir

‎03-22-2023

The capability to 'reconstruct from seeds' was added to Pro 3.0 and enterprise 11.0. On your server manager, I would make sure the capability is checked on. The screenshot below is from ArcGIS Server 10.9.1 so that's why you don't see it. As suggested, you can also test republishing and see if this solves the issue.

‎03-17-2023

Hello @ChadWoods1 The shift you are seeing cannot be related to the parcel fabric and the workflow is not detailed enough to pinpoint the issue. If I had to guess it probably has to do with different spatial references between the source data (CAD) and the target. Maybe one is using US Feet and the other standard feet. Also make sure that you see the CAD file in the correct location before you "append" it (not sure if you use geoprocessing append or copy the data) My recommendations: Read help resources: https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/buildfromcadworkflow.htm See related videos: https://www.youtube.com/watch?v=ROgplT4S4b4 https://community.esri.com/t5/arcgis-parcel-fabric-videos/how-to-automate-and-process-a-cad-file-to-create/td-p/1223736/jump-to/first-unread-message Contact technical support.

‎03-15-2023

We have missed this question and have answered it here: https://community.esri.com/t5/arcgis-parcel-fabric-questions/optional-fields-for-parcel-fabric-and-best/m-p/1267675#M974 As for performing schema changes with branch versioning: 1. Your published service should allow for schema changes 2. You can perform schema changes while there are child versions that have not be reconciled and posted yet. 3. Any schema changes that impact your layers, like adding /removing a layer, or adding/removing a field will require you to republish with the overwrite option. It will also impact the maps your users are using. 4. To make schema changes you first need to make sure no one is locking your geodatabase. 5. You can stop the map service using ArcGIS Server service manager or stop the ArcGIS Server Service (for all published maps) by going to 'My Computer --> Manage --> Services You are always welcome to contact technical support to get help with your specific configuration. I hope this helps Amir

‎03-15-2023

@AndrewWallick From your question, it looks like you were upgrading an ArcMap parcel fabric. Any field that is required (aka 'system field) is listed in the help documentation and you cannot delete it. However, if you are used to call a field something else, you can always create a field alias on your layer after you publish the data. If there is a field you don't want to see, just turn it's visibility off. You can also highlight and reorder fields. You can learn more about it here. Specifically for the 'Stated area' and the 'stated area unit' fields: when we perform a parcel merge for example, we sum the stated areas of the parent parcels in the child parcel and use the projects default area unit - so if you want this behavior we recommend that we use these fields. The calculated area field will be populated when there is enough COGO information to calculate it. You can then compare the stated area and the calculated area for QA. Another last motivation to use these fields: we ship attribute rules with the software that use these area fields. It will make it easier for you to configure them. As for any old ArcMap fields - we move them over so you can QA them, or calculate over values before you get rid of them. If you can delete them it means they are not needed anymore. If you upgraded from ArcMap and have used the Local Government Information Model, you will find that many parcel types have fields that are irrelevant and should be deleted. I hope this answer helps Amir

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by AmirBar-Maor

Re: Add additional match point methods and optional parameters to the 'Import Parcel Fabric Points

Re: Before/After script for the Parcel Fabric

Re: Parcel code spreadsheet integrated into fabric

Re: Add additional match point methods and optional parameters to the 'Import Parcel Fabric Points - Status changed to: Open

Re: Add additional match point methods and optional parameters to the 'Import Parcel Fabric Points - Status changed to: Needs Clarification

Create custom Parcel Fabric Add-Ins using ArcGIS Pro .Net SDK (Meetup)

Re: ‘Copy Lines To’ for Connection Lines

Re: Choose Whether to Create Seeds from the ‘Copy Lines To’ Tool

Re: Validate creates a huge number of MUST HAVE A RECORD warnings

Re: How to create a duplicate of a Parcel fabric

Re: Reconstruct from seeds tool returns error

Re: Reconstruct from seeds tool returns error

Re: CAD files shift in Parcel Fabric

Re: Best Practices for Parcel Fabric Schema Changes w/Branch Versioning?

Re: Optional fields for parcel fabric, and best practices for schema changes?

Re: ArcGIS Pro Topology Not Working

How to publish a Parcel Fabric from ArcGIS Pro to ...

Editing a Parcel Fabric deployed on ArcGIS Online

Meetup: ArcGIS Parcel Fabric deployed to ArcGIS On...

Re: Find which side of line point falls on

PLSS Editing

Land Administration Domain Model (LADM)