3.0 Using the Database Format (.DBF) Option
Refer to Section
8.0, Discussion of Fields in this manual for complete
field descriptions and acceptable entries.
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 via hard copy. 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.
The structure for the Dataset file (DTST.DBF)
is defined in Table 3.1.
KEY: (Mandatory
fields)
|
* |
If not completed, resubmission will
be required.
|
|
NOTE: Exact Field Names and Widths
are needed so that the information can be accurately inserted
into the existing SRP database. If the submitted names or
field widths are not compatible with the SRP database, the
information may not be transferred accurately to the SRP
database, and could result in data loss. In such cases,
the file would be rejected.
The second file you will create is the
SAMPLE file. The Sample file includes the date and location
of the sample and other important information as shown in
the Sample Record Table (Table 3.2, below). Each Sample
Record requires a specific number of fields, a Name for each field, the Field Type (character, date,
or numeric) and the Width of each field.
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.
The structure for the Sample file (HZSAMPLE.DBF)
is defined in Table 3.2 .
KEY: (Mandatory
fields)
|
* |
If not completed, resubmission will
be required.
|
+ |
Either the complete Latitude and
Longitude OR State Plane X, Y Coordinates
must be submitted for each environmental sample
collected. |
|
NOTE: Exact Field Names and Widths
are needed so that the information can be accurately inserted
into the existing SRP database. If the submitted names or
field widths are not compatible with the SRP database, the
information may not be transferred accurately to the SRP
database, and could result in data loss. In such cases,
the file would be rejected.
The third (last) file you will create is
the RESULT File. This file includes the sample date, result
type, and analytical concentrations of the contaminants
detected in the sample and other important information.
Each Result Record requires a specific number of
fields, a Name for each field, the Field Type (character, date, or numeric) and the Width of each
field.
The RESULT file contains the result of
the analysis of the sample. The Result file includes 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. Each compound analyzed for
in each sample collected requires a result record.
The structure for the Result file (HZRESULT.DBF)
is provided in Table 3.3.
TABLE 3.3 – File Structure for
file to be named by submitter as HZRESULT.DBF
KEY: (Mandatory
fields)
|
* |
If not completed, resubmission will
be required.
|
^ |
Either MDL OR Quant Type and Quant Level. |
|
NOTE: Exact Field Names and Widths
are needed so that the information can be accurately inserted
into the existing SRP database. If the submitted names or
field widths are not compatible with the SRP database, the
information may not be transferred accurately to the SRP
database, and could result in data loss. In such cases,
the file would be rejected.
|
Alternate Format of the Entire Guidance Document
Help
for Using Files |