-
Notifications
You must be signed in to change notification settings - Fork 122
Implement collection summary functionality #327
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
Milestone
Comments
This was referenced May 3, 2021
4 tasks
This was referenced Jun 28, 2021
@m-mohr My understanding is that Collection summaries do not apply to the Item Assets Extension since it only has Collection scope. Is that correct? |
Yes, indeed. (Sorry for the misclick.) |
@lossyrob I think I'm going to go ahead and start the release without the Datacube Extension summaries. I can add those in a patch release early next week. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #309, the ability to extract collection summary information for extensions was implemented for the eo extension (see
SummariesEOExtension
inextensions/eo.py
). This should be implemented for each other extension, and tested across all the extensions, as well as pydocs written for that functionality.Top level sphinx documentation should also be written for the summaries extensions as a pattern.
Summary information should only be used where it makes sense; e.g. if something will be a large range of discrete values that doesn't makes sense to put into a range, then we shouldn't make a summary entry for it.
Thought should be put into how the CommonMetadata works here - should we have a similar extension functionality for getting and setting common metadata summary information?
Extensions this issue potentially applies to:
The text was updated successfully, but these errors were encountered: