I'm curious: What's the use case here?
And what does "consecutive" mean in your imagined context? Is it consecutive in the attribute table? Or consecutive in some sort of topology/flow, like a Utility Network?
An example use case would be me selecting parking stalls in a parking lot. There are numerous parking stalls in a row. Sometimes I need to quickly select only 10 of say 80 stalls in a row.
The process right now is counting manually and selecting manually then to get the say 10 stalls.
Consecutive in the above example is consecutive in the row of parking stalls.
Lots of other examples.
Another solution would be having a dynamic "count" indicator on the mouse when in select mode that shows how many features are selected.
You could just do a model to iterate over 10 loops doing a select by layer with the ADD to selection option... This approach assumes the features intersect in some way.
Is the selection simple? You don't actually say if the features intersect, if not that would require some sort of proximity operation. Why 10, 10 is good for you but not enough for another. Then you have to deal with multipart features, what about features that touch but not even the same geometry. So what the brain thinks is easy could be a computational nightmare, especially if the next person who comes along and asks for the next million...
That's why a lot of geoprocessing tools are atomic, just do one thing, and you could the more complex selection logic with a model.
Scripting is often slicker and faster.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.