Navigation:  Data Types > Time-series Logger Data > Time-series Logger Data - Manual Import

Logger or other semi-continuous data can be imported using the "Logger Files" Quick Template button under Import.

 

If the file format is recognised by ESdat then the data will be loaded into an import template for users to enter additional information (such as location).  User can then import the data.

 

If a file is selected, and the format not recognised, the data will be loaded into the Template, and the user will need to enter the Sampling Location, and other related data in an area at the top of the template (see below).   Users can click "Cancel" to generate a blank import template into which data can be pasted.

 

If the format of the logger data file isn't recognised (there are literally hunderds of variations) the file contents will be entered in the lower half of the screen, and the user will need to align the data appropriately.  A prompt will help users through this stage.  It will initially look similar to the image below:

 

 

The data will need to be re-arranged as follows.  The image below shows the parameter names and units have been lined up  across the top of the lower section, and extra header data moved to the Event information (ie the top section), or deleted.

 

 

From this point users will need to assign a "ChemCode" to each parameter.  This enables comparisons with trigger levels.  Even if trigger level comparisons are not required a ChemCode is required.  Generally a duplication of the Parameter Name is suitable.  ChemCodes are assigned or added in the normal manner, by clicking on the "Get ChemCodes" button next to the import arrow in Excel.

 

 

Continuous water level (or streamflow) data may be stored either here, or in the water levels (or Surface Water Flow) table.  It is recommended that water level logger data in particular be stored in the water level table as depth-elevation conversions will then be applied if necessary.

 

If you have a large logger program and the logger data format isn't recognised you may wish to:

•Customise the standard tables to optimally fit your requirements  see Customising the ESdat database for more information.

•Write an Excel Macro to align the data correctly.

•Request the logger data format be recognised in the software.  This can be implemented on a time/expenses basis.

•Request a direct data feed from your logger into ESdat be set up.  This requires either specific in-house IT knowledge, or can be done on a consulting basis by ESdat support staff.