[Gdal-dev] bug: ogr2ogr gml output

[Frank Warmerdam]

Peter.Rushforth at statcan.ca wrote:
> Hi,
> 
> Two bugs, in fact:
> 
> i) When an input gml file contains a feature which contains
> a property of the same name (although beginning with a lower-case letter
> as per gml conventions), ogr2ogr gets confused.  It appears that
> it is not case-sensitive.  When the output is also gml, spurious
> gml:featureMembers appear, as the simple property element has been
> mistaken for the complex feature element.  The issue is reflected
> in the gfs file produced (samples attached).
> eg. ogr2ogr -s_srs NAD83 -t_srs EPSG:3347 -f GML messed_up_features.gml gecu000e07g_e.gml  

Peter,

I have reproduced a problem with this dataset, and submitted a bug
report for this problem:

  http://bugzilla.remotesensing.org/show_bug.cgi?id=1478

I don't anticipate it being dealt with immediately.

> ii)  When translating a shape file with accented characters into gml,
> ogr2ogr outputs a file which it says is utf-8 encoded, but which won't
> parse and which contains iso-8859-1 codepoints. (sample attached).
> eg. ogr2ogr -f GML bad_encoding.gml shp/geco000e07a_f.shp

OGR is currently not character set aware and so this sort of problem
can happen quite easily.  There is an RFC out with the aim of addressing
this in GDAL 1.5.  If you wish, you could file a bug on this issue, and
we can review it once the RFC is implemented.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org