We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://corteva.github.io/rioxarray/stable/examples/reproject_match.html
This is useful for making sure the CRS, resolution, bounds match for raster calculations as mentioned in the MODIS/Landsat/NAIP sections.
The text was updated successfully, but these errors were encountered:
Hey @snowman2 ! Thanks again for doing this review. In regards to reproject match, I had looked into this function before, but didn't ever find a time when we would use it? We only ever reproject a raster to match a GeoDataframe CRS, so I can't use it there. Is there somewhere else you were thinking of using this function? I may just not be fully understanding, apologies! Could be something to ad to the end of this lesson maybe? https://www.earthdatascience.org/courses/use-data-open-source-python/intro-raster-data-python/raster-data-processing/reproject-raster/
Sorry, something went wrong.
That would be a good location for it. It may also be useful to mention here: https://www.earthdatascience.org/courses/use-data-open-source-python/multispectral-remote-sensing/vegetation-indices-in-python/
It helps ensure the resolutions/CRS/extent all match up before performing calculations.
No branches or pull requests
https://corteva.github.io/rioxarray/stable/examples/reproject_match.html
This is useful for making sure the CRS, resolution, bounds match for raster calculations as mentioned in the MODIS/Landsat/NAIP sections.
The text was updated successfully, but these errors were encountered: