[gdal-dev] OGR GeoJSON transormation woes

Frank Broniewski hallo at frankbroniewski.com
Thu May 7 10:14:29 PDT 2020

Ah, I did not make myself clear enough. My intention surely wasn't to 
change any existing standards/formats, I believe especially the GeoJSON 
coordinate thing has been already sufficiently discussed. I was 
referring to the GeoJSON data I receive in my plugin or any future project.

I was merely musing how to approach the coordinate order problem for my 
next project. Using SetAxisMappingStrategy feels more like a patch to 
the problem.

I could as well make the input coordinates follow the standard axis 
order, do my transformation with well behaved coordinates and manipulate 
the output to match what QGIS needs. Just a different approach to the 
problem ...

Am 07.05.20 um 12:28 schrieb jratike80:
> Hi,
> I fear that such a change in GeoJSON would not really correct anything but
> rather move the confusion into another place.
> -Jukka Rahkonen-
> Frank Broniewski-6 wrote
>> But after reading all this stuff, I wonder if it would not have been
>> better/more right to "correct" the GeoJSON coordinate order from Lon/Lat
>> to Lat/Lon so that it matches the definition of EPSG:4326? I will have
>> to think about how to deal with geo data and the treatment of CRS in
>> future projects. Simply setting SetAxisMappingStrategy where it may fit
>> does not seem to be a very thought-out and future proof process in the
>> end.
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev

More information about the gdal-dev mailing list