featuns URI: http://www.opengis.net/gml/3.2

在我的例子中，我使用地理名称。xsd应用程序模式没有任何额外的featumemory属性，因此我启用了映射预定义属性到Yes，这样我就可以将gml_description字段的值添加到featumemory对象中。注意，每个NamedPlace特性如何将它们的gml_parent_id设置为AT.HR.IT。问题2:如何在输出中压制空元素

>目前，GML写入器还没有压制空输出的设置。 FME does support nillable, so if an attribute is nillable then FME will set xsi:nil=true for null values.

To suppress null writing <gml:name/> in this case, there are 2 possible workarounds. You can use the GMLFeatureComposer to generate the GML, then pass it through the XMLFormatter and set it to 'remove empty elements to Yes. You would then need to use the TextFileWriter to write out your GML.

My preferred approach is to stick with the GML writer, and use a NullAttributeMapper to detect null attributes and map them to 'missing'. This effectively removes the field from the FME feature schema. In the attached example I use the NullAttributeMapper to scan all attributes and map any empty or null attributes to missing. This picks up the gml_name{2} list element and effectively removes it from the list.

Question 3: How to set the default namespace to remove namespace prefix from the element names

In your case, you have <eczr:FeatureMember> and you want this to show up as just <FeatureMember >. To do that you need to make eczr the default namespace.

In my case I have <gn:NamedPlace>. If I want to remove the gn namespace prefix, I need to make the namespace associated with gn the default namespace. Looking at the namespace header of my output I see that:

xmlns:gn="urn:x-inspire:specification:gmlas:GeographicalNames:3.0"

So to remove this namespace we need to set:

Override XSD and Use Namespace Declarations to:

xmlns="urn:x-inspire:specification:gmlas:GeographicalNames:3.0"

Thereafter, the output will have <NamedPlace> not <gn:NamedPlace>

Hopefully this gives you a few things to try. Because you can't share your application schema, I thought it might be useful to have a basic example of GML writing to play with. The above example is based on the INSPIRE GeoNames article. Feel free to edit this workspace for testing purposes and send back your modified version if you run into trouble, or manage to reproduce a problem with it.

If you have questions specific to your data feel free to follow up via the support system.

Dean