Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EPIC] STAC metadata upgrade & rework #1027

Open
jdries opened this issue Jan 31, 2025 · 1 comment
Open

[EPIC] STAC metadata upgrade & rework #1027

jdries opened this issue Jan 31, 2025 · 1 comment
Assignees

Comments

@jdries
Copy link
Contributor

jdries commented Jan 31, 2025

Our own STAC metadata generation is showing its age and is not correct in some places. It's becoming increasingly urgent to rework this.

  1. Support newer STAC versions
  2. asset per band: group assets in item, do not create one item per assets
  3. define item_assets in collection metadata
  4. Asset keys should not be item id's or contain dates. They should be the same across the collection.

I propose to make the STAC version of the output a format or job option? We need to offer a proper migration path, also considering that large scale production projects may already depend on the current form of STAC metadata we create.

@jdries
Copy link
Contributor Author

jdries commented Feb 4, 2025

Design idea: scala side returns a list of preliminary item json objects rather than a list of asset filenames.
The python side then transforms/augments the preliminary json into fully stac compliant json, allowing a fairly generic code path for the STAC metadata construction.

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

No branches or pull requests

2 participants