vpts files can have a column processing with an identifier to information about the vol2bird (or other) processing settings used. This settings can be described in a processing.csv, where many vpts rows can point to a single row in processing.csv (i.e. same settings). As a result, processing.csv will often contain just a single row, but expressing it as a csv offers the flexibility to record more processing settings and relate it to the primary data.
The expected fields in processing.csv should be recorded in a table schema (cf. the one for vpts)
vpts
files can have a columnprocessing
with an identifier to information about the vol2bird (or other) processing settings used. This settings can be described in aprocessing.csv
, where many vpts rows can point to a single row inprocessing.csv
(i.e. same settings). As a result,processing.csv
will often contain just a single row, but expressing it as a csv offers the flexibility to record more processing settings and relate it to the primary data.The expected fields in processing.csv should be recorded in a table schema (cf. the one for vpts)
@adokter can you tackle this?