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
Current different groups publish their metadata to OceanGliders in different flavours of JSON. This arose out of the way tools were developed and a common JSON format was not formally defined, documented or ratified by the OGDMTT. An ambition of the OG 1.0 format was to remove the need for auxiliary metadata files but there may be use cases where this is required, e.g. data that have an initial restriction.
This issue was raised at the European Glider data management workshops in June 2022 and we need to revisit as we move forward with OG 1.0.
The text was updated successfully, but these errors were encountered:
Following issue #75 and anticipating on OG1.0 format delivery. I am proposing here a metadata file that will agregate all metadata into a json file, easy to read and very usefull for monitoring (amongst other thing).
This is a practice adopted by Argo with very good results in terms of monitoring.
This is to be discussed amongst each other and not to be tackle before the iugc2024.
Current different groups publish their metadata to OceanGliders in different flavours of JSON. This arose out of the way tools were developed and a common JSON format was not formally defined, documented or ratified by the OGDMTT. An ambition of the OG 1.0 format was to remove the need for auxiliary metadata files but there may be use cases where this is required, e.g. data that have an initial restriction.
This issue was raised at the European Glider data management workshops in June 2022 and we need to revisit as we move forward with OG 1.0.
The text was updated successfully, but these errors were encountered: