I just submitted a bugreport for this issue
https://github.com/OSGeo/gdal/issues/10512
On Fri, Jul 26, 2024 at 12:42 PM Calogero Mauceri
wrote:
> Thanks Javier for your reply.
>
> I'd like to avoid changing the source file work around.
> We are using gdalwarp C++ API as part of a general applica
Thanks Javier for your reply.
I'd like to avoid changing the source file work around.
We are using gdalwarp C++ API as part of a general application that can
open any kind of file.
On Fri, Jul 26, 2024 at 12:26 PM Javier Jimenez Shaw
wrote:
> Hi
>
> I do not know if there is anything wrong in
Hi
I do not know if there is anything wrong in GDAL. It looks like
As a workaround, you can first convert the projection to be centred at
lon=0 with something like this (I kept the same radius as the original to
minimize distortion). You can add bilinear interpolation or not, as you
wish.
gdalwar
Hi,
I'm rendering a 256x256 tile from a mercury dem. I noticed the gdalwarp is
producing a bad output when using interpolation with the following command
gdalwarp -of PNG -r bilinear -t_srs '+proj=eqc +a=2439700 +b=2439700
+lon_0=0.00 +lat_0=0.00 +x_0=0 +y_0=0 +units=m +no_defs' -ts 256
2
