Landing Page

GET

/stac/

const url = 'https://example.com/stac/';
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/stac/

STAC Catalog landing page.

Responses

200

Successful Response

application/json

StacCatalog

STAC Catalog / landing page response.

object

type

Type

STAC object type. Always ‘Catalog’ for the landing page.

string

default: Catalog

required

Stable identifier for the catalog.

string

stac_version

Stac Version

STAC specification version implemented.

string

default: 1.0.0

title

required

Title

Catalog title.

string

description

required

Description

Human-readable catalog description.

string

conformsTo

required

Conformsto

List of conformance URIs declaring which STAC and OGC API standards the catalog implements.

Array<string>

links

required

Links

Catalog navigation links (self, root, search, collections, etc.).

Array<object>

StacLink

A single STAC link object.

object

href

required

Href

Target URL of the link.

string

rel

required

Rel

Link relation type (e.g. ‘self’, ‘root’, ‘parent’, ‘item’, ‘data’).

string

type

Any of:

string
null

string

method

Any of:

string
null

string

Example

{
  "type": "Catalog",
  "stac_version": "1.0.0"
}

400

Bad request — invalid standards parameters

application/problem+json

ProblemDetail

object

type

Type

string

default: about:blank

title

required

Title

string

status

required

Status

integer

detail

required

Any of:

string

Example

{
  "detail": "Dataset not found",
  "status": 404,
  "title": "Not Found",
  "type": "about:blank"
}

401

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.

application/problem+json

ProblemDetail

object

type

Type

string

default: about:blank

title

required

Title

string

status

required

Status

integer

detail

required

Any of:

string

Example

{
  "detail": "Dataset not found",
  "status": 404,
  "title": "Not Found",
  "type": "about:blank"
}

429

Too many requests — retry after the advertised interval

application/problem+json

ProblemDetail

object

type

Type

string

default: about:blank

title

required

Title

string

status

required

Status

integer

detail

required

Any of:

string

Example

{
  "detail": "Dataset not found",
  "status": 404,
  "title": "Not Found",
  "type": "about:blank"
}

Headers

Retry-After

integer

Seconds until the request may be retried

500

Internal server error

application/problem+json

ProblemDetail

object

type

Type

string

default: about:blank

title

required

Title

string

status

required

Status

integer

detail

required

Any of:

string

Example

{
  "detail": "Dataset not found",
  "status": 404,
  "title": "Not Found",
  "type": "about:blank"
}

503

Service unavailable — the database could not serve the request

application/problem+json

ProblemDetail

object

type

Type

string

default: about:blank

title

required

Title

string

status

required

Status

integer

detail

required

Any of:

string

Example

{
  "detail": "Dataset not found",
  "status": 404,
  "title": "Not Found",
  "type": "about:blank"
}

Privacy Apache 2.0 getgeolens.com