...
Imports time series data from Diver loggers. The files have a sort of Windows ini file format with file extension (*.mon). The format of the MON ini files is not well defined. Many programs interpret the structure differently and have various names for the ini file sections and parameters.
Sections: Section declarations start with '\[' and end with '\]'; i.e. '\[Logger settings\]' or '\[Instrument info\]'.Wiki Markup - Parameters or item: this is the content of a section with an '=' sign between the key and the value; i.e. "location = abc"
...
The files can contain a flexible number of channels, where one a channel will contain information on one parameter. Example files with 2 and 3 channels will be shown, when multiple channels/parameters need to be imported a <timeSeriesSet> needs to be configured for each channel/parameter. To illustrate this an example config for an import with 3 channels is given.
Configuration (Example)
A complete import module configuration consists of an ID Mapping file and a Import Module Instance file.
...
The Mon Import module in Delft-FEWS does not parse all data in the MON file. The important sections and parameters are the following:
\[Logger settings\] or \[Instrument info\]; Read location Id from this [Logger settings] or [Instrument info]; Read location Id from this sectionWiki Markup - Location or Locatie ; location Id
- \[Channel X\] or \ [Kanaal X\] ; Not used
\[Series settings\] or \ [Instrument info from data header\] ; Not usedWiki Markup Wiki Markup - \[Channel X from data header\] or \ [Kanaal X from data header\]; Read Parameter Id
- Identification or Identificatie = Parameter Id
\[Data\]; Data values with the different channels in columns. The datavalues may have a "."or a ","as decimal seperator, both options are accepter by the import function.Wiki Markup
When the MON file is not in the correct format a warning message is returned. Known problems are missing location ID's or parameter ID's in the MON files.
...