4.0 Table Definitions & Field Definitions
The table definitions and field definitions for each table are shown below. The column titles “Required 11/14/2012 and before” and “Required 11/15/2012 and after” in the tables below refer to the field “Sampdate”. See HazSite Changes – Compliance Date Change Clarification for details. It is absolutely essential that these table formats are strictly followed.
4.1 The Dataset File (DTST)
The Dataset can be defined as the electronic equivalent of the cover page for the sampling and analytical results that are submitted to the SRP. The DATASET file provides basic information about the sampling event, including site description, investigation phase, consultant, submittal date, and other information. There should be only one record in each Dataset file. The Dataset may represent one or more sampling episodes at a site. For example, the sampling and analytical results of four rounds of quarterly monitoring (at the same site) can be submitted as a single dataset. Valid values are required for several of the DATASET table fields.
4.1a DTST Table Definitions
C = Character, N = Number, D = Date/Time |
4.1b DTST Field Descriptions
Descriptions of the fields are located on a separate page. Please click on the link to take you to DTST Field Descriptions.
4.2 The Sample File (HZSAMPLE)
The second file you will create is the SAMPLE file. The SAMPLE file contains information about each sample collected at a site. The information is roughly equivalent to field notes, and includes: sample number, date, matrix, field identification, location information, etc. There should be one sample record for each sample collected.
A unique sample record is created collectively by the following fields: the SRP ID, the Sample Date, and the Sample Number. Therefore, there can be identical Sample Numbers in a dataset as long as those samples were collected on different dates. Valid values are required for several of the SAMPLE table fields. The required valid values are listed in Appendix 2.
A SRP ID is a unique identifier used to create a unique sample record. Acceptable SRP IDs are:
- Incident Number: An example of the Incident Number is 98-01-31-1422-35. This format represents YY-MM-DD, followed where available by HH-MM-SS where YY = Year, MM = Month, DD = Day, HH = Hours in military time, MM = Minutes, and SS = Seconds. Dashes may be omitted.
- TMS Closure Number :A TMS closure number (ie C98-0001, N98-0001) is acceptable.
- ISRA Number: A former ISRA number, E##### (ie : E99001 or E20040122)
- EPA Number: EPA numbers (ie NJD######### or NJL#########) are acceptable.
- Preferred ID: Sometimes referred to as SRP ID. Excepted formats are 012345 and G000012345. Preferred IDs are always 6 characters or 10 characters long. Preferred IDs that are 10 characters long always begin with a “G”.
The preparer must name the Sample file HZSAMPLE.
4.2a HZSAMPLE Table Definitions
C = Character, N = Number, D = Date/Time |
1. Coordinate data should adhere to be one of the following.
- SP_X, SP_Y.
- LAT_DEGREE, LAT_MINUTE, LAT_SECOND, LON_DEGREE, LON_MINUTE, LON_SECOND.
- LAT_DEGREE, LON_DEGREE as decimal degrees with sufficient decimals and LAT_MINUTE, LAT_SECOND, LON_MINUTE, LON_SECOND set to 0.
- LAT_DEGREE, LON_DEGREE with LAT_MINUTE, LON_MINUTE as decimal degrees with sufficient decimals and LAT_SECOND, LON_SECOND set to 0.
2. Data are required if sampling includes soils.
5. An explanation is required here if the MATRIX and/or SAMPTYPE fields equal 'OTHER'.
6. Data are required if sampling includes Monitoring Wells. 'N/A' is acceptable for potable wells and temporary wells.
7. Data are required if sampling includes Monitoring Wells. 'N/A' is acceptable for potable wells without permit numbers.
8. Data are required if sampling includes Monitoring, Potable or Temporary Wells. 'No Permit' is acceptable for potable wells without permit numbers and temporary wells.
4.2b HZSAMPLE Field Descriptions
Descriptions of the fields are locaed on a seperate page. Please click on the link to take you to HZSAMPLE Field Descriptions.
4.3 The Result File (HZRESULT)
The third file you will create is the RESULT File. The RESULT file includes the results of the analysis of the sample. Fields include the Sample Number, Sample Date, Lab ID, the name of the analyte or parameter, the concentration of the result, QA Qualifier, Method Detection Limit, etc. Valid values are required for several of the RESULT table fields. Some of the required valid value tables are listed in Appendix 3. Each analyte analyzed requires a result record.
LAB NOTES:
- Sample results should not include laboratory generated quality control samples. Examples of laboratory generated quality control samples are shown in Appendix 3.5 of this manual.
- Sample results should not include the concentration of any surrogate standard (sometimes known as a system monitoring compound or a deuterated monitoring compound) or internal standards that might have been added to a normal environmental sample.
- If a sample result must include laboratory generated samples, surrogates standards or internal standards use one of the appropriate RESULTTYPE values listed in Appendix 3 of the EDI manual.
*If a certified lab already completed a results file for you, it can be submitted to SRP as is.
The preparer must name the Result file HZRESULT.
4.3a HZRESULT Table Definitions
C = Character, N = Number, D = Date/Time |
4.3b DTST Field Descriptions
Descriptions of the fields are locaed on a seperate page. Please click on the link to take you to HZRESULT Field Descriptions.
3. These fields must now be filled out for all rows in HZRESULT that are considered ANALYTES (HZRESULT.RESULTTYPE = 'A').
4. Data are required if ANLYS_MTHD = 'TO-15'.
9. Must be filled in if NJDLABCERT is not available.
10. Provide data if available. If there is no data leave the field blank.
11. A non-detect requires that QAQUAL = 'U'.
12. Data are required for tentatively identified compounds and unidentified compounds. If the sample date is November 14, 2012 or earlier, the retention time is still required, but may be entered in the ANALTPARAM or CAS fields.
13. Data are required if the sample has been re-run and diluted for any reason. see DILUT_FAC Definition.
14. Either (MDL) or (both QUANTTYPE and QUANTLEVEL) must be filled out.
|
|