BUG-000107335 for ArcGIS Pro

Bug ID Number	BUG-000107335
Submitted	August 14, 2017
Last Modified	November 20, 2024
Applies to	ArcGIS Pro
Version found	2.0
Operating System	Windows OS
Operating System Version	10.0 64 Bit
Status	Will Not Be Addressed

Additional Information

Closing this issue as designed. This behavior is a result of the design decision for vector-feature selection in 3D to be done using the visual display within the view (ie: WYSIWYG / what-you-see-is-what-you-get). This design means that no matter what symbology the user use, clicking something in the view to select a feature works. It does not matter if a point feature is being rendered with a car symbol, a cube, or a billboarded stop sign. The downside is the features not being displayed from the current viewpoint (eg: features hidden behind other features, or features with symbols that are so small they've been culled from the view) unable to be selected by the visual selection tools. For this dataset, the results seem incorrect because it's not obvious that some of the features are being hidden at longer viewing distances. These features are very close together (10cm apart) in a world-extent coordinate system (Web Mercator) so, when the user zooms out, some of the features are effectively 'hidden' by their neighbors' symbols or culled because they drop below a min-pixel-size. Another approach for geometry-based selection is to generate a physical polygon feature and use 'Select by Location' against the points. This works regardless of viewing distance because it uses the feature's geometry and ignores feature layer symbology. We do not plan to change this behavior for the general screen-based selection tools in Pro. However, it's possible we could add an additional interactive selection mode, eg: a '2D extent selection tool', where the user gets to digitize in a 2D polygon onto the ground and we (effectively) run the 'Select by Location' tool in the background. If multiple users (including this one) request this extra selection tool option, we can look to add it in a future release.