Latest Contributions by Scott_Harris

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

@RobBlash @Melissa_B  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

@RobBlash Great! We like Ideas that have the requirements spelled out, but we can sometimes infer what is required based on all the feedback we get. Thanks for adding a new Idea with your specific requirements.  ... View more

@RichardFairhurst2  You said that layers must be Selectable and Editable.  Both of those requirements should only apply to the target layer.  The source layer only needs to be Selectable in ArcMap, not Editable. Please verify this is still true for the source layer in Pro. Yes, this is still the case in Pro. Only the target needs to be editable. Source and target layers will both need to be selectable. I'll make sure this is clear in the documentation. -- You also did not indicate that a layer must be Visible. That is required in ArcMap. Yes, layers are required to be visible in Pro in order to work in the tool. --- Do features flash when clicked on the map or through single clicking an item in the dialog as part of Attribute Transfers in Pro? Yes, exactly, the features flash in the map when you single click on them in the pop-ups. ... View more

Hey @RobBlash we are aware of that Idea, which I think most closely matches this one (at least some of the comments and/or merged ideas: https://community.esri.com/t5/arcgis-pro-ideas/multiple-field-mapping-scenarios-in-editor/idi-p/1004475 but do not have it in the product plan yet. ... View more

Thanks for the feedback @RichardFairhurst2 . I'll try to address your questions/comments below. The help topic examples indicate that the source and target dialogs will now appear if there are at least two feature layers each with a feature at the location I clicked on my map.  This is probably due to the field mapping for copy/paste and attribute transfers continuing to be merged together in Pro, which is different from ArcMap. The source and target pop-up windows will be available via the chip that appears on the map if there are overlapping features detected during the source click and/or the target click. The current help topic is correct about this. --- Am I correct in assuming that the list order of the layers is controlled by the layer order in the Table of Contents? No. At 3.5, The list of features in the pop-ups didn't have a pattern to it. We fixed this in the next release, and it will be sorted by drawing order then by Display Expression. --- Am I correct in assuming that multiple features for that layer will appear in the list and not just the top feature?  That should be illustrated and explained by the help. Yes, this is illustrated in the help at 3.5, --- I also notice that unlike ArcMap, the Pro dialog does not provide access to the complete list of feature attributes. I frequently use that aspect of the dialog in ArcMap rather than just relying on the feature display value and was not expecting to see the full field list dropped.  In it's absence, the help should point out the importance of setting up the layer Display expression as controlling the value that appears in the second column. I agree. The doc will need to make this clear. We will fix this. --- In ArcMap, the layers used and displayed in the dialogs by the Attribute Transfer tool are limited to layers that are marked as both Selectable and Visible Is all of that still true for Pro? If so, that behavior should be mentioned in the Transfer Attribute help. That behavior has not changed. Layers must be Selectable and Editable to work with Transfer Attributes in ArcGIS Pro. The doc will need to make this clear. We will fix this as well. --- Thanks again for the valuable feedback!       ... View more

At 3.5 the topology combo box can now be added to a custom group on any ribbon tab: ... View more

At 3.5 the 'Templates not listed' banner will no longer flash on/off when collapsing or expanding groups of templates. ... View more

Thanks for the reply @RTPL_AU . If you hit this editing bug again feel free to reach out to me. I'll direct message you my contact info. The ArcGIS Pro Editing team is very interested understanding the problem. ... View more

Hi @RTPL_AU  Regarding item 2, During an edit session, Pro will stop showing the edited geometry once an edit is completed (press F2, etc) and revert to showing the old geometry on screen until you save and refresh the map. You can still interact with the geometry in its new location (edit vertices will show the correct geometry while using the tool but revert to display the last saved version when you finish the tool operation.) The ArcGIS Pro Editing team is not aware of a bug that fits this description. Do you have a bug number that I can look into? If not, I have many more questions, but I'll try to keep it to a minimum. Is this with every workspace type (ex. File Geodatabase, shapefiles, feature services, enterprise geodatabases)? In every project? Does clearing the display cache resolve it? This button in Options > Display: Thanks for any more info! -Scott ... View more

@HbAGeoinfo That is unexpected behavior. You should be able to see the features you are editing without having to save edits. Are you able to contact Esri Technical Support to see if there is something specific about your data or install of Pro that might be causing it?  Things I would try in this order: Clear the local cache (options > Display > Local Cache > clear cache now button) Try it in a new project. Try it with different data. Try it with data in a different type of workspace (ex. if you are working with Shapefiles, switch to File Geodatabase feature classes). Reinstall ArcGIS Pro Soft reset of ArcGIS Pro and try again. Clean uninstall of ArcGIS Pro and then reinstall and try again. For the last few steps, I would recommend working with Esri Technical Support if you can. ... View more

@MikeSmith8 try making the Z values of the overlapping endpoints a bit different. If they are the same, the Merge tool will output a singlepart feature. If they differ, it will output a multipart feature. You can also accomplish this with differing M values if your lines are M-enabled. It also sounds like your trails could be managed using linear referencing, that way you can have a table of "surface types" that can produce a layer based on the surface type at measured intervals. If you did that, you could then produce the layer whenever you need it by running this tool: https://pro.arcgis.com/en/pro-app/latest/tool-reference/linear-referencing/make-route-event-layer.htm   ... View more