Latest Contributions by TimHodson

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

@SarahSibbett  thanks for the additional info. This is very helpful. I'll research further, and report back here. Just to confirm though: the results shown in the video above when not projecting on the fly and with "No topology" set... those results are what is expected, correct? ... View more

Hi @MizukiKayano2 , Thank you for the new videos. I've simulated your scenario. Below is a video using the Align Features tool, with the "Snap line ends to path" option turned on, and with topology turned off altogether. ("No Topology" set in the Quality tab) Does this get you to your intended end result? -Tim ... View more

Hi @MizukiKayano2 and @CathyAppleton Please try the option to "Snap line ends to path"and let us know if it solves the problem.  This option is the most conservative in terms of introducing new vertices and is much better at preventing the creation of bends in the lines. -Tim ... View more

Hi @SamuelLingeman - would you please provide some more information? A screen shot showing your entries would be good. If you could provide your data that'd be useful too. I'll send you a private message. Thanks, Tim ... View more

Hello @TomNeer and @DennisTebo  There is an add-in available that will set the ground to grid values whenever changing the active record. It leverages enhancements made to the Parcel Fabric API with 3.2. If you have 3.2 or higher, you can install the add-in from here. There are some schema changes required. To use the add-in: after installing it you opt-in to the functionality by creating two [double] fields on the Records feature class called 'DistanceFactor' and 'DirectionOffset'. Type in, or calculate the appropriate direction offset and combined scale factor values into these fields for the records in the records feature class. The map's ground to grid correction will change to the (non-null) values found in these fields whenever a record is activated. If the value in the activated record is null, then it will not change the currently set ground to grid value. Set Ground To Grid From Active Record You can also use the add-in button called 'Save Ground To Grid To Record' on the active record's heads up display menu to save the map's ground to grid correction values to these fields. Existing values will be overwritten. For all who use this add-in please provide feedback on its functionality; this will influence our implementation of the functionality in the core product in a future release. If you are a developer : - the code is available here. - in brief, with 3.2 the API provides a new event that is fired when the map's active record is changed. -Tim ... View more

Hello All, In ArcGIS Pro 3.1 this add-in was not refreshing the CAD layer properly after the tool was run. The workaround was to shut down and restart Pro to see the layer properly placed. For ArcGIS Pro 3.2 and higher a new version of the add-in is available that properly refreshes the layer. If you are using ArcGIS Pro 3.2 or higher, it's recommended that you download the latest version of this add-in from here.  In general, add-ins are designed to be forward compatible, however in some instances changes in the underlying .Net SDK require that a newer version be compiled to get improved functionality, as is the case here. If you have the prior version installed, first remove it, and then replace it with this version. -Tim ... View more

Looking forward to hear all of your feedback! With today's release of 3.2, here’s the updated doc that covers the support for the new measurement types in the least squares adjustment. See the section called “Geodetic azimuths and ellipsoid arc distances in the least-squares adjustment”. Also, the following help doc has been updated to include the new step (Step 5) in the configuration to ensure that the adjustment analysis layers for Geodetic Azimuth and Ellipsoid arc distances show up in the table of contents when you run the least squares: https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/use-geodetic-directions.htm -Tim   ... View more

With soon to be released ArcGIS Pro 3.2, the above mentioned behavior with the Planarize tool and COGO attributes has been changed. The COGO will now not be recalculated on the lines that are only snapped. Otherwise, when the lines are split where they intersect, the software will continue to work as it currently does (in 3.1 and prior), with COGO distances recomputed/re-proportioned and their COGO Type set to "Computed". ... View more