Learn how the ESdat Environmental Data Management System works, its file components, and how it simplifies environmental data workflows.
 
															The purpose of the ESdat Electronic Lab Data Format (ELDF) is to enable transfer of results from a laboratory to ESdat users in a format which allows validation and direct import into ESdat.
Other file formats that facilitate advanced integration of eCOC and eSRN information between the laboratory and ESdat are also available. See LSPECS Integration
ELDF 4 extends ELDF 2e in order to accommodate additional QA information. To upgrade from ELDF2e to ELDF see Converting ELDF 2e to ELDF 4.
The file names are of the format: Project Name as provided by the users; a full stop; a laboratory file identifier; a full stop; the text “ESdatHeader”, “ESdatSample4” or “ESdatChemistry4” as appropriate and the file extension (“.xml” or “.csv” as appropriate). An example of a file set would be
The Header File xml specifications are fully described here.
| Primary Key | Field | Description | Req'd | Data Type | 
|---|---|---|---|---|
| 
													*												 | 
													SampleCode												 | 
													Unique Identifier for each sample *												 | 
													Y												 | 
													Text(40)												 | 
|  | 
													Sampled_Date_Time												 | 
													From COC												 |  | 
													Date with optional time												 | 
|  | 
													Field_ID												 | 
													From COC (Normal samples only)												 |  | 
													Text(40)												 | 
|  | 
													Depth												 | 
													From COC												 |  | 
													Number or Number – (dash) Number												 | 
|  | 
													Matrix_Type												 |  | 
													Y												 | 
													List of Soil, Water, Gas, SoilGas, Other or as provided on the COC												 | 
|  | 
													Sample_Type												 | 
													Description of sample as from the field or a lab QC sample.												 | 
													Y												 | List of : | 
|  | 
													Parent_Sample												 | 
													For Laboratory Duplicates, or Matrix Spike Duplicates give the SampleCode of the parent sample.
For Matrix Spikes give the SampleCode of the applicable non-spiked sample.												 |  | 
													Text(40)												 | 
|  | 
													SDG												 | 
													Sample Delivery Group, Use the COC Number from the COC or if not available use “Lab Name Date Received”.
 Lab QA Samples should be given the same SDG as the field Samples, or the value should be left blank. | 
													Y												 | 
													Text(20)												 | 
|  | 
													Lab_Name												 |  | 
													Y												 | 
													Text(20)												 | 
|  | 
													Lab_SampleID												 | 
													Laboratory Sample ID												 | 
													Y												 | 
													Text(20)												 | 
|  | 
													Lab_Comments												 | 
													Lab Comments specific to a sample												 | 
													N												 | 
													Text(255)												 | 
|  | 
													Lab_Report_Number												 |  | 
													Y												 | 
													Text(20)												 | 
| Primary Key | Field | Description | Req'd | Data Type | |||||
|---|---|---|---|---|---|---|---|---|---|
| 
													*												 | 
													SampleCode												 | 
													Unique Identifier for each sample (as per Sample File)												 | 
													Y												 | 
													Text(40)												 | 
													*												 | 
													ChemCode												 | 
													Unique Identifier for each analyte (eg. CAS number)												 | 
													Y												 | 
													Text(20)												 | 
|  | 
													OriginalChemName												 | 
													The name for the Analyte as given in the laboratories Certificate of Analysis												 | 
													Y												 | 
													Text(50)												 | |||||
|  | 
													Prefix												 |  | 
													if below detection limit												 | “<” or “>” | |||||
|  | 
													Result												 | 
													The reported result applicable for the result unit.												 | 
													Y												 | 
													Number. Text is permitted for asbestos analyses or other specific results.												 | |||||
|  | 
													Result_Unit												 | 
													Should use SI Units where possible. A dash should be specified where units are not applicable, such as for pH or text results.												 | 
													Y												 | 
													Text(15)												 | |||||
