[PATCH] GML3 N-E axis order not handled with projected systems
|Reported by:||Jukka Rahkonen||Owned by:||warmerdam|
|Severity:||normal||Keywords:||srs axis ordering|
EPSG:3047 is defined to have axis order Northing-Easting. However, ogr2ogr from gdal 1.8.1 handles coordinates as Easting-Northing even if the coordinate system in given as urn-style.
<gml:location> <gml:Point gml:id="p26127610" srsName="urn:ogc:def:crs:EPSG::3047"> <gml:pos>6763247.267 400218.659</gml:pos> </gml:Point> </gml:location>
It would be useful to have a new parameter in ogr2ogr so that user could define the correct axis order. There are several reasons for this. Lots of GML3 files have srsName in plain EPSG:3047 format. Flipping axis with such data automatically could break things with older data and applications. Data errors with wrong axis order are also pretty common but user could solve them easily with the flip axis parameter. It might also be necessary to define also the axis order when overriding the source srs with the -s_srs parameter. Parameter name could be something like -axis_order and it could take values "en" or "ne". Perhaps also "latlon" and "lonlat". Default would be "en".
Change History (9)
comment:3 by , 11 years ago
|Component:||default → OGR_SRS|
|Keywords:||srs axis ordering added|
|Summary:||GML3 N-E axis order not handled with projected systems → [PATCH] GML3 N-E axis order not handled with projected systems|