I have had this error message show up if the s_srs is not correctly auto detected or not present in the input file. I have used a combination of looking through other nonstandard meta data files present with the image sets or using a program like global mapper which has a good chance at guessing the correct s_srs and then specifying it with the -s_srs option. On Sep 12, 2014 11:19 AM, "Andre Joost" <[email protected]> wrote:
> Am 12.09.2014 04:54, schrieb Love: > >> Hi, >> >> The gdalinfo in my post is the gdalinfo of the subdataset 37. I have also >> tried gdal_translate but when I tried to use gdalwarp using the >> gdal_translate output, it has error. I really need to use gdalwarp so that >> I could project the image into epsg:4326(+prj=longlat). If I'm going to >> use >> the gdal_translate I am ask to indicate the gcp which is not good in my >> case because I have many hdf files in my local directory and maybe they >> have different gcp and I need to batch process them later using the >> gdalwarp with the +proj=longlat command. What could be the solution? >> > > gdalwarp needs the -geoloc switch, and the target extent with -te. See > also <http://osgeo-org.1560.x6.nabble.com/gdal-dev- > Geolocation-Arrays-td4372909.html> > > There does not seen to be any progress on this issue. > > The values for -te can be found with gdalinfo on the subdataset. > > HTH, > André Joost > > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