| 
													*												 | 
													Total_or_Filtered												 | 
													Either Total or Filtered, if blank will default to T.												 |  | List of | |||||
| 
													*												 | 
													Result_Type												 |  | 
													Y												 | Restricted to: | |||||
|  | 
													Method_Type												 |  | 
													Y												 | Text(50): Etc as indicated on the CoC. If a suitable value isn’t available then the name of the Method is most suitable, ie for the method “EG005T: Total Metals by ICP-AES”, the Name “Total Metals by ICP-AES” or similar would be most suitable. | |||||
| 
													*												 | 
													Method_Name												 | 
													Method or Test Code, eg SW-846 or 8260B.												 | 
													Y												 | 
													Text(70)												 | |||||
|  | 
													Extraction_Method  												 | 
													Method used for extraction prior to analysis												 | 
													If possible												 | 
													Text(70)												 | |||||
|  | 
													Extraction_Date												 | 
													Date extracted												 | 
													if possible												 | 
													Date												 | |||||
|  | 
													Analysed_Date												 | 
														
Date analyzed												 | 
													if possible												 | 
													Date												 | |||||
| 
													*												 | 
													Lab_Analysis_ID												 | 
													A unique value per analysis run included in the report.												 | 
													Y												 | 
													Text(20)												 | |||||
|  | 
													Lab_Preperation_Batch_ID												 | 
													A unique value per sample preparation batch.												 | 
													Y												 | 
													Text(20)												 | |||||
|  | 
													Lab_Analysis_Batch_ID												 | 
													A unique value per analysis batch.												 | 
													Y												 | 
													Text(20)												 | |||||
|  | 
													EQL												 | 
													Quantitation Limit, reported in the units specified in the Detection_Limit_Units column.												 | 
													Y												 | 
													Number												 | |||||
|  | 
													RDL												 | 
													Reportable Detection Limit, reported in the units specified in the Detection_Limit_Units column.												 | 
													N												 | 
													Number												 | |||||
|  | 
													MDL												 | 
													Method Detection Limit, reported in the units specified in the Detection_Limit_Units column.												 | 
													N												 | 
													Number												 | |||||
|  | 
													ODL												 | 
													Other Detection Limit, for use if required in contract or client specific requirements such as the US Defense “Limit of Detection”.
Reported in the units specified in the Detection_Limit_Units column.												 | 
													N												 | 
													Number												 | |||||
|  | 
													Detection_Limit_Units												 | 
													Units used for EQL, RDL, MDL and any other Detection/Quantitation Limit values. The Result can be reported in it’s own unit (the Result_Unit). 												 | 
													Y												 | 
													Text(15)												 | |||||
|  | 
													Lab_Comments												 | 
													Lab Comments specific to a result.												 | 
													N												 | 
													Text(255)												 | |||||
|  | 
													Lab_Qualifier*												 |  | 
													N												 | 
													Text **												 | |||||
|  | 
													UCL												 | 
													Upper Confidence Limit used for QA recoveries												 | 
													N												 | 
													Number												 | |||||
|  | 
													LCL												 | 
													Lower Confidence Limit used for QA recoveries												 | 
													N												 | 
													Number												 | |||||
|  | 
													Dilution_Factor												 |  | 
													N												 | 
													Number												 | |||||
|  | 
													Spike_Concentration												 |  | 
													N												 | 
													Number												 | |||||
|  | 
													Spike_Measurement												 | 
													The measured concentration of the spike or surrogate.												 | 
													N												 | 
													Number												 | |||||
|  | 
													Spike_Units												 | 
													Units used for Spike Concentration and Measurement												 | 
													N												 | 
													Text(15)												 | |||||
|  | 
													Text_Result												 | 
													Used for Non-Numeric Results, or Text accompanying a Result (such as Radiological Uncertainty)												 | 
													N												 | 
													Text(15)												 | 
