Hi Nicole, I have not worked with this dataset or with these exact projections and can only speculate, but since no one takes a stab at it…
Have you tried experimenting with leaving out the -tr and/or -tap parameters? My first thought was that it might be a problem with source or target datum, but that seems not so likely. Still, also EPSG:32232, which uses WGS 72. If you have rally old data it might be that. In any event, I’d advise inspecting the output of gdalinfo for both your target and your 2006 version. Chris -- Christine (Chris) Waigl - [email protected] - +1-907-474-5483 - Skype: cwaigl_work Geophysical Institute, UAF, 903 Koyukuk Drive, Fairbanks, AK 99775-7320, USA > On Jan 26, 2017, at 6:28 AM, Nicole Stoffels <[email protected]> wrote: > > Hi, > > I am trying to reproject the CORINE 2012 dataset from LAEA (EPSG:3035) to UTM > 32 (EPSG:32632). I use the following command: > > $ gdalwarp -overwrite -s_srs EPSG:3035 -t_srs EPSG:32632 -tr 100 100 -tap > -dstnodata '-9999' g100_clc12_V18_5.tif corine2012_utm32n_test.tif > > In the past years my colleague used ArcGIS for this operation, but since we > switched to Linux, I have to find a new solution. When I load the new dataset > generated with gdalwarp to QGIS and compare it with the old 2006 version > built in ArcGIS, I have an offset of approximately 15m south and 3m east for > the single raster squares. > > Now I am not sure if I simply forgot an important flag in my gdalwarp-command > or if the problem simply lies within ArcGIS (my colleague used the standard > options that were proposed). > > Thank you for any ideas, > > Nicole > _______________________________________________ > gdal-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/gdal-dev
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
