Thanks for the info and confirmation on an item I was unable to find in Pro.
So in short there is no setting in Arc Pro that I inquired about.
guess not
Rick, no, it doesn't look like there is a selection tolerance setting. I'm assuming you're finding it difficult to edit in Pro right now because of this? Do you have any examples (screenshots) of the type of data where you're able to work more efficiently in ArcMap with control over selection tolerance than when working in Pro?
Thank you!
As for editing in Pro vs Map just being able to grab vertices in line and polygon vector data when doing edits makes it way faster than having to expressly get on the vertices to move them - hence my question about the selection pixel tolerance - I am not snapping the vertices to anything just lining them up on the roads in the streets background map - when I can set the selection tolerance to 10 pixels it makes the edits go very quickly. Current project is fixing some road center line overlays for some data that was made back in 2012 for our catastrophic planning section folks - editing at 1:1000 scale - only reason I am using Pro is the speed at which I can scroll around on the map - 50 overlays with 4 - 8 lines per overlay that span quite a large area - scrolling around in the map using Arc Map is very slow.
Thanks, Rick. Does dragging a selection box around the point not work for you (rather than trying to click on the point)?
Kory - that just enables me to highlight something or activate it for editing.
What I am trying to convey is that with the selection pixel tolerance you can change when you are close enough for the cursor to change and activate the tool such that you can grab the vertices - in short a pixel tolerance of 10 is way easier to work with in an edit session than the preset of 3 pixels which seems to be the default in Pro - it is the default in Map but as I stated I can change that to 10 or whatever I want. By being able to have the tool to activate farther away from something it is easier to grab the vertices in a line or polygon once you have the object activated for editing - it is just way faster to work in this fashion than having to be right on the vertices to than left click and drag it wherever you want to - this setting has nothing to do with the snapping tolerance which controls the number of pixels on the screen that you have to be within to get a vertices to snap to another vertices in another object that setting is adjustable but it appears that when ESRI fielded Pro that setting for selection tolerance was not added by the programmers as an adjustable setting by the user - it appears to be hard coded in the program to 3 pixels.
Very annoying to be in a edit session and trying to work fast and you have to be right on a vertices to grab it to move it versus having to only get relatively close to enable you to have the tool to activate and thus be able to grab the vertices.
Drawing the selection box / line around an object merely activates that vector data for editing and subsequently making the vertices visible so you can move them/add them/remove them.
Open Map up and create a line object with say 10 or so vertices and play around with the selection tolerance setting and you will see what I am explaining for be able to grab the vertices to edit them change from the default 3 to say 10 or 15 at a 1:1000 or 1:1500 scale big difference in how fast you can get on a vertices to work with it.
Thank you, Rick. The additional details are helpful. I've shared your feedback with the editing team.
Hi all,
I was just looking for the same thing. I am trying to select a route at a specific location so I can see what the measure value is. Drawing a box will not work because a want a point along the route. It sounds like maybe I can make my route symbology larger (wider) so I can pick a point easier. I will try that but really thought I would be able to set a selection tolerance. I am using ArcGIS Pro 2.8 in windows.
I would love to see this setting as well! As a third-party developer, we have a custom selection tool that does a spatial query based on the clicked point. If a user's search tolerance isn't high enough, they have to be nearly pixel-perfect to select a feature, depending on their scale. The only workaround we've found is to programmatically increase the search tolerance and re-run the spatial query up to a pre-determined maximum value. For example, we may start with the default of 3, then keep increasing by 5 until we've tried 4 more queries; if nothing is found after that, we consider nothing to be selected and the user must try again.