Skip to contents

stac_build() writes a root catalog.json that knows only the version it just built, so copying it over a deployed catalog would orphan every other release. This edits the DEPLOYED root instead: it adds ./{version}/collection.json as a child if it is not already there and keeps the children in release order (v7, v7b, v8, ... — numeric part, then suffix), which is how a patch release dated after its successors still lands beside the release it patches. A missing catalog is created.

Usage

stac_catalog_register(catalog_json, version, cfg = stac_cfg(version))

Arguments

catalog_json

path to the deployed root catalog.json

version

version to register, e.g. "v7b"

cfg

config from stac_cfg() (used only when the catalog does not exist yet)

Value

invisibly, the child hrefs now in the catalog, in order