Latest Contributions by TimHodson

In general, the goal is that bearings and distances stored on the COGO attributes match the record found on the original document. If there are a set of condo footprints on a document that are identical in all respects aside from their orientation, then it makes sense to be able to make a copy of one "footprint template" and then after moving and rotating the copy by a specific angle, update the bearings from the copied lines using that entered angle in order to match the record on the document for that newly positioned condo footprint. ... View more

@NabilDroby1- thank you for the video! It helps a lot to understand what you are requesting. I have made a video showing a similar (same?) workflow using the traverse in Pro. From what you show in your video, this same capability is already available in Pro, the Start point arrow button/tool that you are using in the ArcMap traverse is the same as the Set Start button in Pro. The End point arrow button/tool you are using in the ArcMap traverse is the same as the Set Closing button in Pro. After the traverse file has been loaded, and you choose the End point, you see the mislcose, and you can then click the Closure tab to adjust the traverse. Note in this case the closure tolerance is set to 0.01 feet, instead of the default 1 foot. As mentioned by Amir, using the higher closure tolerance will automatically adjust the traverse for you. The numbered courses feature was added in ArcGIS Pro 3.3. Does this cover your scenario? Thanks, Tim ... View more

Hi @NabilDroby1  Thanks for adding the idea. Also, in case you are not aware, among the Measure tools there is one to measure Direction and Distance between two locations. You could add this to the quick access toolbar. Does this help for your scenario? -Tim   ... View more

Hi @NabilDroby1  Thank you for the response. We have some further questions about Misclosure As X/Y. We have seen and understand the reasoning for adding the Direction as as part of the Misclosure As Direction/Distance, but we'd still like some further information on the value of also including the Misclosure As X/Y. It's the same information in a different form. We are trying to avoid adding too much information in this part of the UI unless it's absolutely necessary. Are there any negative impacts to your workflows and requirements if the Misclose as XY were not present? With regards to your other request to be able to check the misclosure along the way, would you please create a new idea for that? Thanks, Tim ... View more

In the ArcMap Traverse tool, the misclose information includes the difference in XY. We are looking for feedback from everyone on whether or not to include it in the Pro Traverse. Is there value in representing the closure as X and Y differences as well, or is Direction and Distance enough? Please let us know if the XY representation gives you additional capabilities\business value that the Direction and Distance does not. Thanks. Option 1: Misclose: N7-56-22W, 4.86 ft Misclose XY: -0.671, +4.813 Misclose Ratio: 1 : 89 Calculated Area: Closure Method: Compass (default)  Option 2: Misclose: N7-56-22W, 4.86 ft Misclose Ratio: 1 : 89 Calculated Area: Closure Method: Compass (default)   ... View more

Glad to hear you got it resolved! ... View more

Hi @-_Ashley-B-Potter_- here is the help related to using the Move tool with selected points: https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/setparceledgetopologymovepoints.htm Please confirm that: There is a single fabric point selected Map topology or geodatabase topology is enabled The Stretch topology button is turned on   ... View more

Hi @NickN - thanks for the update. Glad to hear the issue is resolved by splitting the polylines into 2-point lines. ... View more

Hi @NickN - This one's a bit tricky to work out without the data. What is the scale of the screen-shots above? Are they zoomed in to 1:1? Trying to understand the size of the gaps shown. Yes, that preview is definitely odd, can you please confirm that those lines are actually two-point lines? I'd expect to see something like that if the green and purple lines were polylines, and had not been split at the bend. For example, in the second screen-shot, are there 2 purple line features, or 1 purple line feature in the data extent shown? Does the problem only happen when merging points that involve these specific lines, or does it happen in all cases for all of your data? Thanks. -Tim ... View more

Hi @BryanJohnstone, First a quick note that for ArcGIS Pro 3.4 to be released later this year, there will be an enhancement to the Move tool that will address this workflow. We will introduce this in the What's New Parcel Fabric Meetup in November. There are a few other approaches to try: The Merge Points tool Align Features tool, using the setting "Snap line ends to path" Align Parcels tool Note there is related information and discussion at this post. -Tim ... View more

Hi @SamanthaMack - I have a few questions as follows: Is the vector data set and raster data set on the same modified projection? Are you able to use this add-in as it stands for the vector data, in other words, the engineers have provided the base projection and the transformation parameters? Related question: is the vector data represented in CAD? Are you able to share an example dataset? I will send a private message to exchange e-mails. -Tim ... View more

@MizukiKayano2 Thanks for entering this new idea. Just in case anyone reading this was not previously aware; you can select the row in the traverse grid and the corresponding line is selected in the map. Similarly, you can select the line in the map and the corresponding row in the grid is selected. This is one way to help get oriented and relate the grid entry to the corresponding line feature in map. However, it does require interacting with the grid/map, and so this idea of showing the numbers on the map all at once would reduce the need to select rows in the grid. -Tim ... View more

Hi Pascal, Below is some code to do that. -Tim static void Main(string[] args) { Host.Initialize(); Uri service = new("https://myserver.esri.com/server/rest/services/myFeatureServiceName/FeatureServer"); ServiceConnectionProperties serviceConnectionProperties = new(service); Uri portal_uri = new("https://myserver.esri.com/portal/"); ArcGIS.Core.SystemCore.ArcGISSignOn.Instance.SignInWithCredentials( portal_uri, "admin", "adminpassword", out _, out _); if (serviceConnectionProperties != null) { //connect using var featService = new Geodatabase(serviceConnectionProperties); ParcelFabric myFabric = featService.OpenDataset<ParcelFabric>("L0MyParcelFabric"); var version = myFabric.GetDefinition().GetSchemaVersion(); } }   ... View more

@-_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