[gdal-dev] how should SpatialReference::EPSGTreatsAsLatLong work?

[Even Rouault]

Le jeudi 15 mars 2012 10:00:58, Jachym Cepicky a écrit :
> Hi,
> 
> I'm trying to figure out, how OGRSpatialReference::EPSGTreatAsLatLong is
> supposed to be working -> I'm not able to get any proper result.
> 
> I'm playing with the python interface at this place (and assume, C-api
> would work similar way).
> 
> When I create OGRSpatialReference and import it from EPSG with the code
> 4326, I would say, EPSGTreatAsLatLong should return True:
> 
> from osgeo import osr
> sr = osr.SpatialReference()
> sr.ImportFromEPSG(4326)

--> use ImportFromEPSGA() instead of ImportFromEPSG() when you are interested 
in axis ordering. See http://trac.osgeo.org/gdal/wiki/rfc20_srs_axes

> sr.EPSGTreatAsLatLong()
> 0
> 
> Same applies, when trying the same with e.g. EPSG:3035
> 
> sr.ImportFromEPSG(3035)
> sr.EPSGTreatAsLatLong()
> 0
> 
> Both do have (accordi ng to http://epsg-registry.org/) north,east axis
> order, so I would asssume EPSGTreatAsLatLong would return True

EPSGTreatAsLatLong() does not take into account projected coordinate systems. 
See http://trac.osgeo.org/gdal/ticket/4329 with a prototype patch to improve 
that

> 
> Could anybody give me a hint, what am I doing wrong?
> 
> Thanks
> 
> Jachym