In this part the layout of all the different file types (used by the general adapter ) is briefly described. The full description is given in E Fileformats and holds the schema documentation. If the schema documentation is not complete (or clear), the actual schema (XSD) files should be consulted. The supported ASCII grids and binary grids are not described in the schema files. The format descriptions of these files are contained within this document in the Appendices.
Please note that only a subset of the presented files formats may be needed for a particular application. It's prime communication with external forecasting modules is through dynamic data such as time series, model states and diagnostics (see below). The published interface formats have been defined to cover a wider range of data types, but these need not be used in all cases - i.e. there is no requirement to allow communication of all data types. Indeed there is currently no module that caters for the full range of formats.
In exchanging data between a module and NFFS, a prioritisation of data types can be identified.
Priority |
Data Type |
Comment |
1 |
Time Series |
sufficient to cover most modules used in flood forecasting systems, including e.g. Mike-11 and NAM |
1 (a) |
Time series of grid data |
additionaly required for modules with 2D I/O formats (e.g inundation codes) |
2 |
Parameters |
Module parameters may be passed where the module allows calibration through the NFFS calibration facilities |
2 (a) |
Longitudinal profile data |
For hydrodynamic modules longitudinal data types may be passed - not a strict requirement. |
3 |
Static data (cross sections, branches, etc) |
This data is not required for operational forecasting. In exceptional cases data such as on branches may be required (for display purposes), but this need not be passed through the adapter and can be configured as appropriate. |
