This is a reference documentation of the GML (WFS 2.0 FeatureCollection) writer in hale studio. Usually you will not need this reference, as in hale studio the configuration of I/O providers is done via the respective wizards for import and export. Where this reference can come in handy is if you want launch a transformation via the command line.
Name | GML (WFS 2.0 FeatureCollection) |
---|---|
Identifier | eu.esdihumboldt.hale.io.wfs.fc.write-2.0 |
Implementation | eu.esdihumboldt.hale.io.wfs.file.WFS2FCWriter |
Following are the specific configuration parameters for this writer.
Prefix to use for all CRS codes based on EPSG in geometry srsNames.
Setting name | crs.epsg.prefix |
---|---|
Example value | http://www.opengis.net/def/crs/EPSG/0/ |
Make sure that all SRS names use this kind of notation. The EPSG code number is appended to the provided parameter to build the SRS name. | |
By default the CRS code is not modified. |
Target coordinate reference system the data should be transformed to.
Setting name | crs |
---|---|
Example value | code:EPSG:4326 |
Reference systems can be defined either as code or WKT (preceded with code: or wkt: respectively) | |
By default no CRS transformation is performed, the existing geometries are written with their respective CRS. |
Unifiying the winding order of geometries, before writing them
Setting name | geometry.unifyWindingOrder |
---|---|
Example value | clockwise, noChanges |
Unifying order can be set as Clockwise or no changes in order (clockwise or noChanges respectively). | |
Default value | counterClockwise |
By default, counterClockwise is set for GML instance |
If geometries should be simplified (e.g. a MultiPolygon to a Polygon), if possible, before writing them.
Setting name | gml.geometry.simplify |
---|---|
Default value | true |
If the output should be pretty printed (indented)
Setting name | xml.pretty |
---|---|
Default value | false |
States if a data set feed for an INSPIRE ATOM based Download Service should be created.
Setting name | inspire.sds.create_feed |
---|---|
Default value | false |
Title of the generated ATOM data set feed, if created.
Setting name | inspire.feed.title |
---|
Subtitle of the generated ATOM data set feed, if created.
Setting name | inspire.feed.subtitle |
---|
Rights information for the generated ATOM data set feed, if created.
Setting name | inspire.feed.rights |
---|
Author name for the generated ATOM data set feed, if created.
Setting name | inspire.feed.author_name |
---|
Author email address for the generated ATOM data set feed, if created.
Setting name | inspire.feed.author_mail |
---|
URL the generated ATOM data set feed will be available on.
Setting name | inspire.feed.selflink |
---|
URL the GML file will be available on as part of the generated ATOM data set feed.
Setting name | inspire.feed.gmllink |
---|
Don't encode nilReason attributes for elements that are not nil.
Setting name | xml.notNil.omitNilReason |
---|---|
Example value | false |
Default value | true |
By default, nilReason attributes are omitted for elements that are not nil. |
Automatically add codespace to gml:identifier during GML export.
Setting name | xml.add.codespace |
---|---|
Example value | false |
Default value | true |
By default, the codespace is automatically added to the gml:identifier. |
Skip counting features to allow direct streaming
Setting name | skipFeatureCount |
---|---|
Default value | false |
Guiding value for instances per file. The number will be exceeded only in cases where there are too many inter-related instances that cannot be separated.
Setting name | instancesPerFile |
---|---|
Example value | 1000 |
Default value | 0 |
By default, no partitioning will take place and all instances will be written to a single file. |
Mode for partitioning the output
Setting name | partition.mode |
---|---|
Example value | cut |
The partitioning can also be done by cutting strictly at the threshold. | |
Default value | related |
By default objects that are connected via local XML references are kept together. |
The following configuration parameters are shared for all I/O providers.
During import the content type is tried to be auto-detected, for export this is not possible, but I/O providers may have a default content type associated. If an I/O provider only supports one content type, it's usually not necessary to set this parameter. In any case you can override the content type to use/assume using a content type identifier (see the list of supported content types at the bottom of the page).
Setting name | contentType |
---|---|
Example value | eu.esdihumboldt.hale.io.gml |
Specifying a character encoding is important especially for the
import, so data is interpreted correctly. Not every I/O provider
may respect this setting though (e.g. if the encoding is given by
the data source).
Specify a character encoding by its name
as recognised by Java.
Setting name | charset |
---|---|
Example value | UTF-8 |
eu.esdihumboldt.hale.io.gml
)eu.esdihumboldt.hale.io.gml.gzip
)