Raster data is referenced by choosing a point for one of the corners, and counting out the spacing of the pixels by their dimensions and number. This works when all pixels are of a uniform size, be it meters or degrees. However when you change projection, they are no longer the same size, and that's why raster projections dont match up perfectly.... If they were to match them perfectly, they would have to interpolate the pixel grid and generate new pixels which are equally spaced. When you change the projection of the viewing port in the contents, the data displays right because it bends and skews pixels but saved rasters dont do that. At least this is my understanding of the issue.
You're great to listen to. I'm gathering training materials, and you made this fun!
Raster data is referenced by choosing a point for one of the corners, and counting out the spacing of the pixels by their dimensions and number. This works when all pixels are of a uniform size, be it meters or degrees. However when you change projection, they are no longer the same size, and that's why raster projections dont match up perfectly....
If they were to match them perfectly, they would have to interpolate the pixel grid and generate new pixels which are equally spaced.
When you change the projection of the viewing port in the contents, the data displays right because it bends and skews pixels but saved rasters dont do that.
At least this is my understanding of the issue.