Closed oarcher closed 1 year ago
From my point of view, the best way is to store these variables as xarray variable of size () in the dataset. This is not a problem and it keeps homogeneity between all variables and all attributes/name/...
Homogeneity makes further manipulation easier
The definition of each variables has been added using the xsd files #118 . There is no ascendent nodes definition but it seems to do the job. @oarcher let me know if you prefer to go for your first idea or if I close this issue.
I close this issue, since the current implementation seems to bring enough information. Feel free to re-open.
35 is good to add used xpath to 'history' attribute, when the variable is an xarray variable.
But there is a limitation when the variable is a scalar, and packed in a simple structure, like a dict.
For example, here are the 'attrs' dict for a dataset:
Each values in the dict are python type, with no informations about xml xpath.
We could change those simple python types with a class
XmlVar
, that should have the followings attributes:The doc attribute can be extracted from SAFE directory `support/*.xsd' . It seems that there is no easy way to translate xpath from xml file to xsd file.
Here is a first approach that could be used in a PR:
The output is the documentation string for
slantRangeTime
and for all preceding blocks: