Bug
The Spatial Join tool returns different results if it is used in ModelBuilder or via a Python script.
| Bug ID Number | BUG-000147813 |
|---|---|
| Submitted | March 22, 2022 |
| Last Modified | February 11, 2025 |
| Applies to | ArcGIS Pro |
| Version found | 2.9.2 |
| Operating System | Windows OS |
| Operating System Version | 10.0 64 Bit |
| Status | Will Not Be Addressed |
Additional Information
The difference in behavior happens due to projection on the fly when the spatial join target and join features are in different coordinate systems or datums. When the tool is run with the data added to the map in ArcGIS Pro (either in the geoprocessing tool user interface (UI) or in ModelBuilder), it uses the Datum Transformations from the map which were automatically selected when adding the layers to the map. When running the tool from a standalone Python, or if the transformation is cleared from the map, or if a new map is created, do not add layers, and run the tool, the same projection on the fly does not occur, and the results may be different. Use the Project tool to project both datasets into a common spatial reference and the result of Spatial Join and other spatial operations are always consistent. Learn more about how coordinate systems affect geoprocessing results at the following link: https://pro.arcgis.com/en/pro-app/latest/tool-reference/appendices/spatial-reference-and-geoprocessing.htm#ESRI_SECTION1_47C963B12E2B4D32AE65BBB9D6D747D7.Steps to Reproduce
Bug ID: BUG-000147813
Software:
- ArcGIS Pro
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App