Latest Contributions by TimHodson

@-_Ashley-B-Potter_-  The responses above have good information, and here is some more background /overview. The parcel fabric uses the standard geodatabase topology. That topology gets created for you when you create a new parcel fabric, and there are geodatabase topology rules set up for you between the line feature class and polygon feature class for each of the parcel types you create. The standard editing tools and map topology will all work with the parcel fabric features. While there are also additional tools that work with the fabric, you are free to use any and all standard editing tools and GP tools with the parcel fabric features and parcel feature layers. Whether or not there is a topology rule does not really matter for your specific scenario, but as Jason  mentions, you do need to specify either Map topology or the fabric's gdb topology in the edit tab, to enable topological editing. Based on your description it sounds like the editing tools to explore/research for your scenario are: Edit a toplogical vertex Move a topology node -Tim ... View more

Hi @SarahSibbett - using the "Trace Lines" tool actually does modify the existing lines, and does not create new ones. The trace takes the existing COGO stored on the lines into the traverse grid so that you can fix/re-enter the values for that same set of lines. In this example it's a "one-course" traverse, but if you want to re-check the closure for the original entered values (usually in a closed loop), then you'd trace over the whole loop. After you type in the new COGO values the geometry will update, to adjust the traverse based on the type of closure chosen. For the "one-course-traverse" workaround, that one existing line would have its geometry updated, unless you've set the close point, force close setting, etcetera, as described above. ... View more

@SeanLyons @TaylorMcInnes08 @SarahSibbett  The other thing to consider as a workaround is to use the Traverse's "Trace Lines" tool. Set the traverse tool's Direction parameter to Radial, if you haven't already, and then save the project to make sure this setting is persisted with the map.   Trace over the circular arc line, and change the Radial direction to the corrected value. The geometry of the line will change. If the preference is to prevent the geometry change, then you can use the "Set Closing" button and click the other end of the circular arc. If needed, use the "Force Close" on the traverse tool settings under the burger button. This would be needed if the change in bearing results in the new end if the circular arc moving beyond the specified closure tolerance (the default closure tolerance is 0.3meters).     ... View more

@SarahSibbett @SeanLyons Yes it does make sense. In your workflows, would such a tool need to also update the geometry of the circular arc, or does it only need to recalculate the chord direction attribute from the re-entered radial direction? Or ... something else, for example- it only updates the geometry if: there is no fabric point at its end? a check-box option that is presented in the UI is checked? other? ... View more

@SeanLyons- a pop-up is a good option for this. You can configure the popup for the line layer to calculate the Radial direction (and other curve parameters) from the existing circular arc COGO attributes, and then present those in the pop-up list. Like this:   Radial Direction Arcade Expression: function DMS_North(azimuth){     return ConvertDirection(azimuth, {directionType:'North', angleType: 'Degrees'}, {directionType:'North', angleType: 'DMS', outputType: 'text', format: 'd[°]mm[\']ss["]'}) } var radius = $feature.Radius var arcLength = $feature.Arclength var chordDirection = $feature.Direction if( IsEmpty(radius) || IsEmpty(arcLength))  return var delta = arcLength / radius; var chordDistance = 2.0 * abs(radius) * Sin(abs(delta) / 2.0) if ( IsEmpty(chordDirection) ) return var isCCW = radius < 0.0 var isMajor = delta > PI * 2.0 var tangentDirection = chordDirection - (delta/2.0*180.0/PI) var radialDirection iif(isCCW, radialDirection = tangentDirection - 90.0, radialDirection = tangentDirection + 90.0) return DMS_North(radialDirection)   Tangent Direction Arcade Expression: function DMS_North(azimuth){     return ConvertDirection(azimuth, {directionType:'North', angleType: 'Degrees'}, {directionType:'North', angleType: 'DMS', outputType: 'text', format: 'd[°]mm[\']ss["]'}) } var radius = $feature.Radius var arcLength = $feature.Arclength var chordDirection = $feature.Direction if( IsEmpty(radius) || IsEmpty(arcLength))  return var delta = arcLength / radius; var chordDistance = 2.0 * abs(radius) * Sin(abs(delta) / 2.0) if ( IsEmpty(chordDirection) ) return var isCCW = radius < 0.0 var isMajor = delta > PI * 2.0 var tangentDirection = chordDirection - (delta/2.0*180.0/PI) return DMS_North(tangentDirection)   Chord Distance Arcade Expression: var radius = $feature.Radius var arcLength = $feature.Arclength var chordDirection = $feature.Direction if( IsEmpty(radius) || IsEmpty(arcLength))  return var delta = arcLength / radius; var chordDistance = 2.0 * abs(radius) * Sin(abs(delta) / 2.0) return Round(chordDistance,3)   Central Angle Arcade Expression: function RadiansToDMS(input_radians){     return ConvertDirection(input_radians, {directionType:'North', angleType: 'Radians'}, {directionType:'North', angleType: 'DMS', outputType: 'text', format: 'd[°]mm[\']ss["]'}) } var radius = $feature.Radius var arcLength = $feature.Arclength var chordDirection = $feature.Direction if( IsEmpty(radius) || IsEmpty(arcLength))  return var delta = arcLength / abs(radius) return RadiansToDMS(delta)           ... View more

