-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Reading certain tiffs with geotiff
is wrong if the CRS is not WGS84
#32
Comments
i've tracked this down to in
tries to unpack This is because |
geotiff
🐛 geotiff
🐛
The issue is fixed by changing https://github.com/EcoJulia/SimpleSDMLayers.jl/blob/07ecfb6495d7bcd186210a77c0781e6fc1397c3d/src/datasets/geotiff.jl#L68
is wrong? in the example tiff, |
Yeah, unproperly formatted geotiffs happen (you should see the TerraClimate data). It's weird because the CHELSA data are usually very clean. I'll take a look - very bad code smell to have a |
geotiff
🐛 geotiff
is wrong if the CRS is not WGS84
@gottacatchenall / @karinorman - I am actively trying to fix this today, FYI. There's a reprojection function in ArchGDAL which should do most of the work for us. |
While working on this, GEO-BON/bon-in-a-box-pipelines#10, we realized that some types of missing values throw an error when trying to load
What happened?
Reading layers in with
geotiff
, we run into several issues with missing/NaN values in geotiffs.As an example
fails with the below error where the chelsa tiff is available here
Stacktrace
The text was updated successfully, but these errors were encountered: