Fix/collection summaries and extents #78
Closed
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
….7 inbuilt collection_extent utility
|
Meant to open a PR against dev |
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
Use inbuilt pgstac utility function
pgstac.collection_extent(collection_id text)to apply the maximum date range from the items partitions instead of the outdatedcollection_temporal_extentutility that uses only the nominal item datetime.How tested
I executed and verified this method in a test database deployed for this backend pr. I'm still trying to think of ways to test the actual changes in the ingestor but the updating dev deployment and running an actual ingest may be the easiest way to go.
NASA-IMPACT/veda-backend#211