|
POST
|
@Lebowski Since the first three courses reference the quarter section lines and don’t directly state any bearings, getting a “validated closure” for this deed description is not possible from my side. This is because the ¼ section lines will have direction differences and angle breaks that are not exactly 90 degrees, or 180 degrees, and they are not “exactly” north-south and “exactly” east-west. So, the first three courses below are “made-up” by me using some best guesses, but those will need to be properly determined on your side based on your existing lines, your map projection, and so on. However, that’s not your original question; the remaining courses after the first three show what to enter for the backsight angle mode. Note that the angles as entered are only persisted for the life of the traverse in the UI, but the directions are computed from your entered angles and are stored on the lines. S0-08-32E 2,682.55 S0-12-37W 34.32 N88-57-30E 1,369.52 +90-56-26 33.34 -90-56-10 1,465.18 +90-54-05 1,905.79 -135-9-54 26.43 +150-44-30 369.03 -177-08-56 321.46 -143-28-26 148.33 +116-14-03 136.9 +87-08-53 27.33 -75-50-30 1,370.48 +86-57-03 3,192.51 +90-21-25 1,500.34
... View more
3 weeks ago
|
0
|
0
|
78
|
|
POST
|
@Lebowski - I'd enter those as follows. Your line geometry and direction values will not match these because I adopted an arbitrary starting course, but the courses on 2-4 would be what I'd expect to work to close the traverse. Feel free to provide the whole description if you like.
... View more
3 weeks ago
|
0
|
2
|
422
|
|
POST
|
@Lebowski - I don't see your attachment, but the convention is to use a plus sign for the clockwise angle so if, for example, Angle2 is "clockwise 90 degrees 12 minutes and 55 seconds from the previous course" , then you would type "+90-12-55" instead.
... View more
3 weeks ago
|
1
|
4
|
427
|
|
POST
|
@Lebowski - yes, Also note that backsight mode for angles is only supported with 3.4 and higher. If the traverse is not closing then you could also try the "regular" deflection mode with the identical workflow, but my interpretation of the call is that it's backsight based, and so I'd expect that to work.
... View more
3 weeks ago
|
1
|
7
|
444
|
|
POST
|
@Lebowski - you first need to set the traverse options to use "Backsight" angle mode: Then type -90-56-10 into the direction field (this assumes your backstage units for Angles are set to DMS - let me know if you need help setting that) press enter and then type the distance and press enter again: You can confirm the angle is correct using the angle measure tool:
... View more
3 weeks ago
|
2
|
9
|
460
|
|
POST
|
Starting with ArcGIS Pro 3.7 there are new .Net SDK capabilities available for COGO (Coordinate Geometry) In this 45 minute presentation we first review the COGO basics in the context of the API, and then we introduce the classes and functions now available in the new COGO namespace: using ArcGIS.Desktop.Editing.COGO; Also attached please find the code used for the demos presented.
... View more
05-06-2026
06:04 PM
|
2
|
0
|
370
|
|
IDEA
|
Original request from @GIS-Chops : "It would be nice if Pro would update the COGO attributes of those lines based on the rotation angle that I enter in the rotate tool." Question for the community: Would there ever be a case where a typed-in rotation angle should not be applied to update the COGO Directions after the rotation?
... View more
02-12-2026
09:54 AM
|
0
|
0
|
162
|
|
IDEA
|
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
05-19-2025
09:53 AM
|
0
|
0
|
2089
|
|
IDEA
|
@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
02-05-2025
09:20 PM
|
0
|
0
|
2828
|
|
IDEA
|
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
02-03-2025
11:53 AM
|
0
|
0
|
2883
|
|
IDEA
|
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
01-31-2025
09:02 AM
|
0
|
0
|
1630
|
|
IDEA
|
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
11-19-2024
12:17 PM
|
0
|
0
|
3742
|
|
POST
|
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
11-14-2024
12:11 PM
|
0
|
2
|
2897
|
|
POST
|
Hi @NickN - thanks for the update. Glad to hear the issue is resolved by splitting the polylines into 2-point lines.
... View more
10-21-2024
01:27 PM
|
0
|
0
|
941
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 2 | 3 weeks ago | |
| 1 | 3 weeks ago | |
| 2 | 05-06-2026 06:04 PM | |
| 1 | 09-18-2024 12:38 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|