id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	state
2388	Format.GML.v3 does not parse gml:MultiCurve properly	rpieciorak	tschaub	"There is a problem when trying to read response from Deegree WFS 2.2.

GML fragment which will not parse currently: 
{{{
<gml:MultiCurve srsName=""EPSG:2175"">
    <gml:curveMembers>
        <gml:Curve>
            <gml:segments>
                <gml:LineStringSegment>
                    <gml:posList>
                      235669.48 878306.69 
                      ... 
                      235666.58 881038.3
                    </gml:posList>
                </gml:LineStringSegment>
            </gml:segments>
        </gml:Curve>
        ...                        
        <gml:Curve>
            <gml:segments>
                <gml:LineStringSegment>
                    <gml:posList>
                      235696.9 879864.26 
                      ... 
                      235812.73 879676.71
                    </gml:posList>
                </gml:LineStringSegment>
            </gml:segments>
        </gml:Curve>
    </gml:curveMembers>
</gml:MultiCurve>
}}}

GML will not parse because there are no reader for ""gml:curveMembers"" element.

After adding following:
{{{
   ...
   ""curveMember"": function(node, obj) {
      this.readChildNodes(node, obj);
   },
   ""curveMembers"": function(node, obj) {
      this.readChildNodes(node, obj);
   },
   ...
}}}
all will parse as expected."	bug	new	minor	2.13 Release	Format.GML	2.8				Needs Discussion