Opened 17 years ago

Closed 14 years ago

#1478 closed defect (fixed)

GML Case Insensitivity bug?

Reported by: warmerdam Owned by: warmerdam
Priority: highest Milestone:
Component: OGR_SF Version: 1.4.0
Severity: blocker Keywords:
Cc:

Description (last modified by Mateusz Łoskot)

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).

Example: 

ogr2ogr -s_srs NAD83 -t_srs EPSG:3347 -f GML \
   messed_up_features.gml gecu000e07g_e.gml

Attachments (1)

gecu000e07g_e.gml​ (1.7 KB ) - added by warmerdam 17 years ago.
Problem input GML file.

Download all attachments as: .zip

Change History (4)

by warmerdam, 17 years ago

Attachment: gecu000e07g_e.gml​ added

Problem input GML file.

comment:1 by warmerdam, 17 years ago 

Note: 

With a debug build, I get an assertion failure reading the gml file. 
Some sort of unexpected state when popping a context.

comment:2 by Mateusz Łoskot, 17 years ago

Description: modified (diff)

comment:3 by Even Rouault, 14 years ago

Resolution: → fixed
Status: new → closed

Works now. Duplicate of #2709.

Note: See TracTickets for help on using tickets.