List of Supported Formats

Search the Online Transformer Gallery

 

INSPIRE GML Writer Parameters

INSPIRE Themes

ClosedSelect Feature Types
  • by Themes(default): The INSPIRE Themes parameter takes effect.
  • by XSD: A different INSPIRE schema (other than the built-in themes) may be specified via the Application Schema parameter.

begin snippet

ClosedSelect Feature Types
  • by Themes(default): Enables the INSPIRE Themes parameter.
  • by XSD: This option enables the Application Schema parameter, where you can specify a different INSPIRE schema (other than the built-in themes).

When reading schema features or importing feature type definitions into the INSPIRE writer, the INSPIRE reader dataset parameter may be left unset.

ClosedINSPIRE Themes

Browse a list of the available INSPIRE themes. (Note that INSPIRE themes are based on the v3.3 schemas.)

Note: An explicit path to a different INSPIRE schema with the definitions for the appropriate theme or layer can be specified in the Application Schema parameter.

ClosedApplication Schema

When the by XSD parameter is selected, this parameter specifies the location of the INSPIRE .xsd document.

end snippet

SRS Parameters

ClosedGML srsName

This parameter can overwrite the CRS value that is written in the GML instance’s srsName attributes.

By default, the FME coordinate system name in a feature is transferred directly onto the srsName attribute. Using this parameter allows you to provide your own URN CRS string for the srsName attributes.

ClosedGML SRS Axis Order

This parameter is required in conjunction with the GML srsName parameter. It specifies the axis order for a coordinate tuple in a GML <pos> or <posList> element.

The valid values are

  • 1,2
  • 2,1
  • 1,2,3
  • 2,1,3

There is no default value.

For example, if GML srsName is set to urn:ogc:def:crs:EPSG:6.6.4326, this parameter should be set to “2,1” so that the coordinates in the GML <pos> and <posList> elements are written in lat-lon order.

Pretty Printing

ClosedPretty Print

Setting this parameter to Yes ensures the output is neatly formatted. This promotes easier reading on screen and in print output.

  • Indent Size: Select a value from 0 to 9.
  • Replace Tabs with Spaces: By default the Tab character is used to for indentations. Select Yes to substitute the Tab character with a Space.

Note: Enabling this option produces a considerably larger output file due to added whitespace.

Feature Properties

ClosedMap Predefined Properties

Specifies whether the default and optional GML feature properties, name and description, should be read.

Feature Properties – Attribute Handling

ClosedMap Complex Properties as

Specifies whether GML properties that are defined as a complex type with complex content (that is, those that have embedded children elements) should be mapped as nested list attributes within FME features.

If the value is set to XML Fragments, then the complex properties with complex content are mapped as XML fragments.

Some complex properties, such as those that are recursively defined, cannot be mapped as nested lists. These complex properties will always be mapped as XML fragments, regardless of the setting for this parameter.

ClosedLimit Number of Lists in Nested Attributes

This optional parameter can control the depth of nested list attributes.

Advanced

ClosedMaximum Decimal Places

Specify the maximum number of decimal place to write to the GML file when writing coordinates.

To specify an exact number of decimal places to write, use this parameter in conjunction with the Minimum Decimal Places parameter.

Value

An integer greater than or equal to 0.

Default value: 15 decimal places.

ClosedMinimum Decimal Places

Specify the minimum number of decimal place write to the GML file when writing coordinates.

To specify an exact number of decimal places to write, use this parameter in conjunction with the Maximum Decimal Places parameter.

Value

An integer greater than or equal to 0.

Default value: 0 decimal places.

ClosedSystem Encoding

This parameter specifies the encoding for the incoming schema and data feature (for example, UTF-8).

If unspecified, the writer assumes that the schema and data features are encoded with the system’s encoding.

ClosedSuppress xsi:schemaLocationAttribute

This parameter suppresses the output of the xsi:schemaLocation attribute in the GML instance’s root element. The xsi:schemaLocation in an XML document instance is not a mandatory attribute – it is merely a hint that an XML processor may choose to ignore.

Setting this parameter to Yes suppresses the output of the xsi:schemaLocation attribute in the output GML instance. The default setting is No.

Feature Collection

ClosedFeature Collection

The target namespace of the root FeatureCollection element is influenced by this parameter.

  • gml – FeatureCollection root element for the output GML instance is the predefined <gml:FeatureCollection> element.
  • wfs– Changes the root element in the output document to <wfs:FeatureCollection>; in addition, appropriate XML namespace declarations and xsi:schemaLocation entries are added to include the WFS schemas.
    Note:The wfs choice is not currently supported when writing GML v3.2.1 data. This is because the WFS 1.1.0 FeatureCollection is defined for GML 3.1.1. Wrapping the data with a WFS FeatureCollection will be enabled for GML v3.2.1 writing when WFS 2.0 is supported.
  • target-namespace – Changes the root element to <[target-ns-prefix]:FeatureCollection>, where [target-ns-prefix] is the prefix that is bound to the output document target namespace, e.g., <fme:FeatureCollection>. The output xsd document will also include a custom FeatureCollection declaration and FeatureCollectionType definition.

Feature Collection when GML Version is Application Schema

This parameter can also be used to specify the local-name of the element that should be used as the feature collection only when the GML Version parameter is set to Application Schema. The specified feature collection must exist in the set of parsed schemas, otherwise FeatureCollection in the GML namespace will be assumed.

If the parameter is left empty and if the parent/child relationship for the features in the writer are assembled into several rooted trees, then FeatureCollection will be assumed as the wrapper collection; parent/child relationships are maintained with the gml_id and gml_parent_id attributes. Note that an XML document must have a single rooted element.

If the parameter has the local-name of the element and this element corresponds to a feature collection in the set parsed schemas, and:
  • if the specified collection is passed in as a feature, then the writer will use this feature as the feature collection of the dataset. The parent/child relationships should be set up so that this feature ends up as the single rooted element of the output. If the single rooted tree does not have the same element name as the specified feature collection, then the writer will automatically create the specified feature collection to serve as the root element of the GML output. Note that the writer will also force any features without a gml_parent_id to be children of the specified collection. This means that users may skip the extra step of assigning a gml_parent_id to all features belonging to that collection.
 OR
  • if the specified collection is NOT passed in as a feature, then the writer will automatically create the specified feature collection to serve as the root element of the GML output. Note that this may not be ideal, as the feature collection may have some required properties that the GML writer cannot automatically populate.
ClosedFeature Collection ID

GML v3.2.1 requires a gml:id on every feature and feature collection.

This parameter allows you to supply a custom gml:id value to replace UUID that is automatically assigned for the feature collection under GML v3.2.1.

ClosedFeature Collection NS URI

This parameter is applicable only when the GML Version parameter is set to Application Schema. It is used to specify the XML Namespace URI for the element name that is specified as the feature collection in the Feature Collection parameter.

For example, to specify that we want the WFS 2.0 "FeatureCollection" then we set this parameter to "http://www.opengis.net/wfs/2.0" and Feature Collection to the "FeatureCollection" (as specified above in Feature Collection when GML Version is Application Schema).