Closed ronaldtse closed 2 months ago
@HassanAkbar :
Actually, I updated this in the mapper. Let me share the commit with you.
@HassanAkbar this is causing failure here:
https://github.com/lutaml/ogc-gml/issues/1
<gml:GeodesicString>
<gml:posList>55.233333333333334 -36.166666666666664
55.23116372807667 -36.89437337916484</gml:posList>
</gml:GeodesicString>
- <gml:ArcByCenterPoint numArc="1">
- <gml:posList>55.233333333333334 -36.166666666666664</gml:posList>
- <gml:radius uom="NM">25.0</gml:radius>
- <gml:startAngle uom="deg">270.0
- </gml:startAngle>
- <gml:endAngle uom="deg">497.0</gml:endAngle>
- </gml:ArcByCenterPoint>
<gml:GeodesicString>
<gml:posList>54.92816350530716 -35.674116070018954
55.233333333333334 -36.166666666666664</gml:posList>
</gml:GeodesicString>
+ <gml:ArcByCenterPoint numArc="1">
+ <gml:posList>55.233333333333334 -36.166666666666664</gml:posList>
+ <gml:radius>#<Ogc::Gml::Measure:0x00000001094ddaa0></gml:radius>
+ <gml:startAngle>#<Ogc::Gml::Measure:0x00000001094dd280></gml:startAngle>
+ <gml:endAngle>#<Ogc::Gml::Measure:0x00000001094dca88></gml:endAngle>
+ </gml:ArcByCenterPoint>
</gml:segments>
@ronaldtse I've looked at the code at https://github.com/lutaml/ogc-gml/issues/1 and It is using the shale mapper and not the one that we have extended, I'll move the mapper to the shale fork and I think using that can fix the issue.
It does not support interleaved element orderings. It only supports fixed ordering, e.g. according to the declared element order.
Given:
Shale will return:
Because 'a' element is mapped before 'b'.
This ordering is very important in some schemas because it is positional.