> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/upload-anything/data-sources/web-feature-service-wfs.md). # Web Feature Service (WFS) Add vector layers from a Web Feature Service (WFS), such as GeoServer. Use its URL on one map or connect it as a shared source. A Web Feature Service (WFS) is an Open Geospatial Consortium (OGC) standard for sharing vector features over the internet, served by software such as GeoServer. Felt copies a service's feature types into maps as vector layers, so adding or refreshing one counts toward your workspace's processing limit. See [Plan usage](/plans-and-billing/plan-usage.md). You can add a service to one map from a URL, or connect it as a source that everyone with access can use on any map. ## Add a WFS layer to a map Add a WFS layer from a URL that meets the [URL requirements](#url-requirements). 1. In the center of the toolbar at the top of the map, click **Upload Anything** > **From URL**. 2. Paste the service's URL and click **Add to map**. See [Add data from URLs](/upload-anything/urls.md). ## Connect a WFS source Connecting a WFS source needs Edit access to the workspace. Follow the steps in [Add a source](/upload-anything/data-sources/add-a-source.md#connect-a-source), select **Web Feature Service (WFS)**, and in **Connection**, enter the service's **URL**. If the server accepts requests only from known addresses, [allow Felt's IP addresses](/upload-anything/data-sources/add-a-source.md#allow-felts-ip-addresses). A WFS source has no credential fields. If the server needs a login, include it in the URL, such as `https://user:password@example.com/geoserver/wfs`. A GeoServer `authkey` parameter can go in the URL too. Only people with Edit access to the source can see its URL. Felt doesn't hide a password in the URL from them the way it hides credential fields, so use a read-only account for Felt. ## URL requirements Felt reads the service's capabilities from its URL, so the URL must point to the service itself, not to one file or request. * The URL must contain `wfs`, regardless of capitalization, such as `https://example.com/geoserver/wfs`. * Felt supports WFS 2.0.0, 1.1.0, and 1.0.0. To force a version, add a `version` parameter. * To add only some feature types, list them in the `typeNames` or `typeName` parameter. Otherwise, Felt adds every feature type in the service. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.felt.com/upload-anything/data-sources/web-feature-service-wfs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.