Download OGC API - Features to GeoJSON, Shapefile, or KML
Paste any public OGC API - Features URL, pick a collection, and download the result. Runs entirely in your browser — files never leave your device.
Paste the service URL
OGC API - Features is the modern REST/JSON successor to WFS, served by pygeoapi, ldproxy, GeoServer 2.20+, and ArcGIS Enterprise. Paste a landing page, /collections, or single-collection URL — the tool detects the shape, reads queryables for the schema, and pages through features using rel="next" links for reliable pagination even with opaque page tokens.
What is OGC API - Features?
OGC API - Features is the Open Geospatial Consortium's modern, REST-first protocol for serving vector geospatial data. Published in 2019, it's the successor to WFS — same goal (deliver features and attributes over HTTP) but built around JSON, GeoJSON, and the conventions web developers already know. There's no envelope of XML operations; you just follow links between resources.
A conformant server always has the same resource shape:
/— landing page/collections— list of collections/collections/{id}— metadata for one collection/collections/{id}/items— features (GeoJSON)/collections/{id}/queryables— the attribute schema (optional, Part 1)
You can paste any of the first three into the tool — it detects the shape and resolves the rest.
How it works
- Probe. The tool GETs
?f=jsonon the URL you pasted and follows the structure: landing → collections → metadata → queryables. - Read the schema. Fields come from
/queryables(a JSON Schema) when the server publishes one. If it doesn't, the tool fetches a single sample item and infers the field list from its properties. - Filter by attribute. Equality filters map directly to query parameters (
?fieldname=value) — the simplest and most widely supported mechanism. More complex filters (>,BETWEEN,LIKE) are encoded as CQL2. - Filter by area. Draw a bounding box; the tool adds
?bbox=minLon,minLat,maxLon,maxLat. - Preview. Fetch the first 10 items to sanity-check the query.
- Download. The tool pages through the collection by following
rel="next"links in each response (the recommended way, works even with opaque page tokens), then converts to your chosen format in the browser.
About CORS
Browsers require the server to include CORS headers allowing requests from other origins. Most public demos (pygeoapi, ldproxy) do. If you hit a CORS error on a private deployment, the server admin needs to enable CORS for https://www.quickmaptools.com. This is not something any browser tool can work around without a proxy.
Frequently asked questions
What is OGC API - Features?
OGC API - Features is the modern, RESTful successor to WFS. Instead of exchanging XML via GetCapabilities/DescribeFeatureType/GetFeature, it exposes JSON resources under a predictable path structure: a landing page lists collections at /collections; each collection has metadata at /collections/{id} and features at /collections/{id}/items. Responses are GeoJSON by default.
What URL should I paste?
Any of three shapes: the server's landing page (e.g. https://demo.pygeoapi.io/master), the collections list (.../collections), or a single collection (.../collections/obs). The tool detects which shape you gave it and follows links from there.
How does this differ from WFS?
Both serve vector features over HTTP, but OGC API - Features is JSON-first, uses standard REST conventions, and is much easier for web clients to consume. WFS 2.0 is XML-based and better-established in enterprise GIS; OGC API - Features is newer (published 2019) and is now the default way new servers expose vector data. GeoServer, pygeoapi, ldproxy, QGIS Server, and Esri Enterprise can all publish OGC API - Features today.
How do attribute filters work?
Simple equality filters (field = value) become standard URL query parameters — ?fieldname=value — which every compliant server supports. Anything more complex (>, <, BETWEEN, LIKE, NULL) is encoded into a CQL2 text filter and passed via ?filter=…&filter-lang=cql2-text, per OGC API - Features Part 3. Not every server implements CQL2 yet; if yours doesn't, stick to equality filters or narrow your query with the bounding box.
How does pagination work?
The tool follows the rel="next" links the server returns on each page — this works even when the server uses opaque page tokens rather than numeric offsets. Typical page sizes are 1000 features. There is a default 5000-feature cap you can raise; very large collections should be narrowed with a bounding box or attribute filter.
Why does the tool say "Server blocks browser access (CORS)"?
Browser security requires the server to include CORS headers allowing requests from other origins. Most public OGC API - Features deployments (pygeoapi demo, ldproxy demo, GeoServer 2.20+) do. Private deployments often don't. Contact the service admin and ask them to enable CORS for https://www.quickmaptools.com.
Do my data or my queries go through your servers?
No. Your browser queries the OGC API - Features server directly. QuickMapTools only sees the URL you paste. Results are decoded and converted in your browser with GDAL-WebAssembly.