With XtraProxy for WFS you can access OGC Web Feature Services from your usual web, desktop and mobile GIS clients as long as they support the GeoServices REST API.

GIS clients often focus on simple models and displaying features in maps. As a result, support for OGC Web Feature Services (OGC WFS) is often lacking. This is in particular an issue with OGC Web Feature Services which provide data using complex application schemas. XtraProxy for WFS provides seamless access to the data from such services.

Setting up proxy services for OGC Web Feature Services is simple with XtraProxy for WFS. Using the XtraProxy Service Manager you register a new WFS simply by providing its URL. XtraProxy for WFS then analyses the service and automatically configures a new proxy service by inspecting the capabilities document, the schemas of the feature types provided by the service as well as sample feature data returned by the WFS.

The Service Manager can then be used to update the configuration of the proxy services as well as to manage and remove the services. Configuration options include:
  • the title and description of the service
  • the maximum number of features that a query may return
  • for each feature type
    • the scale range
    • the extent
    • the default symbolization in a map
    • the list of feature attributes to be included in output of the proxy service

In addition, a flag can be used to specify whether the WFS honours the axis order definition of the coordinate reference system or always uses long/lat and easting/northing as the axis order.

For well-known feature types, e.g. selected INSPIRE feature types, XtraProxy for WFS includes default configurations that are used whenever a new proxy service is added based on a WFS with these feature types. Administrators can customize these default configurations and add new ones for additional feature types based on their needs.

If the map.apps option of XtraProxy for WFS is used, a map.apps application is created for each proxy service as part of the Service Manager to display and inspect the feature data provided by the service.

The use of modern http streaming results in performance close to the performance of the WFS for queries returning a normal number of features.

XtraProxy for WFS supports a wide range of WFS services and understands all commonly used versions of WFS (1.0, 1.1, 2.0) and GML (2.1, 3.1, 3.2).

Complex data structures in the feature data of the WFS are automatically flattened for the transport over the GeoServices REST API, but are preserved in the HTML popups.

Our presence in ArcGIS Online at https://ii.maps.arcgis.com/ includes sample web maps using XtraProxy for WFS services.

System requirements

XtraProxy for WFS requires Java Runtime Environment 1.8 and supports recent Enterprise Linux distributions like Debian, SLES, RHEL and Ubuntu. In addition to it Windows is also supported.

XtraProxy for WFS runs on both physical and virtual machines on the ESX platform (VMware vSphere or ESXi). The exact hardware requirements depend on a variety of factors. Typically, 4GB or 8GB of RAM and 1GB of storage are sufficient.