Re: [gdal-dev] Confusing error behavior of OGR_L_GetSpatialRef

2018-11-14 Thread Even Rouault
Hi Sean, (re adding the list) > > This is driver specific behaviour. How can we reproduce ? > > I see it with this shapefile: > > https://github.com/Toblerity/Fiona/tree/master/tests/data/coutwildrnp.shp > > The .prj file contains > > GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_198

Re: [gdal-dev] Confusing error behavior of OGR_L_GetSpatialRef

2018-11-13 Thread Even Rouault
On mardi 13 novembre 2018 14:13:27 CET Sean Gillies wrote: > Hi, > > While debugging a problem with my Fiona project I realized that if > GDAL_DATA is not known, OGR_L_GetSpatialRef() (master branch and also > 2.3.2) can return a not-NULL spatial reference while also putting a > CE_Failure error o

[gdal-dev] Confusing error behavior of OGR_L_GetSpatialRef

2018-11-13 Thread Sean Gillies
Hi, While debugging a problem with my Fiona project I realized that if GDAL_DATA is not known, OGR_L_GetSpatialRef() (master branch and also 2.3.2) can return a not-NULL spatial reference while also putting a CE_Failure error on the error stack. Is this intended or is the error code perhaps one le