What is most relevant when setting up a WFS is the spatial filter, defined by xmin, xmax, ymin and ymax, as well as the object filtering otypes.

The former defines the geographical area within which the WFS will make data available. x in this case is E and y is N.

The object filter otypes determines which object types are to be made available. The filter can consist of only one object type or a series of comma-separated object types.

 

What is most often relevant when setting up a WFS is the spatial It is also possible to specify which components you want to make available via your WFS in addition to specifying object types.

The component filters are written in the form object type; subtype; component type, where the tuples are separated by commas. These filters can specify which components should or should not be made available via WFS.

 

A WFS is created as a separate file, usually under ... app / <utility> / <customer> / web.

The file name should be capitalized and be in the form WFS_EXAMPLE.conf.

The path to the WFS can then look like this: bios / wfs / app / <utility> / <customer> / web / WFS_EXAMPLE