[Gdal-dev] gdalwarp, proj4 and Space Oblique Mercator problem

Even Rouault even.rouault at mines-paris.org
Wed Aug 5 14:25:09 EDT 2009

This projection is recognized by proj, but not by the GDAL module that
parses PROJ.4 strings into its OGC WKT model. I'm afraid there's nothing you
can do, apart from improving OGR to support this projection method and
posting the patch ;-)

Maybe a way of cheating could be to use a valid (and unrelated) OGC WKT
string and putting your proj4 string  into the EXTENSION parameter. See

Something like that might be worth trying (completely untested. No warranty) 
LOCAL_CS["unnamed",EXTENSION["PROJ4","+proj=lsat +lsat=5 +path=188 

----- Original Message ----- 
From: "ilumas" <anssisamuli at gmail.com>
To: <gdal-dev at lists.osgeo.org>
Sent: Wednesday, August 05, 2009 7:49 PM
Subject: [Gdal-dev] gdalwarp, proj4 and Space Oblique Mercator problem

Dear all,

I'm trying to re-project a USGS Landsat 5 scene with Space Oblique Mercator
projection with the following command:

gdalwarp -s_srs  '+proj=lsat +lsat=5 +path=188'  -t_srs EPSG:2393 input.tif

For some reason this fails:

ERROR 1: Translating source or target SRS failed:
+proj=lsat +lsat=5 +path=188

even though my proj -lp lists the lsat projection and the parametrization
seems appropriate to me (see below).

Any idea what's wrong and how could I solve this?



--8< from http://download.osgeo.org/proj/proj.4.3.pdf ---8< ----

landsat C E S I

This projection (not shown) is for use with landsat
satellite data and is a limited form of the more general
Space Oblique Mercator projection. The landsat satellite
number, n, must be in the range 1–5 and the path
number, p, must be in the ranges 1–251 for n = 1, 2, 3 or
1–233 for n = 3, 4.

--8< from http://download.osgeo.org/proj/proj.4.3.pdf ---8< ----

tmp> proj -lp |grep lsat
lsat : Space oblique for LANDSAT

tmp> proj
Rel. 4.4.9, 29 Oct 2004

tmp> uname -a

Linux 2.6.13-15.11-smp #2 SMP Fri Jul 28 11:01:31 EEST 2006 x86_64 x86_64
x86_64 GNU/Linux

-------  hdr file for the input ------

View this message in context: 
Sent from the GDAL - Dev mailing list archive at Nabble.com.
gdal-dev mailing list
gdal-dev at lists.osgeo.org

More information about the gdal-dev mailing list