WFS API

Opendatasoft records can be accessed through a Web Feature Service (WFS), which provides an interface allowing requests for geographical datasets.

The WFS API provides an interface that enables requests for geographical features from the Opendatasoft records.

This documentation is designed to guide you through the usage of the WFS API in version 2.0.0 with simple conformance class. It includes information on the supported operations, examples of typical use cases, common errors, and additional resources.

If you have any questions or encounter any issues while using the WFS API, refer to the troubleshooting section or contact our support team for assistance.

Let's get started with using the WFS API in version v2.0.0. (v1.1.0 is deprecated)

Operations supported

Opendatasoft platform implements only by HTTP GET method the 5 following operations defined by the WFS standard with simple conformance class : GetCapabilities, DescribeFeatureType, ListStoredQueries, DescribeStoredQueries, GetFeature operation with only the StoredQuery action. One stored query, that fetches a feature using its id, is available.

Operation	Description
`GetCapabilities`	Retrieves metadata about the WFS service
`DescribeFeatureType`	Generates a schema description of features types
`GetFeature`	Retrieves features from the service and output them using the GML representation
`ListStoredQueries`	Lists the stored queries that are available
`DescribeStoredQueries`	Generates a description of the named stored queries that are available

Service address and methods

Service entry address

GET https://documentation-resources.opendatasoft.com/api/wfs HTTP/1.1

The service can be reached at the following entry address.

The workspace https://documentation-resources.opendatasoft.com/ is used as an example in this documentation, but you should replace it with your custom workspace name.

The WFS supports only GET HTTP methods in v2.0.0 (POST HTTP method is supported in v1.1.0 with only text/xml as Content-Type header, but this version is deprecated)

Common parameters

When the HTTP GET method is used, the parameters are appended to the URL using a Keyword Value Pair (KVP) encoding.

Here is the list of the common parameters, supported by all WFS operations:

Operation	Description	Possible values	Optionality and use
`service`	The requested service	`WFS`	One (Mandatory)
`request`	The requested operation	`GetCapabilities`, `DescribeFeatureType`, `GetFeature`, `ListStoredQueries`, `DescribeStoredQueries`	One (Mandatory)
`version`	The requested version of the service	`2.0.0`	One (Mandatory except GetCapabilities)

Notice that all usable parameters in this API are case-insensitive.

Common usages

Viewing and analyzing geographic data: QGIS or ArcGIS can be used to connect to a WFS service and visualize the retrieved data on a map. This allows users to explore and analyze the data in a familiar GIS environment.
Filtering data based on attributes or location: Users can also use the WFS API to filter data based on attributes or location. For example, users may want to filter out features that are not relevant to their analysis or only include features near from a point of interest.

Overall, the WFS API provides a flexible and powerful tool for accessing and analyzing geographic data by other software, enabling users to perform a wide range of tasks related to spatial analysis, visualization, and mapping.

Examples

GetCapabilities

Basic example GetCapabilities

GET https://documentation-resources.opendatasoft.com/api/wfs?service=WFS&request=GetCapabilities HTTP/1.1

Example 1 : To retrieve the service metadata. This will return an XML document that describes the capabilities of the WFS service, including supported operations, data types, and service metadata.

Parameterized example GetCapabilities

GET https://documentation-resources.opendatasoft.com/api/wfs?SERVICE=WFS&REQUEST=GetCapabilities&SECTIONS=ServiceProvider HTTP/1.1

Example 2 : To retrieve the service provider metadata, you can use the following URL.

DescribeFeatureType

Basic example DescribeFeatureType

GET https://documentation-resources.opendatasoft.com/api/wfs?SERVICE=WFS&REQUEST=DescribeFeatureType&VERSION=2.0.0 HTTP/1.1

Example 1 : To retrieve schema description of features types serviced by the service. This will return an XSD document that describes the features types.

Parameterized example DescribeFeatureType

