hale studio supports publishing your transformed GML data to a WFS with
support for transactions. Currently supported are Transactional Web
Feature Services following the OGC WFS 1.1.0 or WFS 2.0.0
specifications. There are two different providers for publishing to
- The direct upload will do a single request
that starts as soon as the first transformed features are available.
Use this option if you are sure the WFS can cope with the amount of
data in a single transaction.
- The partitioned upload partitions the
transformed data before upload to be able to do multiple requests to
the WFS-T for large data sets. The partitioning is done based on the
references between features. Features that are connected are kept
together so the WFS-T is able to retain those references.
The publishing to WFS in this version of hale studio is
deemed experimental. This means it does not have the full
functionality we want to provide for a WFS publishing feature.
However, within its limits it is functional and may be useful to you.
The publishing to WFS currently has the following known limitations:
- Non-fatal errors during the transformation or the GML
encoding are ignored, the features published thus may be incomplete
or missing specific information - please note the corresponding
messages in the transformation and export reports. There is no
automatic recovery, features may have to be deleted manually if they
are not desired to be published.
hale studio behaves like this because both transformation and GML
export aim to provide you a result even if there are small errors or
- hale studio will not check the WFS Capabilities if the WFS
supports any of the provided GML feature types.
Target location for the WFS-T export is the POST URL for the
WFS Transaction operation. The hale studio user interface provides a helper to
determine that URL from the WFS capabilities.