fix: vector ingest can use href from preprocessed object metadata #319
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… been preprocessed for cog ingest
anayeaye
changed the title
smohiudd
approved these changes
Mar 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
This is a temporary solution to continue using s3 discovery that was written for generating stac item metadata for COG assets. All the vector pipeline needs comes from the property that has been preprocessed to asset href in the discovery response.
Why
Existing vector ingests have been using the preprocessed stac item metadata even though it does not agree with features db schema. In the future the stac item metadata preprocessing should be removed from the generic s3 discovery.