SOSI GML Themes
Select Feature Types
- by Themes(default): Enables the SOSI GML Themes parameter.
- by XSD: This option enables the Application Schema parameter, where you can specify a different schema (other than the built-in themes).
SOSI GML Themes
Browse a list of the available SOSI GML themes. (Note that themes are based on the v4.6 schemas.)
Note: An explicit path to a different SOSI GML schema with the definitions for the appropriate theme or layer can be specified in the Application Schema parameter.
SRS Parameters
GML 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.
GML 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
Pretty Print
Setting this parameter to Yes ensures the output is neatly formatted. This promotes easier reading on screen and in print output. Note, however, that it also produces a considerably larger output file size due to the added whitespace.
- 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.
Feature Collection
Feature Collection
The root collection element is influenced by this parameter.
- FeatureCollection – In GML 3.1.1 mode, the default collection element is <gml:FeatureCollection>; the Feature Collection NS URI parameter may be used in conjunction with this parameter to change the collection element to <wfs:FeatureCollection>.
Note: <wfs:FeatureCollection> is not supported when writing in GML v3.2.1 mode.
- 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: |
||
|
OR |
|
Feature 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.
Feature Collection NS URI
This parameter is applicable only when the GML Version parameter is set to Application Schema or 3.1.1. 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 the WFS 2.0 "FeatureCollection", 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).
Feature Properties
Map Predefined Properties
Specifies whether the default and optional GML feature properties, name and description, should be read.
Feature Properties – Attribute Handling
Map 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.
Limit Number of Lists in Nested Attributes
This optional parameter can control the depth of nested list attributes.
Advanced
Maximum 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.
Minimum 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.
System 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.
Suppress 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.
Override XSD and Use Namespace Declarations
This parameter allows elements in different namespaces, other than the GML and the document target namespace, to be included in the output file.
The valid values for this parameter are whitespace-separated XML namespace declarations, as they would appear in an XML element.
A schema file is not written when this directive is used, that is, the output XSD file is suppressed.
To control the namespace of a particular element, the FME feature type and/or attribute name must carry the corresponding namespace prefixes declared by this parameter. The prefix must be separated by an underscore.
For example, in order to write out a <hy-p:Watercourse> feature type element, the FME feature type and hence the FME feature type definition – the DEF line – must be prefixed with hy-p_. For example:
GML_DEF hy-p_Watercourse
The value will need to include the XML namespace declaration for the hy-p prefix. For example:
xmlns:hy-p=”urn:x-inspire:specification:gmlas:HydroPhysicalWaters:3.0”
Values
One or more whitespace-separated XML namespace declarations of the form xmlns:PREFIX=”URI”, where PREFIX is the namespace prefix and URI is the namespace URI. For example:
xmlns:gml=”http://www.opengis.net/gml/3.2”
Validate Output File
This optional parameter performs validation of the output file against the schemas referenced in that file:
Yes:
- If Select Feature Types is set to by Themes, the INSPIRE Themes are used for validation.
- If Select Feature Types is set to by XSD, the specified Application Schema is used for validation.
No (default):
- Validation is not performed.
Target xsi:schemaLocation URL
By default, the URL for the target namespace URI–URL location pair in the instance document’s xsi:schemaLocation attribute is the application schema’s relative filename. This parameter allows you to overwrite the .xsd filename by supplying a custom URL.
The parameter affects only the value of the URL for the target namespace in the xsi:schemaLocation. It does not affect where the application schema will be written. The parameter should have exactly one URL value indicating the XSD location for the target namespace URI. For example:
http://www.conurl/ns.xsd
To add multiple values, they must be whitespace-separated URI–URL pairs. This option allows you to provide a complete custom xsi:schemaLocation for the output document.
Output Encoding
Specifies the encoding to use for the output XML documents, which include both the GML instance and the GML application schema.
Use Network Authentication
This parameter is always visible in some formats, and visible in other formats only when the dataset is a URL.
Authentication Method
Specify the authentication method to use when accessing a password-protected server.
- Basic: (default) Basic access authentication is designed to allow a client to provide credentials to a server on the assumption that the connection between them is trusted and secure. Note that any credentials passed from client to server can be easily intercepted through an insecure connection.
- Digest: Digest authentication is one of the agreed-upon methods a web server can use to negotiate credentials, such as username or password, with a user's web browser.
- NTLM: A challenge-response protocol that is used to provide compatibility with versions of Windows earlier than the Windows 2000 operating systems.
- Web Connection: Web connections provide a convenient and secure way to store and reuse previously established connection parameters. See Web Connection below.
- Single Sign-on: FME will use the credentials of the current user to authenticate the HTTP request. This authentication method currently works only on the Windows operating system.
Note: To access datasets using a proxy server, use the Network tools in FME Options. From the Workbench menu, select Tools > FME Options > Network. For more information, see "Network Proxy" in the FME Workbench Help.