Automated Import for logger data is desirable where permanent loggers are in place providing continuous data, such as might occur at a mine site, industrial facility or port.

Due to the variety of loggers and data streams used the automated import of this data to the ESdat database needs to be set up on a case by case basis.

Depending on the requirements of the organisation this may be by directly mapping data from the loggers systems to the "Logger Data" table in ESdat, or a view based on that table, or setting up a stored proceedure to facilitate the import.  Contact EScIS staff if you would like this to be done for you.

This data synchronisation can be set up by some In-house IT staff.  The relevant tables, relationships and considerations are shown in SQL Server Tables for Logger Data.

The following additional points are of note:

•All data in the Logger Data table must be given a ChemCode that is a valid value in the Chemistry Lookup Reference Table.

•All Matrix Type values must be a valid value in the Matrix Types Reference Table.

•The Logger Events table would typically be set up once for a particular logger/location, and the continuous data recorded in the Logger Data table, and given a valid Event ID to match.