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
We have a cryptic problem when creating a cube that involves a coordinate transformation. So far, we only have this problem when running gdalcubes through Conda with the r-gdalcubes Condaforge package. Creating the cube works when there is no coordinate transformation necessary between the original files and the cube view, or when going from 4326 to 3857. However, when going from 4326 to 32198 or 6623, we get this error (with debug enabled):
However, the same code works well outside of Conda. I'm not sure whether this is an issue with the versions of proj or gdal packaged with r-gdalcubes, whether it's an issue with the r-gdalcubes-feedstock, or whether it's an issue with newer versions of proj that I don't have on my machine. Any ideas how we can address this issue ?
The text was updated successfully, but these errors were encountered:
After more investigating, this seems to be an issue with coordinate transformations to certain CRS only. For example EPSG:4326 to EPSG:6624 works well, but not to 6623. Same with 32198 not working, while 6622 works. This is probably an issue with Proj, but for some reason, we only have the issue when using Conda.
We have a cryptic problem when creating a cube that involves a coordinate transformation. So far, we only have this problem when running gdalcubes through Conda with the r-gdalcubes Condaforge package. Creating the cube works when there is no coordinate transformation necessary between the original files and the cube view, or when going from 4326 to 3857. However, when going from 4326 to 32198 or 6623, we get this error (with debug enabled):
[WORKER #2] [DEBUG] GDAL CE_Failure (1): Coordinate to transform falls outside grid [in gdalcubes/src/config.cpp:gdal_err_handler_default:107]
However, the same code works well outside of Conda. I'm not sure whether this is an issue with the versions of proj or gdal packaged with r-gdalcubes, whether it's an issue with the r-gdalcubes-feedstock, or whether it's an issue with newer versions of proj that I don't have on my machine. Any ideas how we can address this issue ?
The text was updated successfully, but these errors were encountered: