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 replacing rasterio with gdal, gdal.warp() seems to be producing a raster that is clipped on one of the edges. I've tried a number of parameters including outputBounds with no success.
For example, comparing the previous BLE benchmark inundation raster for 12040101 (left) with the new raw BLE depth raster (middle) and the GDAL transformed (using gdal.warp() overlaid on the first image) shows that the bottom of the grayscale image is missing ((right).
This issue might be ignored. It will mean that create_ble_benchmark.py will import both rasterio and gdal, but there do not appear to be any conflicts and this is a seldom-used script that doesn't impact FIM pipeline at all.
The text was updated successfully, but these errors were encountered:
When replacing
rasterio
withgdal
,gdal.warp()
seems to be producing a raster that is clipped on one of the edges. I've tried a number of parameters includingoutputBounds
with no success.For example, comparing the previous BLE benchmark inundation raster for 12040101 (left) with the new raw BLE depth raster (middle) and the GDAL transformed (using

gdal.warp()
overlaid on the first image) shows that the bottom of the grayscale image is missing ((right).This issue might be ignored. It will mean that
create_ble_benchmark.py
will import bothrasterio
andgdal
, but there do not appear to be any conflicts and this is a seldom-used script that doesn't impact FIM pipeline at all.The text was updated successfully, but these errors were encountered: