[gdal-dev] GDAL 3.0.0 / Proj 6.1.0 Shapefile import coordinates X/Y transposed?

[Simon Eves]

That would explain it.

I just found RFC 73 and some other stuff in the docs, but perhaps you could
put it in the main 3.0 Release Notes? :)

Thank you.

Simon

On Fri, May 24, 2019 at 1:50 PM Even Rouault <even.rouault at spatialys.com>
wrote:

> On vendredi 24 mai 2019 13:35:40 CEST Simon Eves wrote:
> > I feel like I'm asking a really dumb and naive question again, but here
> > goes...
> >
> > Our geo importer loads polygons in what I assume is a very standard way.
> > The importer code has not changed in some time, and works fine built
> > against GDAL 2.3.2 and Proj 5.1, and also against GDAL 2.4.1 and Proj
> 5.2.
> >
> > When I build our system against GDAL 3.0.0 and Proj 6.1.0, everything
> seems
> > to work fine, and GeoJSON and KML files import correctly, but Shapefiles
> > result in all the geo being transposed in X/Y!
> >
> > Simplified code...
> >
> > sr = new OGRSpatialReference();
> > sr->importFromEPSG(4326);
>
> EPSG:4326 has lat,long order enforced by default in GDAL 3.0
> So either cope with it with the x,y you get.
> Or add sr->SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER);
>
>
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
>


-- 
<http://www.omnisci.com/>
Simon Eves
Senior Graphics Engineer, Rendering Group
OmniSci, 1 Front St. #2650, San Francisco, CA 94111, USA


Email: simon.eves at omnisci.com | Cell:  415.902.1996
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20190524/d9a353f7/attachment-0001.html>