GMLAS driver: not correct geometry fields about gdal HOT 4 OPEN

I'm not sure the GMLAS driver is ready for such a untypical advanced use case. Furthermore the write side of the GMLAS driver is quite couple with its read side. Cf https://gdal.org/drivers/vector/gmlas.html#creation-support
Here would would need to force the input dataset to be read by the GMLAS driver as well with GMLAS:test-file.gml, and hencure that your input file fully validates. But even with that, the subtlety of the xs:choice on geometry, might easily confuse the driver.

from gdal.

I'm not sure the GMLAS driver is ready for such a untypical advanced use case. Furthermore the write side of the GMLAS driver is quite couple with its read side. Cf https://gdal.org/drivers/vector/gmlas.html#creation-support Here would would need to force the input dataset to be read by the GMLAS driver as well with GMLAS:test-file.gml, and hencure that your input file fully validates. But even with that, the subtlety of the xs:choice on geometry, might easily confuse the driver.

Should have deleted choice not to confuse, it is just like in real schema, where i faced this problem)
In this issue i'm talking about double tags when in xsd geometry field looks like this "<xs:element ref="gml:MultiSurface"/>
"

In this case "gml:MultiSurface" is recognized by GMLAS like geometry field name and we got "gml:MultiSurface<gml:MultiSurface" regardless of the input file format

from gdal.

Should have deleted choice not to confuse, it is just like in real schema, where i faced this problem)

Please update precisely the initial post with a valid schema and sample. Details matter a lot in that area (but the GMLAS driver is very tricky and it is likely that a fix to address your use case would go beyond usual maintenance activities)

from gdal.

Should have deleted choice not to confuse, it is just like in real schema, where i faced this problem)

Please update precisely the initial post with a valid schema and sample. Details matter a lot in that area (but the GMLAS driver is very tricky and it is likely that a fix to address your use case would go beyond usual maintenance activities)

Okay, Thank you!
Updated the post.

from gdal.