Latest Contributions by Scott_Harris

@RTPL_AU  You can achieve this with the editing grid, snapping, and the anchors for the rotate tool. Turn on the editing grid. Set the grid's orientation and rotation using the command found on the grid settings pop-up - so that the grid aligns with the segment that you want to align to. Open the Rotate tool > hold CTRL key and click to place the primary anchor on a segment of the feature you want to align > hover over somewhere along same segment > hit S key to place the secondary anchor. Rotate until the segment is snapped to the inferred grid intersection.   ... View more

Hi @RTPL_AU This is possible at ArcGIS Pro 3.5 by turning on Curved Edges and/or Bezier Curved Edges within the Vertices and Nodes settings and enabling it in your map.   More info: https://pro.arcgis.com/en/pro-app/latest/help/editing/symbolize-vertices-and-nodes.htm https://pro.arcgis.com/en/pro-app/latest/help/editing/change-vertices-and-nodes-settings.htm   ... View more

Thanks for that info @Jeff-Reinhart  Regarding the error: "Edit operation failed. This layer's workspace is read only.": Where do you see it? Somewhere in the UI? Or is this error returned when you make edits using the SDK? Also, which version of ArcGIS Pro / SDK are you using? ... View more

@TD1  Just a thought, the Attributes pane has the ability to step through and review all features in a layer. If you have a particular field that specifies a sequence, you can set that field as the display field for that layer and then sort on that layer within the attribute table. Now you can step through all of the features in the layer consecutively and review and update attributes/geometry as needed. ... View more

@MarkusWall1  I'll close this out since it seems like a bug. If your original map still reproduces the issue, we'd definitely be interested in seeing the behavior to address the bug. The best way to do that would be to present issue to Esri Technical Support so they can log it. ... View more

@MarkusWall1 I'm not sure why you can't snap to the intersection of a line feature and a grid line. How about in a new project? Different data? Here I'm snapping to the intersection of the green line and my grid line (gray):   ... View more

@Jeff-Reinhart  What is the error that you are getting? Where is the data? Is it in the same geodatabase? Is it in the same feature dataset? ... View more

@SarmenBajari  My guess is a soft reset won't help. Esri Support would need to see the ErrorReport that @DanielFox1 mentioned above as well as the reproducible steps/data in order to file a bug report with the development team. ... View more

@MarcinLatos1 Can you clarify what you mean by selection handles? Are you referring to the handles that appear around graphic elements in a map or layout? Or the handles that appear when you are editing 3D objects in a scene? Something else? ... View more

@RobBlash  I was suggesting clearing the field mapping as a way to prevent unwanted transfers from the source to itself. An even easier "one-click" method is to mark the source layer as non-editable since editability is only a requirement for the target layer(s). See my comment here: https://community.esri.com/t5/arcgis-pro-ideas/attribute-transfer-tool-selection-chip-respect/idc-p/1621155/highlight/true#M35060 These would be considered workarounds until we can make the experience of the tool more transparent and easy to use. ... View more

@cmathers You mentioned that you are seeing source features show up in the chip. You can prevent this by turning off the Editability of the source layer while using the tool. Example: LayerA is my intended source and LayerB is my intended target: During the "target click", If I click on overlapping features from both layers, I will only have any overlapping features from LayerB showing up in the chip - any features from LayerA will be ignored by the tool. This how the tool has always worked, but I think introducing the chips has uncovered a bit of confusion about how the tool works - especially if your maps had source features beneath target features in the Contents pane. If that was the case prior to 3.5, those features would have never been optional targets since the topmost feature was the only one available to the tool. ... View more

Hi Melissa,  Regarding:  it doesn't matter if you clear the mapping and set an explicit source and target, the tool still overwrites data between source feature class features. I can't reproduce this. Can you share steps/data with me? I'll direct message you with my contact info. ... View more

Hi @Melissa_B  did you clear the field mapping that exists between the source layer and itself like I suggested above? Did you also try turning off editability of the source layer like I also suggested in my last comment to you? I think doing both things will help in your daily work. There are open Ideas that may address these issues: https://community.esri.com/t5/arcgis-pro-ideas/create-a-separate-field-mapping-for-the-attribute/idi-p/1617440/jump-to/first-unread-message https://community.esri.com/t5/arcgis-pro-ideas/multiple-field-mapping-scenarios-in-editor/idi-p/1004475 Regarding the doc, agree, it needs to be clearer. Adjustments are in progress. ... View more

Hi @Melissa_B If you clear the field mapping between the source layer and itself it should not being transferring attributes. However, I can see where you might be in a situation where you have a source feature overlapping the intended target feature. In that case, the new behavior of showing the chip for overlapping features would still show the chip asking you for the intended target of the overlapping features where you clicked. It comes down to editability. The key step for that situation would be to turn off editability of the source layer since that's not the intended target and it will not be found by any target clicks of the transfer attributes tool. Source clicks are still allowed in that case. For example, here my source is layerA and my target is layerB. If layerA has features that overlap features from layerB, as long as editability is turned off for layerA, I will only get the chip when there are overlapping features in layerB:     ... View more

@Melissa_B @cmathers  I'm sure you are aware, but I wanted to point this out to any others that are reading: If you don't want to accidentally transfer attributes from a source layer to itself you can clear the field mapping that exists for that layer as a target and a source: ... View more