You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR addresses the following problem / context:
All resources should have a defined abstract and keywords for the pygeoapi-rendered frontend to display
How
Implementation summary - the following was changed / added / removed:
add/update abstract and keywords for all resources in orchestration/config/products.yaml
Notes
Any special considerations, workarounds, or follow-up work to note?
I used my best judgement to document non-summary and non-timeseries layers, but the metadata for them is sparse.
It is easier to determine the sources at the end of the abstract rather than point to the data dictionary at the end. the sources and data dictionary were therefore flipped for an easier-to-assess abstract for each resource.
@jacob-a-brown Looking good. Question: do you think there's a better way to note the data orchestration schedule to the user besides (or in addition to) writing the day of the month in the abstract? Since we can change that programmed schedule it would be nice if that info stayed in sync. Is there another place to put that in the collection metadata?
I think that we could read each resource's schedule and use it to add that information to the abstract so that it gets auto-created whenever the Docker image is made. It would/could be a similar process to automatically creating the sources/parameter table on the landing page. I want to get all metadata into a central location so we have a single source of truth rather than needing to update multiple parameters in multiple places. I can add this to my list of ideas for repository refactoring and reorganization.
This file contains hidden or 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
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.
Why
This PR addresses the following problem / context:
abstractandkeywordsfor the pygeoapi-rendered frontend to displayHow
Implementation summary - the following was changed / added / removed:
abstractandkeywordsfor all resources inorchestration/config/products.yamlNotes
Any special considerations, workarounds, or follow-up work to note?