GET https://documentation-resources.opendatasoft.com/api/wfs?SERVICE=WFS&REQUEST=DescribeFeatureType&VERSION=2.0.0&TYPENAMES=arrondissements-paris HTTP/1.1

Example 2 : To retrieve schema description of a feature type. This will return the XSD document that describes an Opendatasoft dataset.

GetFeature

Basic example GetFeature

GET https://documentation-resources.opendatasoft.com/api/wfs?SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=arrondissements-paris HTTP/1.1

Example 1 : To retrieve features from the arrondissements-paris dataset.

Parameterized example GetFeature

GET https://documentation-resources.opendatasoft.com/api/wfs?SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=arrondissements-paris&BBOX=(48.811090519909115,2.34832763671875,48.90686235347725,2.4300384521484375) HTTP/1.1

Example 2 : To retrieve features from the arrondissements-paris dataset within a bounding box.

ListStoredQueries

Basic example ListStoredQueries

GET https://documentation-resources.opendatasoft.com/api/wfs?SERVICE=WFS&REQUEST=ListStoredQueries&VERSION=2.0.0 HTTP/1.1

Example : To retrieve stored queries from the workspace.

DescribeStoredQueries

Basic example DescribeStoredQueries

GET https://documentation-resources.opendatasoft.com/api/wfs?SERVICE=WFS&REQUEST=DescribeStoredQueries&VERSION=2.0.0 HTTP/1.1

Example : To retrieve stored queries structure from the workspace (it gives details about input parameters and responses of stored queries).

Exception reports

Exception example

<?xml version="1.0" encoding="UTF-8"?>
<ExceptionReport xmlns="http://www.opengis.net/ows" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd" version="2.0.0" language="en">
  <Exception exceptionCode="InvalidParameterValue" locator="service">
    <ExceptionText>Service must be WFS or CSW.</ExceptionText>
  </Exception>
</ExceptionReport>

When an error occurs, the service responds to the client using an Exception Report message to describe the error.

Name	Definition	Data type and value	Multiplicity and use
`ExceptionText`	Text describing specific exception represented by the exceptionCode	Character String type, not empty. Value is an exception description as defined by individual servers	Zero or more (optional). Omitted only when no more useful information available
`exceptionCode`	Code representing type of this exception	Character String type, not empty. Allowed values are specified by each implementation specification and server implementation	One (mandatory)
`locator`	Indicator of location in the client's operation request where this exception was encountered	Character String type, not empty Contents defined for each allowed exceptionCode value for each operation	Zero or one (optional). Omitted when no useful value available

Authentication

An authenticated user can be granted access to restricted datasets and benefit from extended quotas for API calls. The API features an authentication mechanism for users to be granted their specific authorizations.

For the platform to authenticate a user, you need to either:

be logged in a portal so a session cookie authenticating your user is passed along your API calls, or
provide an API key via the Authorization header or as a query parameter.

Finding and generating API keys

API keys are managed via your user profile page at https://<youropendatasoftportal>.com/account/ or by clicking on your name in the header.

Link to account settings

Go to the tab named My API keys to see your existing API keys, revoke them and create new ones.

Account's API keys page

Providing API keys within requests

Unauthenticated request on a private portal

> GET https://private-portal.opendatasoft.com/api/v2/catalog/datasets/ HTTP/1.1

< HTTP/1.0 401 Unauthorized

Authenticated request using an Authorization: Apikey <API_KEY> header

> GET https://private-portal.opendatasoft.com/api/v2/catalog/datasets/ HTTP/1.1
Authorization: Apikey 7511e8cc6d6dbe65f9bc8dae19e08c08a2cab96ef45a86112d303eee

< HTTP/1.0 200 OK

{
    "total_count": 4,
    "links": [{
        "href": "https://private-portal.opendatasoft.com/api/v2/catalog/datasets?include_app_metas=False&limit=10&offset=0",
        "rel": "self"
    }, {
        "href": "https://private-portal.opendatasoft.com/api/v2/catalog/datasets?include_app_metas=False&limit=10&offset=0",
        "rel": "first"
    }, {
        "href": "https://private-portal.opendatasoft.com/api/v2/catalog/datasets?include_app_metas=False&limit=10&offset=0",
        "rel": "last"
    }],
    "datasets": [...]
}

Authenticated request using an API key as a query parameter

> GET https://private-portal.opendatasoft.com/api/v2/catalog/datasets/?apikey=7511e8cc6d6dbe65f9bc8dae19e08c08a2cab96ef45a86112d303eee HTTP/1.1

< HTTP/1.0 200 OK

{
    "total_count": 4,
    "links": [{
        "href": "https://private-portal.opendatasoft.com/api/v2/catalog/datasets?include_app_metas=False&limit=10&offset=0",
        "rel": "self"
    }, {
        "href": "https://private-portal.opendatasoft.com/api/v2/catalog/datasets?include_app_metas=False&limit=10&offset=0",
        "rel": "first"
    }, {
        "href": "https://private-portal.opendatasoft.com/api/v2/catalog/datasets?include_app_metas=False&limit=10&offset=0",
        "rel": "last"
    }],
    "datasets": [...]
}

If you try to access a private portal's catalog without being authenticated, the API returns a 401 Unauthorized error.

After generating an API key, you can use it to make authenticated requests. Depending on the permissions granted to the user for which the API key has been created, the JSON response contains only data about the datasets this user can access on the portal.

It is good practice to pass the API key to the Authorization header in the following format:

Authorization: Apikey <API_KEY>

Alternatively, you can pass the API key as a query parameter in the following format:

apikey=<API_KEY>

Replace <API_KEY>with your API key.

Using OAuth2 authorization

Overview

Opendatasoft implements the OAuth2 authorization flow, allowing third party application makers to access the data hosted on an Opendatasoft platform on behalf of a user while never having to deal with a password, thus avoiding any user credential to be compromised.

The Opendatasoft OAuth2 authorization flow is compliant with RFC 6749 and makes use of Bearer Tokens in compliance with RFC 6750.

Application developers who want to use the Opendatasoft APIs with OAuth2 must go through the following steps, which will be explained in this section.

Register their application with the Opendatasoft platform.
Request approval from users via an OAuth2 authorization grant.
Request a bearer token that will allows them to query the Opendatasoft platform APIs for a limited amount of time.
Refresh the Bearer Token when it expires.

Currently, applications are registered on a specific domain and can only access data on this domain.

Register an application for OAuth2 authentication

OAuth2 applications management interface

Go to the My applications tab of your account page on the domain you want to register the application on.
Fill the registration form with the following information:
- Application name: the name of the application
- Type:
  - confidential: client password is kept secret from the user and only used from a trusted environment (e.g: a web service, where the client password is stored server-side and never sent to the user)
  - public: client password is embedded in a client-side application, making it potentially available to the world (e.g: a mobile or desktop application)
- Redirection URL: the URL users will be redirected to after they have granted you permission to access their data
Store the resulting client ID and client secret that will be needed to perform the next steps.

Getting an authorization grant

Example call to /oauth2/authorize/

GET /oauth2/authorize/?
    client_id=123456789&
    redirect_uri=https://example.com&
    response_type=code&
    state=ilovedata&
    scope=all HTTP/1.1

To get an authorization grant from a user:

Redirect them to /oauth2/authorize/ with the appropriate query parameters.
The user will then be authenticated in the platform and redirected to a page identifying your application.
From there, the user will review the information you filled in the form described above and the scope of the requested access, and grant your application the right to access their data.
Once the user has accepted those terms, they will be redirected to your application's redirection URL with query parameters describing your authorization grant.

The query parameters you need to supply when redirecting the user are the following:

client_id: the client ID you were given during registration
redirect_uri: the redirect URI you provided during registration
response_type: this should always be set to code
scopes (optional): a list of space-separated requested scopes. Currently only all is supported
state (optional): a random string of your choice

Redirection following a successful authorization

HTTP/1.0 302 FOUND
Location: https://example.com?state=ilovedata&code=gKnAQc2yIfdz2mY25xxgpTY2uyG5Sv

The authorization grant redirect will have these values:

code: a 30-characters-long authorization code
state: the state passed in the request described above

The 30-character authorization code must now be converted into a bearer token within 1 hour before expiring.

Converting an authorization grant to a bearer token

Example call to /oauth2/token/

POST /oauth2/token/ HTTP/1.1

client_id=cid&
    client_secret=csc&
    grant_type=authorization_code&
    code=GokshWxRFXmW0MaLHkDv5HrG6wieGs&
    scopes=all&
    redirect_uri=https://example.com&
    state=ilovedata

To receive a bearer token, convert the previously obtained authorization grant via a POST request to /oauth2/token/ with the following parameters:

client_id: the client ID you were given during registration
client_secret: the client secret you were given during registration
redirect_uri: the redirect URI you provided during registration
grant_type: this should always be set to authorization_code
code: the 30-character authorization code received as an authorization grant
scopes (optional): a list of space-separated requested scopes. Currently only all is supported
state (optional): a random string of your choice

Alternative call with an Authorization header

POST /oauth2/token/ HTTP/1.1
Authorization: Basic Y2lkOmNzYw==

grant_type=authorization_code&
    code=GokshWxRFXmW0MaLHkDv5HrG6wieGs&
    scopes=all&
    redirect_uri=https://example.com&state=ilovedata

Alternatively, you can pass your client ID and client secret through the Authorization header

Example response for a bearer token request

HTTP/1.0 200 OK
Content-Type: application/json

{
    "access_token": "9kxoTUYvSxnAiMpv008NBqRiqk5xWt",
    "expires_in": 3600,
    "token_type": "Bearer",
    "state": "ilovedata",
    "scope": "all",
    "refresh_token": "jFfDUcsK9zzNMs1zwczzJxGrimPtmf"
}

The response to this request is a JSON representation of a bearer token, which contains the following values:

access_token: the token you can use to access the user's data.
expires_in: the number of seconds before token expiration
token_type: the type of the token. It will always be Bearer
state: the state passed in the request described above
scope: the list of scopes of this authorization code
refresh_token: a refresh token that can be used to renew this bearer token when expired

Using the bearer token

Using the token as a query parameter

GET /api/end/point?access_token=9kxoTUYvSxnAiMpv008NBqRiqk5xWt HTTP/1.1

Using the token in an Authorization header

GET /api/end/point HTTP/1.1
Authorization: Bearer 9kxoTUYvSxnAiMpv008NBqRiqk5xWt

Using the token in the request body

GET /api/end/point HTTP/1.1

access_token=9kxoTUYvSxnAiMpv008NBqRiqk5xWt

The bearer token can be passed along requests for authentication in three different ways:

as a query parameter of the request
in the request's Authorization header
in the request body

Refreshing a bearer token

Example token refresh call

POST /oauth2/token/ HTTP/1.1

client_id=cid&
    client_secret=csc&
    grant_type=refresh_token&
    refresh_token=jFfDUcsK9zzNMs1zwczzJxGrimPtmf&
    scopes=all&
    redirect_uri=https://example.com&
    state=ilovedata

To refresh an expired bearer token, send a request to the /oauth2/token/ endpoint, with the following query parameters:

client_id: the client ID you were given during registration
client_secret: the client secret you were given during registration
refresh_token: the refresh token returned in the bearer token response
grant_type: this should always be set to refresh_token
scopes: a list of space-separated requested scopes. Currently only all is supported
state (optional): a random string of your choice

The response to this request is identical to the bearer token response.

Operations

GetCapabilities

GetCapabilities operation with the optional Sections parameter

GET https://documentation-resources.opendatasoft.com/api/wfs?service=WFS&request=GetCapabilities&sections=OperationsMetadata,FeatureTypeList HTTP/1.1

The GetCapabilities operation allows clients to retrieve service metadata. The response is an XML document containing the information.

Parameters

This is the list of the supported parameters specific to the GetCapabilities operation. You should also take into consideration the common parameters. See here.

The existing parameters in the WFS standard that are not listed in this table are currently not supported.

Parameter	Description	Optionality and use
`Sections`	Unordered list of zero or more names of sections of service metadata document to be returned in service metadata document.	Optional. When omitted, returns the complete service metadata document.
`AcceptVersions`	Prioritized sequence of one or more specification versions accepted by client, with preferred versions listed first.	Optional. When omitted, returns the latest supported version.

*(AcceptFormats and UpdateSequences are not supported)

Response document

The WFS API returns from a GetCapabilities request sections in the service metadata. The section name can be used as a value for the Sections parameter.

Section name	Content
`ServiceIdentification`	Metadata about the WFS implementation
`ServiceProvider`	Metadata about the organization offering the WFS service
`OperationsMetadata`	Metadata about the WFS operations offered by the WFS implementation
`FeatureTypeList`	List of features types that are available from the service
`Languages`	Languages supported from the service
`Filter_Capabilities`	Metadata about the Filter encoding implementation

DescribeFeatureType

DescribeFeatureType operation with the optional TypeNames parameter

GET https://documentation-resources.opendatasoft.com/api/wfs?service=WFS&request=DescribeFeatureType&version=2.0.0&typeNames=ods:gender-equality-in-europe HTTP/1.1

The DescribeFeatureType operation generates a schema description of features types serviced by the WFS.

Parameters

This is the list of the supported parameters specific to the DescribeFeatureType operation. You should also take into consideration the common parameters. See here

The existing parameters in the WFS standard that are not listed in this table are currently not supported.

Parameter	Description	Optionality and use
`TypeName`	A comma-separated list of feature types to describe.	Optional. When omitted, return all feature types known.

*(OutputFormat is not supported)

GetFeature

GetFeature operation with the optional PropertyName parameter

GET https://documentation-resources.opendatasoft.com/api/wfs?service=WFS&request=GetFeature&version=2.0.0&typename=ods:gender-equality-in-europe&propertyname=country HTTP/1.1

The GetFeature operation allows retrieval of features from the WFS, and output them using the GML 3.1.1 representation.

Parameters

This is the list of the supported parameters specific to the GetFeature operation. You should also take into consideration the common parameters. See here.

The existing parameters in the WFS standard that are not listed in this table are currently not supported.

Parameter	Description	Optionality and use
`ResultType`	Used to indicate whether a WFS should generate a complete response document or an empty response document indicating only the number of features that the query would return	Optional. Values can be `hits` or `results`. Default value is `results`
`Count`	Used to define the maximum number of records that should be returned from the result set of a query	Optional
`TypeNames`	A list of feature type names to query	Optional
`PropertyNames`	A list of properties (dataset columns) that should be returned	Optional
`FeatureId`	An enumerated list of feature instances to fetch identified by their feature identifiers	Optional
`Bbox`	A bounding box used to filter the results by spatial extent	Optional

(OutputFormat and SortBy are not supported)

ListStoredQueries

ListStoredQueries operation

GET https://documentation-resources.opendatasoft.com/api/wfs?service=WFS&request=ListStoredQueries&version=2.0.0 HTTP/1.1

The ListStoredQueries operation lists the stored queries that are available in the WFS service, it does not require any parameters.

This operation is only available in v2.0.0.

DescribeStoredQueries

DescribeStoredQueries operation

GET https://documentation-resources.opendatasoft.com/api/wfs?service=WFS&request=DescribeStoredQueries&version=2.0.0 HTTP/1.1

The DescribeStoredQueries operation generates a description of the named stored queries that are available in the WFS service, it does not require any parameters.

This operation is only available in v2.0.0.