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

[Jachym Cepicky]

On 15.3.2012 20:42, Even Rouault wrote:
>>
>> 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
> 

Oh, thanks for this hint. It does not solve my problem completely, but
it is something.


>> 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
> 

OK, that might be solution - will let you know.

Thanks!

Jachym

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
Url : http://lists.osgeo.org/pipermail/gdal-dev/attachments/20120315/8714cd7c/signature.bin