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
When I inspect the raster with gdalinfo, I see the correct minimum value (0), and the raster's nodata value is correctly stated as well (2147483647.0). gdalinfo https://storage.googleapis.com/natcap-data-cache/global/landscan-pop/landscan_2023.tif will demonstrate this.
And when I download the file and read in the raster with GDAL, I can see that the minimum pixel value matches the nodata value:
Because of this mismatch between the nodata value and the rio-tiler-identified pixel minimum, the rest of the percentile breaks are being incorrectly identified.
Any suggestions? Thanks!
The text was updated successfully, but these errors were encountered:
Greetings! I have a TiTiler instance (which of course is using
rio-tiler
under the hood), and I have a COG (https://storage.googleapis.com/natcap-data-cache/global/landscan-pop/landscan_2023.tif) that I am attempting to render tiles for. The problem is thatrio-tiler
appears to be incorrectly reporting the minimum pixel value.When I inspect the raster with
gdalinfo
, I see the correct minimum value (0
), and the raster's nodata value is correctly stated as well (2147483647.0
).gdalinfo https://storage.googleapis.com/natcap-data-cache/global/landscan-pop/landscan_2023.tif
will demonstrate this.And when I download the file and read in the raster with GDAL, I can see that the minimum pixel value matches the nodata value:
However, when I use
rio-tiler
to get statistics, the minimum value is incorrectly stated:Because of this mismatch between the nodata value and the
rio-tiler
-identified pixel minimum, the rest of the percentile breaks are being incorrectly identified.Any suggestions? Thanks!
The text was updated successfully, but these errors were encountered: