STAC API entry point. Discovery (landing, collections, collection) plus search (search, searchAll, searchStream) and item fetch.

Constructors

Properties

client: HonuaClient

Methods

  • Parameters

    • request: {
          collectionId: string | number;
          extraParams?: Record<string, string | number | boolean>;
          itemId: string | number;
          responseFormat?: string;
          signal?: AbortSignal;
          stacBasePath?: string;
      }
      • collectionId: string | number
      • OptionalextraParams?: Record<string, string | number | boolean>
      • itemId: string | number
      • OptionalresponseFormat?: string
      • Optionalsignal?: AbortSignal
      • OptionalstacBasePath?: string

    Returns Promise<HonuaStacItemResponse>

  • Whether the API advertises POST /search.

    STAC API - Item Search requires GET /search and makes POST optional, so the POST support has to be discovered rather than assumed: servers list the endpoint on the landing page as a rel="search" link per method (stac-fastapi / pgstac and stac-server emit both a GET and a POST link). The probe runs at most once per instance and resolves to false when the landing page is unreachable or advertises no POST search link, so callers fall back to the universally supported GET.

    Parameters

    • Optionalsignal: AbortSignal

    Returns Promise<boolean>