[gdal-dev] GML driver - gml:xlink resolving - just embedding?

[Johannes Echterhoff]

Hello,

Does resolving of xlink:href by the GML driver (when GML_SKIP_RESOLVE_ELEMS is used, i.e., set to NONE or HUGE) simply mean that the referenced resource is copied into the XML element that contains the xlink:href XML attribute? Tests seem to support this, but I'd really like to double-check on this list.

My somewhat naive assumption was that if the reference pointed to another GML object, then that would be recognized somehow (though the exact "how" is probably the issue; document-internal reference via @gml:id could work, but not an external reference), and duplication of objects avoided. The resolving also seems to remove the xlink:href attributes for resolved references, and the gml:id attributes on the elements that are copied into the main GML file. That, in fact, creates duplicate objects in my test case.

Best regards,
Johannes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20221115/888629cf/attachment-0001.htm>