...
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.
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 Date format used is: "yyyy/MM/dd HH:mm:ss"
Configuration (Example)
A complete import module configuration consists of an ID Mapping file and a Import Module Instance file.
ModuleConfigFiles
The files can contain a flexible number of channels, where 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.
ModuleConfigFiles
The following example of an Import Module Instance The following example of an Import Module Instance will import the time series as equidistant series for timezone GMT+1 with a time step of 1 hour. Many times the MON files do not save the data at rounded hourly tims, therefore a tolerance has been added to map the imported data to correct hourly interval time series.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun ......">
<import>
<general>
<importType>DIVERMON</importType>
<folder>$IMPORT_FOLDER_MON$</folder>
<failedFolder>$IMPORT_FAILED_FOLDER_MON$</failedFolder>
<backupFolder>$IMPORT_BACKUP_FOLDER_MON$</backupFolder>
<idMapId>IdImportMON</idMapId>
<unitConversionsId>ImportUnitConversions</unitConversionsId>
<importTimeZone>
<timeZoneOffset>+01:00</timeZoneOffset>
</importTimeZone>
<dataFeedId>MON</dataFeedId>
</general>
<tolerance locationSetId="ImportMON_H.meting.cm_uur" parameterId="H.meting.cm" timeUnit="minute" unitCount="30"/>
<timeSeriesSet>
<moduleInstanceId>ImportMON</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>H.meting.cm</parameterId>
<locationSetId>ImportMON_H.meting.cm_uur</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour" multiplier="1"/>
<readWriteMode>add originals</readWriteMode>
<synchLevel>1</synchLevel>
</timeSeriesSet>
</import>
</timeSeriesImportRun>
|
IdMapFiles
ID mapping fefines mappings between Diver MON and FEWS parameters and locations. Remember that ID mapping is case sensitive.Here is an example config file for an import file with three channels:
| Code Block | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun ......">
<import>
<general>
<importType>DiverMon</importType>
<folder>$IMPORT_FOLDER$/DiverMon</folder>
<idMapId>IdMap</idMapId>
<missingValue>-999.0</missingValue>
<expiryTime unit="day" multiplier="366"/>
</general>
<timeSeriesSet>
<moduleInstanceId>ImportMON</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>X.yy.zz</parameterId>
<locationId>Delft</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="minute" multiplier="10"/>
<readWriteMode>add originals</readWriteMode>
</timeSeriesSet>
<timeSeriesSet>
<moduleInstanceId>ImportMON</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>A.bb.cc</parameterId>
<locationId>Delft</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="minute" multiplier="10"/>
<readWriteMode>add originals</readWriteMode>
</timeSeriesSet>
<timeSeriesSet>
<moduleInstanceId>ImportMON</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>D.ee.ff</parameterId>
<locationId>Delft</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="minute" multiplier="10"/>
<readWriteMode>add originals</readWriteMode>
</timeSeriesSet>
</import>
</timeSeriesImportRun>
|
IdMapFiles
ID mapping defines mappings between Diver MON and FEWS parameters and locations. Remember that ID mapping is case sensitive.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<idMap version="1.1" ..............> <parameter internal="G.hh.ii" external="LEVEL"/> <parameter internal="J.kk.ll" external="TEMPERATURE"/> <parameter internal="X.yy.zz" external="PCH"/> <parameter internal="A.bb.cc" external="HG"/> <parameter internal="D.ee.ff" external="2: SPEC.COND."/> <location internal="Utrecht" external="13PB1"/> <location internal="Delft" external="ro954 <idMap version="1.1" ..............> <map internalParameter="H.meting.cm" internalLocation="Dorperdijk_beneden" externalParameter="niveau" externalLocation="Dorperdijk beneden"/> </idMap> |
Example file
There is a wide range of MON file types, here are examples of files with 2 and 3 channels respectively.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
Data file for DataLogger. ============================================================================== COMPANY : <Company name> COMP.STATUS: Do DATE : 22/10/2013 TIME : 07:22:29 FILENAME : D:\diver offive\vistrap\MON\ro954_131022072229_M0026.MON CREATED BY : SWS Diver-Office 5.0.25.0 ========================== BEGINNING OF DATA ========================== [Logger settings] Instrument type =CTD-Diver=17 Status =Started =0 Serial number =.N10-M0026 317. Instrument number = =0 Location =ro954 Sample period =M10 Sample method =T Number of channels =3 [Channel 1] Identification =PRESSURE Reference level =400 cm Range =5750 cm Master level =5750 CMH2O Altitude =0 m [Channel 2] Identification =TEMPERATURE Reference level =-20.00 °C Range =100.00 °C [Channel 3] Identification =2: SPEC.COND. Reference level =0.000 mS/cm Range =120.000 mS/cm [Series settings] Serial number =.N10-M0026 317. Instrument number Serial number = =.N10-M0026 317. Instrument number = Location =ro954 Sample period =00 00:10:00 0 Sample method =T Start date / time =00:00:08 12/09/13 End date / time =00:20:06 22/10/13 [Channel 1 from data header] Identification =PRESSURE Reference level =400 cm Range =5750 cm Master level =5750 CMH2O Altitude =0 m [Channel 2 from data header] Identification =TEMPERATURE Reference level =-20.00 °C Range =100.00 °C [Channel 3 from data header] Identification =2: SPEC.COND. Reference level =0.000 mS/cm Range =120.000 mS/cm [Data] 5751 2013/09/12 08:00:00.0 1332 18.18 0.824 2013/09/12 08:10:00.0 1326 18.18 0.828 2013/09/12 08:20:00.0 1328 18.17 0.824 2013/09/12 08:30:00.0 1329 18.16 0.828 2013/09/12 08:40:00.0 1329 18.17 0.824 2013/09/12 08:50:00.0 1328 18.21 0.824 2013/09/12 09:00:00.0 1329 18.23 0.820 |
...
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 section
- Location or Locatie ; location Id
Wiki Markup - \[Series settings\] or \ [Instrument info from data header\] ; Not used
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.
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.
...