about the sublinks, i guess it is about different polarizations / frequencies ?
If this is the case, I would see two different ways to treat them (at least for the metadata and csv files) :
a general ID for the link ("Link identifier", as it is in the document) and then a list of sublinks (a kind of dictionary), each with associated frequency and polarization.
For instance if the metadata are in json format it could look like this :
{
"ID" = "xxxx"
"sublinks" : [
{ "ID" : "xxxx_UH", "frequency" : "12000MHz", "polar" : "H"},
{ "ID" : "xxxx_UV", "frequency" : "12000MHz", "polar" : "V"},
{ "ID" : "xxxx_LH", "frequency" : "11300MHz", "polar" : "H"}
]
}
And then the *.csv raw data file would look like :
"
timestamp ; RSL xxxx_UH ; RSL xxxx_UV ; RSL xxxx_LH
"
each sublink is treated as an independant link (there is no more notion of sublink). In this case there is no more "sublinks" section in the metadata file and only 2 columns (timestamp and RSL) in the raw data file.
about the sublinks, i guess it is about different polarizations / frequencies ? If this is the case, I would see two different ways to treat them (at least for the metadata and csv files) :
For instance if the metadata are in json format it could look like this : { "ID" = "xxxx" "sublinks" : [ { "ID" : "xxxx_UH", "frequency" : "12000MHz", "polar" : "H"}, { "ID" : "xxxx_UV", "frequency" : "12000MHz", "polar" : "V"}, { "ID" : "xxxx_LH", "frequency" : "11300MHz", "polar" : "H"} ] }
And then the *.csv raw data file would look like : " timestamp ; RSL xxxx_UH ; RSL xxxx_UV ; RSL xxxx_LH "