Export Dataset Endpoint
const url = 'https://example.com/datasets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/export?format=gpkg';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://example.com/datasets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/export?format=gpkg'Export a dataset as a downloadable file.
Supports GeoPackage, GeoJSON, Shapefile (zipped), CSV, GeoParquet, FlatGeobuf, and PMTiles formats. Optional CRS reprojection, spatial filtering, and attribute filtering. GeoParquet is always emitted in EPSG:4326 (OGC:CRS84). PMTiles renders zooms 0..N where N is extent-budgeted (ceiling 14).
Authorizations
Section titled “ Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”Query Parameters
Section titled “ Query Parameters ”Responses
Section titled “ Responses ”Successful Response
Bad request — invalid query parameters or payload
Unauthenticated — a credential was supplied and could not be resolved (expired, revoked, or malformed). Sending no credential at all is not an error on these operations; they answer anonymously with the public subset. Neither is sending an unresolvable credential alongside a capability that authorizes the request on its own — a valid X-Embed-Token or a valid signed tile template (sig, exp, scope). Those are served and the unrelated credential is ignored.
Forbidden — caller lacks access to this resource
Not found
Precondition failed — the caller’s If-Match no longer matches the current representation
Payload too large
Validation error
Too many requests — retry after the advertised interval
Headers
Section titled “ Headers ”Seconds until the request may be retried
Internal server error
Service unavailable — the database could not serve the request