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
lib/python3.13/site-packages/rasterio/merge.py:321: UserWarning: Ignoring nodata value. The nodata value, -3.4028234663852886e+38, cannot safely be represented in the chosen data type, float32. Consider overriding it using the --nodata option for better results. Falling back to first source's nodata value.
warnings.warn(
True
The warning message there is probably related. I'm not sure why rasterio is returning all zeros just because it can't handle the nodata value. I think this bug is worth reporting to rasterio.
Description
Hi, I'm not exactly sure what's causing this issue, though I have a suspicion it might be related to compression of geotiffs.
When data is downloaded from the UK environment agency's LIDAR data programme, it shows in torchgeo as all zeros.
This can be rectified by running the file through
gdal_merge.py
- I'm unsure why.This is not an issue when reading directly with rasterio.
Steps to reproduce
Run the following file. It downloads the relevant data,
Checking for a dataset reading all zeros, I get:
Version
ff3d087 (latest main)
The text was updated successfully, but these errors were encountered: