Get Features Geojson Z Endpoint
const url = 'https://example.com/datasets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/features.geojson';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/features.geojsonReturn up to 5,000 features as RFC 7946 GeoJSON with Z coordinates.
X-Embed-Token authorizes private datasets in the token’s scope through
the same capability check used for tile requests.
Anonymous callers can read public, published datasets. Private or restricted datasets return 404 unless user or embed credentials authorize access.
Supplied credentials that are expired or revoked receive 401 so clients can refresh them. Requests without credentials use the anonymous access path.
Authorizations
Section titled “ Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”Header Parameters
Section titled “ Header Parameters ”Responses
Section titled “ Responses ”Successful Response
Example generated
exampleBad 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 valid X-Embed-Token that authorizes the request on its own. That request is served and the unrelated credential is ignored.
Forbidden — caller lacks access to this resource
Not found
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