Commit a137e77c authored by cponcele's avatar cponcele
Browse files

move history variable

parent 0f30f846
......@@ -2,7 +2,13 @@
"name": "",
"obligation": "M",
"comment": "root",
"dims": [],
"dims": [
{
"value": "unlimited",
"name": "history",
"comment": "Number of history records, unlimited length to allow to add more "
}
],
"types": [],
"attributes": [
{
......@@ -59,6 +65,14 @@
"obligation": "M",
"comment": "A short phrase or sentence describing the dataset. For direct sonar-generated files, this can be as simple as \"Files generated by the XYZ sonar\"."
},
{
"name": "processing_status",
"obligation": "O",
"comment": "For a given field of work or kind of sounder, processing workflow is usually standardized. This file contains description on the status of the processing applied to the data. Description is free and left to the user and software, it could be a json or xml field containing metadata like 'Tide Correction : Done' ",
"type": "string",
"value": ""
},
{
"name": "xsf_convention_version",
"obligation": "M",
......@@ -99,7 +113,22 @@
"type": "double"
}
]
}
},
{
"name": "history",
"obligation": "O",
"comment": "An array of string containing an historical description of processing or transformations applied to the data. Description is free, if possible it should be time stamped at the date and time when processing occured : for example 2019-09-07T15:50+00Z File conversion by XXX software",
"dims": [
"history"
],
"type": "string",
"attributes": [
{
"name": "long_name",
"value": "history"
}
]
}
],
"coordinatevariables": [],
"subGroups": []
......
{
"name": "Sonar",
"dims": [
{
"value": "unlimited",
"name": "history",
"comment": "Number of history records, unlimited length to allow to add more "
}
],
"types": [
{
......@@ -56,33 +52,12 @@
"obligation": "M",
"comment": "Type of sonar, chosen from a defined vocabulary (currently only one value): ”omnisonar” (a sonar with a nominally omnidirectional mode).",
"value": "omni-sonar"
},
{
"name": "processing_status",
"obligation": "O",
"comment": "For a given field of work or kind of sounder, processing workflow is usually standardized. This file contains description on the status of the processing applied to the data. Description is free and left to the user and software, it could be a json or xml field containing metadata like 'Tide Correction : Done' ",
"type": "string",
"value": ""
}
],
"variables": [
{
"name": "history",
"obligation": "O",
"comment": "An array of string containing an historical description of processing or transformations applied to the data. Description is free, if possible it should be time stamped at the date and time when processing occured : for example 2019-09-07T15:50+00Z File conversion by XXX software",
"dims": [
"history"
],
"type": "string",
"attributes": [
{
"name": "long_name",
"value": "history"
}
]
}
],
"coordinatevariables": [],
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment