Overview
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.
- 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 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.
<?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.
<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, this is just one example.
Data file for DataLogger. ============================================================================== COMPANY : Your Company Name LICENSE : DATE : 08/24/07 TIME : 11:20:44 FILENAME : H:\Grondwater\DLG-Mariapeel NIEUW\24-8-2007\13PB175646_03_16_0708_23_07.mon CREATED BY : EnviroMon version 1.9 ========================== BEGINNING OF DATA ========================== [Instrument info] Instrument type =Diver =3 Instrument state =Stopped =2 Serial number =.N00-75646 210. Instrument number =13PB1 =0.00000000000000E-0000 Location =13PB1 Sample Rate =00 01:00:00 0 Sample Mode =T Channel =2 [Channel 1] Identification =LEVEL Reference =0.0 cm Range =500.0 cm Master Level =0.0 cm Altitude =0 m [Channel 2] Identification =TEMPERATURE Reference =-20.00 deg C Range =100.00 deg C Master Level =100.00 deg C Altitude =-20.00 deg C [Instrument info from data header] Serial number =.N00-75646 210. Instrument number =13PB1 Location =13PB1 Sample Rate =00 01:00:00 0 Sample Mode =T Tb =22:47:10 16/03/07 Te =22:47:10 23/08/07 [Channel 1 from data header] Identification =LEVEL Reference =0.0 cm Range =500.0 cm Master Level =0.0 cm Altitude =0 m [Channel 2 from data header] Identification =TEMPERATURE Reference =-20.00 deg C Range =100.00 deg C Master Level =100.00 deg C Altitude =-20.00 deg C [Data] 3841 2007/03/16 10:47:22.0 93.2 11.61 2007/03/16 11:47:22.0 209.7 8.96 2007/03/16 12:47:22.0 209.4 8.93 2007/03/16 13:47:22.0 208.9 8.94 2007/03/16 14:47:22.0 208.5 8.95 2007/03/16 15:47:22.0 207.9 8.95 2007/03/16 16:47:22.0 207.7 8.96
Accepted Mon file Sections and Parameters
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
- Channel 1 or Kanaal 1 ; Not used
- Channel 2 or Kanaal 2 ; Not used
- Series settings or Instrument info from data header ; Not used
- Channel 1 from data header or Kanaal 1 from data header; Read Parameter Id
- Identification or Identificatie = Parameter Id
- Channel 2 from data header or Kanaal 2 from data header; Read Parameter Id
- Identification or Identificatie = Parameter Id
- Data Data values with the different channels in columns
When the MON file is not in the correct format a warning message is returned.