...
The structure files contain the variable definitions (including the links between them) for the Bayesian network. Variables of the same category are defined in the same file. Because there are five categories, i.e. boundary condition (BC), receptor (R), hazard (H), impact (C) and measure (M), there are five structure files. The data format is JSON (http://www.json.org/). A JSON object is an unordered set of name/value pairs. Each variables is defined by a name/value pair. Consistent naming of the variables across all files (netCDF, JSON, text) is crucial. Consequently, for variables that are exported from FEWS to the model adaptor, that are BC and H variables, the name must be the FEWS ID. In case of R variables the name points to a text file of the the same filename.
The values itself The paired values are JSON objects with at least four name/value pairs on their own:
- "title" is the title of the variable as seen in the BN
- "bins" is an array containing the bin values itself or the interval boundaries for each bin depending on the value in "nobins". The values can either be numeric or a string starting with a letter and without any spaces.
- "nobins" is an integer defining the number of bins (or states) in the BN. If "nobins" equals the length of the "bins" array, each value in "bins" is a bin. If "nobins" is one smaller that the length of the "bins" array, the values in "bins" are taken to be the interval boundaries of each bin.
- "parents" is an array of the "ID"s of parent variables or "None".
- (optional:) "aggregation" describes the method by which data will be extracted from netCDF files. This is only relevant for hazard variables. It can have either "max" or "mean" as a value, indicating of the average of maximum is taken when aggregation of several hydraulic model grid points takes place.
...