Validate Geodcat Ap Catalog
const url = 'https://example.com/datasets/geodcat-ap/validation/';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/geodcat-ap/validation/Validate the visible GeoDCAT-AP 2.0.0 catalog feed.
Authorizations
Section titled “ Authorizations ”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 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.
Not found
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