The fields and data in the csv files may optionally be surrounded by quotation marks.
Leaching test results are not given a separate SampleCode, (i.e., are not treated as a separate sample). Results are indicated in the chemistry file and are identified in the Result_Type field.
Dates should be in the format dd mmm yyyy (e.g., 3 Jan 2007). This avoids confusion between users with different regional settings. If time is included, it should be hh:mm AM/PM.
Tentatively Identified Compounds should be reported with the ChemCode of the TIC and be identified as such in the Comments field of the chemistry file. If the laboratory is using lab qualifiers a suitable lab qualifier should be reported.
In some use cases laboratory results are not numeric but are text (such as some asbestos results), or a combination of numeric and text.
Result must be numeric for graphing or similar purposes.   Text_Result is to be used for text results, or textual parts of the Result.  Where the result is just text, with no numeric result a value of -997 should be reported in the Result, and the text should be reported in Text_Result.
Radiological results are sometimes reported with a result and an uncertainty such as 10±0.01.
In this case the numerical result value should be reported in the Result, and the uncertainty should be reported as "± XXXX" in the Text Result.  The result and the uncertainty should be in the same unit as reported in the Result_Unit.
The EQL and the detection limit units should remain as normal where available, for example, 1 g/kg.
Aborted analyses can be reported, a value of -999 should be entered as a result, and a comment entered into the comments field in the Results file.
The Sample Type should be reported as MS.
The SampleCode of the pre-spike sample is indicated in the Parent Sample Column.
The results should be reported as per all Spike results, i.e.:
The % recovery should be reported in the Result column with Result Units of '%' and Result Type specified as MS. The Spike Concentration should be reported in the Spike_Concentration column and the Spike Measurement reported in the Spike_Measurement column. The Spike units should be reported in the Spike_Units column.
The Sample Type should be reported as LCS, CRM, or SRM as appropriate.
The results should be reported as per all Spike results, i.e.:
The % recovery should be reported in the Result column with Result Units of '%' and Result Type specified as MS. The Spike Concentration should be reported in the Spike_Concentration column and the Spike Measurement reported in the Spike_Measurement column. The Spike units should be reported in the Spike_Units column.
The Sample Type should be reported as MS_D or LCS_D as appropriate.
The SampleCode of the primary matrix spike sample is indicated in the Parent Sample column.
The results should be reported as per all Spike results, i.e.:
The % recovery should be reported in the Result column with Result Units of '%' and Result Type specified as MS. The spike concentration should be reported in the Spike_Concentration column and the spike measurement reported in the Spike_Measurement column. The spike units should be reported in the Spike_Units column.
The Sample Type should be reported as Trip_B, MB or SB as appropriate.
The results should be reported as normally measured concentrations.
The Sample Type should be reported as Trip_S.
The results should be reported as per all Spike results, i.e.:
The % recovery should be reported in the Result column with Result Units of '%' and Result Type specified as MS. The Spike Concentration should be reported in the Spike_Concentration column and the Spike Measurement reported in the Spike_Measurement column. The Spike units should be reported in the Spike_Units column.
If the lab duplicate or matrix spike used for analysis batch QC is on a field sample from another client, the QC results on the parent and duplicate or spiked sample should still be reported.
The field ID and depth and any client-provided information for these samples should not be reported.
The Sample Type of the Parent Sample should be set to NCP (Non-Client Parent).
The Sample Type should be reported as Lab_D or Lab_T for laboratory duplicates or triplicates.
The SampleCode of the parent sample should be reported in the Parent_Sample column.
The results should be reported as normally measured concentrations.
Copyright 2005
The ESdat ELDF Format is a continuously maintained and evolving proprietary format for receipt of laboratory results by organizations with an active ESdat maintenance agreement, account, or subscription and the subsequent processing, storage, or other use without limitation.
Copyright in the ESdat ELDF Format and the reference lists used in conjunction with the Format reside with EarthScience Information Systems Pty Ltd.
Third-party software or other organizations wishing to use the ESdat ELDF Format for other commercial or bespoke software should contact EScIS to arrange a license agreement.