You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @snowman2 ! So in regards to this, we did that initially, but started avoiding implementing it in our lessons. We found the way that the clip function reprojects vector data added a slight tilt to the data, which in turn tilted the outcome, which wasn't what we were hoping for in our lessons. I made a gist visually representing the difference we were finding, and this happened across landsat, MODIS, and NAIP data. https://gist.github.com/nkorinek/94a69b125bbb97044c2c49a60cf94643 if there's a solution here please let us know!
The reason I suggest to add the CRS is that it is a good practice to follow. Since this is a tutorial, I recommend adding it so users are used to doing it.
We found the way that the clip function reprojects vector data added a slight tilt to the data, which in turn tilted the outcome, which wasn't what we were hoping for in our lessons.
The tilt is due to the CRS of the raw raster data. MODIS shows this difference best since as it uses the sinusoidal projection. I think showing the tilt and then re-projecting the raster in the lesson will be valuable for users to see.
https://www.earthdatascience.org/courses/use-data-open-source-python/multispectral-remote-sensing/modis-data-in-python/
This is where I noticed it. I would recommend going through and making sure it is used in other clipping examples.
https://corteva.github.io/rioxarray/stable/rioxarray.html#rioxarray.raster_array.RasterArray.clip
https://corteva.github.io/rioxarray/stable/examples/clip_geom.html#Clip-using-a-GeoDataFrame
This ensures that the geometries are the same CRS as the raster when clipping.
The text was updated successfully, but these errors were encountered: