-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Gdalwarp producing multiple copies of input image at incorrect positions #10975
Comments
I could re-produce on Windows with GDAL 3.9.1. Without Corner Coordinates:
What is this coordinate system of n4.tif?
|
I think that the issue must have something to do with those arc-seconds. If I first warp the image into EPSG:4326 without any parameters, and then this interim image into the target extent, then the result looks good. I have removed all parameters which I thought are not essential.
|
…cs related to geographic CRS Fixes OSGeo#10975
Exactly. Fix in #10988 |
…cs related to geographic CRS Fixes OSGeo#10975
…cs related to geographic CRS Fixes OSGeo#10975
…cs related to geographic CRS Fixes OSGeo#10975
What is the bug?
Gdalwarp is producing artifacts in output when using -te arguments larger than bounds of the input
Steps to reproduce the issue
repro.zip
Inside the zip attached there is tiff file used as input. When running this through gdal with the following arguments:
-t_srs "+proj=longlat +datum=WGS84 +ellps=WGS84 +no_defs +type=crs" -of GTiff -co "TILED=YES" -co "BLOCKXSIZE=1024" -co "BLOCKYSIZE=1024" -co "BIGTIFF=YES" -wm 500 -wo "NUM_THREADS=ALL_CPUS" -multi -co "COMPRESS=ZSTD" -co "NUM_THREADS=ALL_CPUS" -dstnodata -32767.0 -ot Float32 -te -81.500000000000 28.500000000000 -81.000000000000 29.000000000000 -r near "n4.tif" "Repro_hgt.tif"
There are copies of the input produced on the left and right side of where the actual input should be on the resulting image.
Input image:
Resulting output:
Versions and provenance
I have tested with multiple versions, including 3.6.2, 3.9.2 (from QGIS install), as well as 3.10.0dev-d04e73dfbd from a source build all with the same result.
Additional context
No response
The text was updated successfully, but these errors were encountered: