1. Home
  2. Working with data
  3. How to import features from a WFS server

How to import features from a WFS server

A Web Feature Service (WFS) server can provide access to “layers” for download, where a layer is a designated collection of features. Using Cadence , you can easily pick from the layers within a given WFS server and import the features into a file for use in your project.

Before you get started, you will need the web address (a.k.a. URL) of your WFS server. This will look something like https://my-geoserver.com/geoserver/wfs.

If your features are stored in a namespace in WFS, then your URL should also include the namespace. For example, the planning-maps namespace would be accessed by a URL that ends in /geoserver/planning-maps/wfs.

  1. To connect to your WFS server in Cadence, go to the Files tab. Then select Import source > WFS features.
  2. In the form provided, enter the WFS server url and click Connect. If connection is successful, you will see a tick alongside the server URL. See Common issues below if the attempt to connect fails.
  3. If your WFS server contains layers, they will now be listed in the Layer to import dropdown. Select the layer you would like to import.
  4. The form will automatically generate a name based on the chosen layer, but if you wish to change it, you can do so with the File name field
  5. When ready, click Import
  6. The features can then be added to your map in the same way as other files, via Add overlay

This will only import features that intersect your project bounds.

Common issues

Failed to get WFS layers: Request failed with status code 404

This error indicates that the given URL points to a resource which doesn’t exist. You can confirm the existence of the underlying server by removing the /wfs off the end of the URL. For example, https://my-geoserver.com/geoserver/wfs will have a web interface that can be reached at https://my-geoserver.com/geoserver. Double-check the URL you’re using is valid.

Failed to get WFS data: Request failed with status code 400

This error can be caused by the WFS server not supporting the GeoJSON output format, which is required for importing a GeoJSON file into Cadence.

In order to allow Cadence to communicate with a server that gives this error, you will need to contact the server administrator to see if the WFS server can be configured to export features with the application/json file type.

Failed to get WFS layers: Network Error

This error typically arises from a security measure on the given WFS server called Cross-Origin Resource Sharing (CORS). It means that other websites cannot connect to the server. If you can successfully visit the server URL directly, but cannot connect to it in Cadence, this is usually the case.

In order to allow Cadence to communicate with a server that gives this error, you will need to contact the server administrator.

Updated on 23rd March 2026

Was this article helpful?

Need Support?
Can't find the answer you're looking for?
Contact support