We think there's a bug with the Nearest Neighbor Interpolation technique when you switch from ArcGIS Pro 2.0.1 to 2.1. In 2.0.1, nearest neighbor runs fine and the interpolated output is generated in the same projection as the input (California Teale Albers). When we run the tool exactly the same way in ArcGIS Pro 2.1, the interpolated output ends up in the North Pole area. Is this a known bug?
Thanks,
Anna Studwell
sounds like the data being interpolated wasn't actually in that coordinate system but was being projected on the fly to the coordinate system of the data frame. (ie looking at it in the map isn't enough, examine its properties... ditto for the map)
or the output coordinate system wasn't set.
Can you report on both scenarios?