Skip to content

feat: implement the alternate assets extension - #1830

Open
keewis wants to merge 18 commits into
stac-utils:mainfrom
keewis:alternate-assets
Open

keewis wants to merge 18 commits into
stac-utils:mainfrom
keewis:alternate-assets

Conversation

@keewis

@keewis keewis commented Oct 15, 2026 •

Copy link
Copy Markdown

Related Issue(s):

Description:

The alternate assets extension allows specifying different hrefs to reach the same object through different methods (e.g. different protocols). I personally need this for stac-utils/xpystac#71.

Intentionally a draft PR until I found the time to write some more tests.

Handwritten, no LLM involved in any part of this PR.

cc @jsignell

PR Checklist:

  • Pre-commit hooks pass (run pre-commit run --all-files)
  • Tests pass (run pytest)
  • Documentation has been updated to reflect changes, if applicable
  • This PR maintains or improves overall codebase code coverage
  • This PR's title is formatted per conventional commits

@keewis
keewis marked this pull request as ready for review October 20, 2026 22:56
@keewis

keewis commented Oct 20, 2026 •

Copy link
Copy Markdown
Author

still to be resolved is the interaction with other extensions. In theory, converting the AlternateAsset object to a pystac.Asset object does allow this, but this means that the mutation of the alternate asset is not possible anymore: the properties the asset was constructed from were copied to support the inheritance of properties from the default asset (unless I'm reading the spec wrong?)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant