Latest Contributions by TimHodson

‎10-17-2023

Mark, I see messages similar to this when trying to delete a feature class if I have forgotten to first remove the parcel type from the fabric. You should be able to delete those feature classes. To remove the parcel type, right click on the fabric in the Catalog pane, and click Manage->Remove Parcel type, then in the GP tool that's presented, enter the name of the parcel type to be removed. You'd repeat this for each parcel type. After removing the parcel type, the feature classes should be "released" from their controller, and you can try the delete again.

‎10-09-2023

Hi @ElisseDeleissegues1 , To your question and reference to use of the NGS point. I know you are asking for other methods, but I'm curious about how you are currently using the NGS point reference, if at all? The reason I ask is that last year and earlier this year a few of us on the parcel development team had the opportunity to review a large number of land records documents from in and around Honolulu. We noticed that the NGS point reference used for the point of beginning appears on most (pretty much all?) of the documents. I see this same NGS-reference pattern on the document you've shared. Based on our research we found that NGS references are valuable for geolocating parcels with better than expected positional accuracy. It requires the use of feature templates that use geodetic azimuths, as described here: https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/use-geodetic-directions.htm I will follow up with additional information on this method. Regarding the painted locations for the centers of cul-de-sacs. The painted /surveyed locations used for the photo-control could serve double-duty as a tie-in to the parcel boundaries if there is a physical marker in the asphalt (iron pipe or similar) that can be positively identified as the "true" (in parcel boundary sense) center of the cul-de-sac, and that is what gets painted/surveyed. -Tim

‎08-28-2023

Hi Nick, yes you have answered your own questions correctly. @NickN wrote: My understanding is that the adjustment uses COGO to calculate adjustment vectors of the fabric points. In the case of a tax parcel and lot parcel being identical, the fabric points will be shared between the two sets of lines, correct? Yes. This would be what we'd expect to see. Sometimes you need to use the merge points tool when there happen to be exactly overlapping stacked points, or very close points that really should be a single point to represent a single shared corner. @NickN wrote: Are lines without COGO ignored in the adjustment calculations, but still affected by the adjustment when applied? Yes. @NickN wrote: ...we should be able to only backfill COGO on the Lot lines correct? When an adjustment is run and points moved, since the points are shared all lines shared between points are adjusted, even the ones without COGO. Yes. A general tip on running the least squares; note that you can also select the lines that you want to process in the least squares. Selecting the parcel polygons does work to include the boundary lines for the parcel, but it will not include any connection lines that are attached to the parcel. You need to select those connection lines as well. For this reason I personally like to simply work with the lines (parcel lines and connection lines), and directly select those lines to be processed. It's a bit less ambiguous about what lines are going to be used. As you note, if the line has no COGO, then even if it's selected it will not be "seen" by the adjustment. -Tim

‎08-24-2023

This is fixed in the latest patch 3.1.3 that was released today. ArcGIS Pro 3.1 patch 3 (3.1.3) is now available to download from My Esri. https://support.esri.com/en-us/bug/the-merge-parcel-points-tool-returns-topology-errors-bug-000159260 Thank you again for reporting it.

‎08-24-2023

Links shared in the chat during the session. Latest software Patches: https://support.esri.com/en-us/patches-updates/2023/arcgis-web-adaptor-iis-11-1-reliability-update-2-patch https://support.esri.com/en-us/patches-updates/2023/arcgis-server-11-1-utility-network-and-data-management-patch-1 https://www.esri.com/content/dam/esrisites/en-us/media/products/arcgis-pro-issues-addressed/arcgis-pro-3-1-issues-addressed.pdf Starting point for help doc on parcel fabric: https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/whatisparcelfabric.htm Add-in for transforming CAD: https://arcg.is/1bb9Lq Idea on storing ground to grid with the record: https://community.esri.com/t5/arcgis-parcel-fabric-ideas/combination-scale-factor/idi-p/1057561/jump-to/first-unread-message Video demo: How to migrate data to the parcel fabric: https://community.esri.com/t5/arcgis-parcel-fabric-videos/how-to-migrate-to-the-parcel-fabric/m-p/976836#M10 The sequential numbering tool: https://pro.arcgis.com/en/pro-app/latest/help/editing/assign-sequential-attributes-by-drawing-a-line.htm

‎08-24-2023

hi Dean, The effect you were seeing where circular arcs fall outside the tolerance can be solved in two different ways, as specified by the bullet points. It’s either/or, not both. Sorry it was not very clear in the original post, I've edited the post to clarify. -Tim

‎08-04-2023

@DeanAnderson2 I can give possible reasons for two of the items you mention, the one about circular arcs getting created when you don't what them to be, and the other about resulting feature geometry being outside the specified offset. Without seeing examples it's hard to know if these make sense for your cases. It is possible that the Simplify By Straight Lines and Circular Arcs GP tool can result in a circular arc that bows out beyond the Maximum Allowable offset from the initial feature’s geometry. This may occur if you chose the Fit to Vertices option, and it is also more likely to occur with a larger value for the Arc Angle Step. The algorithm works by taking the positions of the vertices and trying to fit straight lines and circular arcs and by allowing the positions of any of the original feature vertices (except the first and last vertex of the feature) to be iteratively varied within the Maximum Allowable offset until a best-fit circular arc and/or straight line can be found. This can result in a new circular arc that bows outside of the offset distance while not breaking the conditions of the algorithm because the original vertices that are used to define the circular arc are still within the allowable offset. Here's a graphic showing this: To avoid the likelihood of this happening, you can either: Use the Fit to segments option instead, because this option uses the segment geometry, OR Reduce the value for the Arc Angle Step if you are using the Fit to vertices option.

‎07-28-2023

Hello Diego, I suspect that you have geometries that are bezier curves. With ArcGIS Pro 3.1 we fixed a performance problem and a geometry problem like the one you show in your third image above. If you are not able to upgrade to ArcGIS Pro 3.1, you could consider converting your bezier curves to circular arcs or to polylines with straight line segments. For your reference: BUG-000155164 See also related post here: https://community.esri.com/t5/arcgis-parcel-fabric-questions/is-there-an-easy-way-to-track-down-features-that/m-p/1236543#M898 -Tim

‎07-28-2023

For the ArcGIS Pro 2.6 release we fixed an issue on the parcel fabric line layers that addressed this problem. However, for standalone COGO layers there is a separate but similar issue where the unit is "hard-coded". This will be fixed in the 3.2 release. If you are seeing this problem in parcel fabric line layers and in a release that is later than 2.6 then please contact tech support. If /when you contact tech support please reference the following number; its for the bug mentioned above that will be fixed in ArcGIS Pro 3.2: BUG-000158885.

‎07-26-2023

The ground to grid correction is applied when the data is entered. If you need to rotate and scale the features after they've already been created then a different approach will be needed to do that. There are a couple of options, you can set the ground to grid as before and then use the Trace lines button in the traverse tool, as explained in the above referenced video, around 31m29s. This should apply the ground to grid to the lines you trace. You could also use the rotate and scale tools on the selected line features (and polygons if needed.) Turn off the map or gdb topology (optional but depends on the situation) and then select the features you want to rotate and scale. Since you know the scale and rotation from the computed ground to grid, you can set the anchor at the commencement point location and then use the ‘A’ and ‘F’ shortcut keys to get the dialogs to type in the rotation [A]ngle and scale [F]actor as follows:

‎07-26-2023

Yes, the best practice would be to set the ground to grid correction first, and then use the COGO entry tools such as traverse, direction/distance, and so on, while using COGO-enabled lines. All the lines in the fabric are COGO enabled, and so there is no difference when using connection lines. The general workflow in the fabric, would be to use the connection lines to start at the commencement point, and then COGO to the point of beginning, then switch to the lines for the parcel type you are using, and enter the COGO for the parcel's lines. Here's another video recording from our meetup on the topic of COGO: https://community.esri.com/t5/arcgis-parcel-fabric-videos/meetup-entering-cogo-measurements-in-arcgis-pro/m-p/1115965#M66 -Tim

‎07-25-2023

Hi @SenecaFrancis , using your example COGO line, I made a video showing how to set the ground to grid correction using the Interactive tool, and then using the Direction Distance tool after the correction has been set to create the line geometry between the two points. Since the correction is turned on, the end point of the line now matches the position of the "to" point.

‎06-12-2023

Thanks @jcarlson @KarinPierce @anna_garrett for reporting this problem. I've reproduced the issue on 3.1.x. It is not reproducible in 3.0.x. We will work to find the cause, identify a solution, and get a fix into the next available patch.

‎05-16-2023

Please note this similar idea; you may want to up-vote it as well: https://community.esri.com/t5/arcgis-pro-ideas/live-total-length-measurement-of-polyline-when/idi-p/1018975

‎04-13-2023

Here are the links to the resources from the chat and slides: Pro Concepts page Parcel API Pro Concepts page COGO Developer Summit 2023 Slides and sample code on Github. Parcel Utilities add-in: Item on ArcGIS Online Code COGO Line Features add-in: Item on ArcGIS Online Code Transform CAD 3.x add-in: Item on ArcGIS Online Code Full list of ArcGIS Online add-ins from Esri parcel team Additional recording of technical session from 2021 Esri Developer Summit: ArcGIS Pro SDK .Net Introduction to the Parcel Fabric API

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by TimHodson

Re: Parcel Fabric Local Government Model GBD Feature Class Deletes

Re: Fixed Points from Survey

Re: Fabric COGO and Adjustments

Re: Merge Points: Inconsistent Behavior?

Re: MeetUp: Introduction to Record Driven Workflows

Re: Using SimplifyByStraightLinesAndCircularArcs to help convert taxlot polygons from ArcMap to Fabric (ArcPro Fabric 3.1x)

Re: Using SimplifyByStraightLinesAndCircularArcs to help convert taxlot polygons from ArcMap to Fabric (ArcPro Fabric 3.1x)

Re: Build Parcel using Build Extent

Re: Pro Fabric - Layer Cannot Be Edited Please Change The Layer Elevation Units

Re: Parcel Fabric correction methods??

Re: Parcel Fabric correction methods??

Re: Parcel Fabric correction methods??

Re: Merge Points: Inconsistent Behavior?

Re: Total Distance when drawing polylines in the Traverse Tool

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

Re: Help Entering Meets & Bound Call

Re: Help Entering Meets & Bound Call

Re: Help Entering Meets & Bound Call

ArcGIS Pro .Net SDK 3.7 for COGO Traverse

Re: Connection lines creating new vertices when cr...

PLSS Editing

ArcGIS Parcel Fabric - SDK for Add-ins and Scripting