Currently, when adding in data which is in a different datum to that of the map properties, ArcGIS Pro assigns a datum transformation based on the maximum spatial extent of ALL the layers and basemap listed under the Contents pane. If you have a Esri basemap then this spatial extent will be a global extent, which is seldom the scale at which I work (and I suspect the scale at which most of us work).
My idea is to either (1) drop the basemap from any transformation calculations, or (2) under Project>Options, provide the user with the option to exclude the basemap from any datum transformation calculations.
It is implemented in ArcGIS Pro 3.4 release. Thank you all for your suggestions and feedback.
Beginning in ArcGIS Pro 3.4 you can now choose to ignore the extents of any basemaps when transformations are presented in this list and limit the extents considered to the operational layers of the map only. In the map and scene application options, under the Spatial Reference heading, check Ignore the extents of basemap layers when listing and automatically choosing transformations.
See the Ignore the extents of basemaps section in the Specify a datum transformation topic.
Wonderful, thank you so much.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.