-
Notifications
You must be signed in to change notification settings - Fork 2
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
Changes recommended by Advisory Group for review by Steering Group #22
Open
padajo
wants to merge
29
commits into
main
Choose a base branch
from
recommended
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Adding Gemini 2.3 metadata standard. After discussion, the INSPIRE metadata standard will be the one used to validate metadata on the platform, with additional information on how to make the metadata Gemini 2.3 compliant.
Update README.md - to resolve the conflicts between main and working.
Resolving merge conflict by replacing previous version into the working branch.
At the Advisory Group, it was requested that we review GitBook instead of GitHub. https://docs.gitbook.com/
…age-reservoir-levels.md
Update data standards page to add Gemini/INSPIRE metadata standard
Change from using GitHub to Gitbook
Working Schema folder created and populated
Changes recommended for review by Advisory Group
elucasaiimicom
approved these changes
Nov 25, 2024
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.
These are the changes that the Stream Advisory Group (Technical) has approved for review by the Stream Steering Group after a recommendation by the Stream Data Standards Workstream to update the data standards.
This pull request will only be accepted if the Steering Group adopts the changes specified.
Overview of the changes:
Addition of GEMINI 2.3 as the metadata standard, based upon INSPIRE
Updating the main page (README.md) to clarify that these are a work in progress, but are also the current accepted version of the data standards for Stream
The addition of a schema section for Stream data
The addition of schema for the use cases that are already published
The reason that schema has been added here is to give a centralised and public location for the schema, instead of replicating the same information for each dataset.