Hi @RobertChaney - that message appears in cases where the end point and start point of the line feature are at the same location, or when there are feature vertices on top of each other. Based on your graphic this does not seem possible, however, it could mean that the line feature has overlapping segments that double-back and overlap. Would you please check the geometry to see if the number of segments are what you expect? I notice also that on the southwestern side there is a longer line that does not have the same geometric-pattern as the other shorter segments that form the circular arc.Was it your intention to include that longer line as part of the new circular arc feature, or should it have remained as its own line feature?   ... View more

Hi @SarahSibbett - this will be fixed in the next release: ArcGIS Pro 3.3. Additional note: the align features tool, when used with a parcel fabric, will also automatically merge points that would otherwise be co-located; this was an enhanced capability introduced in 3.0. This also ties in with the other thread on Align Parcels regarding preserving the older point. With ArcGIS Pro 3.3 Align Features will follow the same pattern as for Align Parcels and will preserve the older point (unless if the younger point is a fixed point and the older point is not.) -Tim ... View more

hi @CatherineRoloson , I was curious if you've investigated using the Import Parcel Fabric Points tool to achieve what you need? https://pro.arcgis.com/en/pro-app/latest/tool-reference/parcel/import-parcel-points.htm It has a parameter that allows you to specify a record name (create new or add to pre-existing): -Tim ... View more

For scenario #1 there is a solution coming in ArcGIS Pro 3.3. For scenario #2, it is also in the product plan, but may not make it into the 3.3 release. ... View more

From version 3.1 and higher, when using the Update COGO tool on very flat circular arcs, pre-existing Radius and Arclength COGO attributes are not overwritten. ... View more

For the latest code for Update COGO, including access and use of the map’s ground to grid corrections, see the Parcel Utilities Add-in. Install: https://arcg.is/0f5reS Code: https://github.com/Esri/parcel-fabric-pro-addins/tree/main/ParcelsAddin The configuration settings are designed to protect against the overwriting of good COGO: These settings are saved between Pro sessions. -Tim ... View more

Thanks @SarahSibbett - I totally understand the request in the idea, and it absolutely makes sense to have this consistency with Move tool and the way it behaves with Map topology in Pro. Thanks for clarifying! My previous responses are only to make sure anyone reading this post are aware of the "Snap line ends to path" capabilities as an approach to get around this current limitation in Align Features when working with parcels. When using the Align Features tool, I'd also recommend avoiding the option "Preserve shapes outside the alignment area", as this will add extra vertices at the locations that intersect the perimeter of the alignment area.   The methodology you describe with the Move tool also requires the "Stretch Topology" button to be turned on. For parcel boundaries this would (likely?) always be necessary.   On a separate but related note, we have development work in progress (release version TBD) to enhance the move tool to be aware of parcel edges, independent of layer visibility. -Tim   ... View more

Thank you @MizukiKayano2 @SarahSibbett for reporting this bug - I can confirm the tool does not complete when using the "Snap lines ends to path" option while projecting on the fly, and while "No Topology" is set. For your reference: BUG-000164978 On the other case, I see how we are getting different results, and how this idea applies. In my case with the videos above the topology had not yet been validated, whereas in your case the topology validation has introduced a vertex via the connection line, and so the polygon's segment is bending at that location. There is also a vertex on the line, but its behavior is as expected and the line does not bend at the vertex. To workaround this you could shrink the polygons to seeds first, run the align features just on the lines, and then reconstruct from seeds. Another approach is to run the SLACA (Simplify By Straight lines and...) tool with a small tolerance on all the surrounding parcel polygons to remove these vertices, and then run the Align Features. Both of these approaches seemed to be effective for me. ... View more