GML SF-0 Writer Parameters

The version of the GML schema document. If not specified, FME assumes a value of 1.0.0.

The file location for the output GML application document. If left blank, the .xsd file is created in the same folder and with the same file basename as the output dataset.

Allows you to 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. This parameter allows you to provide your own URN CRS string for the srsName attributes.

The axis order for a coordinate tuple in a GML <pos> or <posList> element. This parameter is required if GML srsName is specified.

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

The GML application schema target namespace prefix. If not specified, the default value is fme.

The GML application schema target namespace URI. If not specified, the default value is
http://www.safe.com/gml/fme.

Yes: Every GML writer DEF line is translated to the output GML application schema document as an XML Schema element declaration and a corresponding complex type definition.

No (Default): Directs the writer to ignore those DEF lines that have no corresponding feature instances.

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.

Instructs the writer to write out only the .xsd document, only the .gml document, or both documents.

If wfs, the root element in the output document changes to <wfs:FeatureCollection>. In addition, appropriate XML namespace declarations and xsi:schemaLocation entries are added to include the WFS schemas.

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.

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.

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.

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.

Specifies the encoding to use for the output XML documents, which include both the GML instance and the GML application schema.

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.

Sets the URL location of the GMLSF compliance levels schema. This URL is transferred to schemaLocation attribute in the <import> element for the “http://www.opengis.net/gmlsf” namespace in the generated GMLSF .xsd document. If not specified, the default value is http://schemas.opengis.net/gml/3.1.1/profiles/gmlsfProfile/1.0.0/gmlsfLevels.xsd.

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.

Using Web Connections

FME Options: Web Connections

Enter the username and password to access the database, user account, or wherever authentication is required.