Electronic Data
Deliverable (EDD)
Comprehensive
Specification Manual 2.0
-:H;
•"'- ',
i.
%i
;
^-&
•
U.S. Environmental Protection Agency
Region 2, Superfund 290 Broadway
New York, NY
May 2011
-------
THIS PAGE LEFT BLANK INTENTIONALLY
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 2 Environmental Protection Agency
-------
ACKNOWLEDGEMENTS
This document was originally prepared for EPA Region 5 by the John A. Volpe National Transportation
Systems Center (Volpe Center). This document was reviewed and edited by David Wilson and Mary
Tierney of EPA Region 5; William Halloran and Joseph Monaghan of the Volpe Center; and John
Hennessy and Ellen Baptiste-Carpenter of Battelle Laboratories, Inc. Other technical reviewers from
EPA include Patricia Scott, Chemist, EPA Region 5; Douglas Yeskis, Geologist, EPA Region 5; Luanne
Vanderpool, Geologist, EPA Region 5; Anthony Kahaly, EPA Region 5, RCRA Division; and Andy
Grassland, Hydrogeologist, EPA, Region 2. Other reviewers include Steve Losier of the Volpe Center;
Janet Magurn, Scot Weaver and Dave Abercrombie of EarthSoft, Inc.; Rosanna Buhl of Battelle
Laboratories, Inc.; and Izak Maitin of the New Jersey Department of Environmental Protection.
EarthSoft Inc. developed the Electronic Data Processor (EDP) and reviewed the EDD format to assure its
technical accuracy.
This documentation was reviewed and updated by Diann Cox-Tramel and Robert M. Alvey, Region 2 and
updated May 2011 to meet the standards and requirements of EPA Region 2.
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 i Environmental Protection Agency
-------
DISCLAIMER OF ENDORSEMENT
Reference herein to any specific commercial products, process, or service by trade name, trademark,
manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or
favoring by the United States Government. The views and opinions of authors expressed herein do not
necessarily state or reflect those of the United States Government, and shall not be used for advertising or
product endorsement purposes.
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 ii Environmental Protection Agency
-------
EXECUTIVE SUMMARY
The purpose of this specification manual is to provide detailed instructions on how to report
environmental data electronically to the United States Environmental Protection Agency (EPA) Region 2.
The types of data can be reported electronically include, for example, data generated during site
characterization and investigation phases, data recorded when installing monitoring wells, and monitoring
data that is routinely collected from a variety of media. This manual describes the procedural and
formatting requirements you need to know to submit your Electronic Data Deliverable (EDD) to the EPA
Region 2 Superfund Division.
This EDD Comprehensive Specification manual describes the requirements for reporting all current and
future environmental data to EPA Region 2. EPA recognizes that some information about data collected
in the past may not be readily available and, by reducing the requirements for electronic basic data, is
endeavoring to strike a balance between minimizing the amount of effort involved in inputting
information and maximizing the ability to document remedy progress. Environmental data collected and
analyzed prior to the initial use of this EDD Comprehensive specification manual should be reported
using the EPA Region 2 "Basic Manual for Historic Electronic Data". The reporting requirements of the
"Basic Manual for Historic Electronic Data" are a subset of this comprehensive EDD Comprehensive
specification manual.
The EPA Region 2 EDD is comprised of five groups: Initial, Field, Vapor Intrusion, Chemistry, and
Basic. The Initial EDD files refer to an electronic base map of the site property, one file containing
general information about the site and about the point of contact for the EDD, and a file containing data
pertaining to site sampling locations. The Initial EDD files are only resubmitted if information, such as
the point of contact, changes. The three initial files are:
Initial - (only submit once unless changes are needed)
• Base Map (electronic map of the site property boundaries in *.dxf format)
• Data Provider (point of contact for EDD and file providing the information)
• Site (general information about the site)
• Location (information regarding the sampling locations)
In most cases, the vast majority of the electronic data submitted over the life of the project, and that will
be submitted on a reoccurring, routine basis, will be chemistry data.
Field
The Field EDD files contain data regarding drilling activities, lithology, geologic sampling, well
construction, down hole point data, and water table levels. The seven Geology EDD files are the:
. Drilling Activity (information about drilling activities)
. Lithology (lithology information)
• Well (monitoring well information)
• Well Construction (well construction details)
• Geology Sample (geology sample data)
• Water Table (water table data collected during drilling)
. Down Hole Point (down-hole logging data)
• Soil Gas ( soil gas survey data)
• Water Level (information regarding groundwater level measurements)
. Extraction/Injection Well (information about extraction and/or injection wells)
. Field Results (information of field results)
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 iii Environmental Protection Agency
-------
Vapor Intrusion
• Building Address (information of the building address)
• Building
• Task Parameters
• Samples
. Test Result QC
• Batches
Chemistry
The Chemistry EDD files contain data related to chemistry field measurements, sample collection
information, sample tests and result QC. The Chemistry EDD files are the:
• Sample (information about sample collection)
• Sample Parameter (information about the parameter data associated with a sample sent to a lab)
• Test Result QC (information about the analytical test performed on samples with quality control
data elements)
• Batch (test batch information)
Basic Submittals
The Basic EDD files contain historical operation and maintenance (O&M) data. The EDD files are the:
• Location (information about sampling locations from historical data)
• Water Level (information regarding groundwater level measurements)
. Chemistry Sample (information about sample collection)
• Geology (information about geology data)
Of the files listed above, the Chemistry and Field files that most data providers will submit will be the
Well, Water Level, Extraction Injection Wells, Sample, Test/Result QC files. The Test Result with QC
and Batch files will only be submitted in those rare cases where EPA requires QA/QC data in electronic
format. The Extraction/Injection Well file will only need to be submitted for sites with extraction or
injection wells.
The process for creating initial, chemistry and field EDDs are shown in Figures E-l and E-2, respectively.
The process begins by identifying the software tool that will be used. . Many software tools, such as text
editors, word processors, spreadsheets, and databases, are capable of creating EDDs. Because
spreadsheets and databases are designed to enter and manage data, however, they are generally preferred
for creating EDDs. The production of the data tables will normally be a collaborative effort between
laboratories and environmental contractors. The laboratories will typically produce the test/result tables
while the contractors normally will produce all of the other tables.
As shown in Figures E-1 and E-2, decision points are included in the EDD creation process to ensure that
Initial EDD files have been submitted for a site, as well as to prevent redundancy when getting ready to
submit chemistry or field EDDs. For example, one of the Initial EDDs called the SITE file, which
contains data describing the site and site contact information, should generally only be reported once
(unless, as previously noted, a change occurs). Similarly, another Initial EDD file, the Location file,
which contains locational data, typically only needs to be reported once. The only time a Location EDD
file would be resubmitted is if the data changed in some way. For example, if settling occurs at a site over
time, a resurvey of site monitoring wells may be warranted. If the survey results show changes in the
elevations of the monitoring wells, the Location file would have to be resubmitted.
The final step before submitting an EDD to EPA Region 2 is to check it using the Electronic Data
Processor (EDP) software application that is currently provided on the EPA Region 2 website (located at
http://www.epa.gov/region02/superfund/medd.htm). This software application will identify any
formatting errors in the files that must be corrected prior to submitting the EDD.
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 iv Environmental Protection Agency
-------
Figure E-l Process flow diagram for the creation and checking of Initial, Field and Chemistry
EDO files
Select a Data Entry
Product
Use the file
EDO Region 2 EDO Template
http://www.epa.qov/reqion02/s
Define the columns in the
selected software according to
the tables in sections 3 & 4
uperfund/medd.htm
Enter Site Data
(Initial EDO File)
Has site ever been
reported?
Enter Location Data
(Initial EDO File)
Has location ever
been reported?
Enter Extraction
-Injection Data
(if applicable)
Enter Water
Level Data
Enter Sample
Data
Has sample ever
been reported?
Enter
Test/Result
Data
Send EDO
Files to
Region 2
Check with EDP and Correct Errors
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 v
United States
Environmental Protection Agency
-------
Figure E-2 Process flow diagram for the creation and checking of Initial and Field EDD files
Select a Data Entry
Product
Access or
Excel?
Define the columns in the
selected software
according to tables in
sections 3 & 5
Use the file
EDD Reaion 2
temnlate
Enter Site Data
(Initial EDD File)
Has site ever
been reported?
Has location
ever been reported?
Enter Location Data
(Initial EDD File)
Enter Drilling
Activity Data
Enter Lithology
Data
Enter Well
Data
Enter Well
Construction Data
Enter Water Level
Data
Enter Water Table
Data
1
Enter Down Hole
Point Data
Check with EDP
and Correct Errors
H
Send EDD Files
to Region 2
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 vi
United States
Environmental Protection Agency
-------
THIS PAGE LEFT BLANK INTENTIONALLY
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 vii Environmental Protection Agency
-------
TABLE OF CONTENTS
EXECUTIVE SUMMARY iii
1. INTRODUCTION TO THE EPA REGION 2 ELECTRONIC DATA DELIVERABLE (EDO) 1
2. GENERAL EDO REPORTING REQUIREMENTS 3
2.1 File Formats 3
2.2 Initial Data Submittals 3
2.3 Chemistry Data Submittals 4
2.4 Field Data Submittals 5
2.5 Vapor Intrusion Data Submittals 7
2.6 File Naming Convention 8
2.7 Data Integrity Rules 10
2.8 Definition of a Facility, Site, and Location 13
2.9 Reporting Null Values 13
2.10 Valid Values 14
2.11 Reporting Re-Tests 15
2.12 Reporting Non-Detects 15
2.13 Reporting Tentatively Identified Compounds 16
2.14 Data Types 16
2.15 Data Entry Tools Provided to Create the EDD Files 16
2.16 Using the Electronic Data Processor to Check EDD Formatting 18
2.17 Submitting Your EDD to EPA 18
2.18 Examples of Initial, Chemistry, and Field EDD Files 20
3. FORMATS FOR INITIAL FILES 27
3.1 Site Base Maps in the file section 27
3.2. Data Provider 28
3.3 SITE EDD File 28
3.4 Location EDD File 29
4. FORMATS FOR CHEMISTRY FILES 35
4.1 Chemistry Sample EDD File 35
4.2 Chemistry Sample Parameter EDD Files 39
4.3 Chemistry Test/Result with QC Data EDD File 39
4.4 Chemistry Batch Data EDD File 46
5. FORMATS FOR FIELD FILES 47
5.1 Drill Activity EDD File 47
5.2LithologyEDDFile 48
5.3 Well EDD File 50
5.4 Well Construction EDD File 52
5.5 Geology Samples EDD File 53
5.6 Water Table EDD Files 56
5.7 Geology Down Hole Point Data EDD File 57
5.8 Soil Gas Data EDD File 58
5.9 Water Level 59
5.10 Extraction - Injection Well EDD File 62
5.11 Field Parameters 64
6. FORMATS FOR VAPOR INTRUSION FILES 66
6.1 Vapor Intrusion Building Address EDD File 66
6.2 Vapor Intrusion Building EDD Files 66
6.3 Vapor Intrusion Task Parameter EDD File 68
6.4 Vapor Intrusion Sample EDD file 68
6.5 Vapor Intrusion Test Result QC 69
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 viii Environmental Protection Agency
-------
6.6 Vapor Intrusion Batch EDD File 77
7. TECHNICAL SUPPORT 79
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 ix Environmental Protection Agency
-------
LIST OF TABLES
Table 2-1 General information on the files that comprise the Initial EDD 3
Table 2-2 General information on the files that comprise the Chemistry EDD 4
Table 2-3 General information on the files that comprise the Field EDD 5
Table 2-4 General information on the files that comprise the Vapor Intrusion EDD 7
Table 2-5 EDD File Naming Formats 10
Table 2-6 Examples of how to report null values 13
Table 2-7 Cross-reference between the valid value tables in appendix and the EDD files 14
Table 2-8 Example of reporting re-tests 15
Table 2-9 Example of reporting non-detects 15
Table 2-10 Example nomenclature for TIC reporting 16
Table 2-11 Datatype descriptions 16
Table 2-12 Instructions for producing tab-delimited text files from some software packages 17
Table 3-1 Files 27
Table 3-2 Data Provider File Structure 28
Table 3-3 SITE data file structure 28
Table 3-4 Location Data File Structure 31
Table 4-1 Chemistry sample file data structure 35
Table 4-2 Chemistry Sample Parameter file data structure 39
Table 4-3 Chemistry test/results with QC data file structure 40
Table 4-4 Chemistry batch file data structure 46
Table 5-1 Drill activity file data structure 47
Table 5-2 Lithology file data structure 48
Table 5-3 Well file data structure 50
Table 5-4 Well construction file data structure 52
Table 5-5 Geology samples file data structure 53
Table 5-6 Water table file data structure 56
Table 5-7 Geology Down Hole Point File Data Structure 58
Table 5-8 Example of down hole point data file 58
Table 5-9 Soil Gas Survey file data structure 58
Table 5-10 Water Level file data structure 59
Table 5-11 Extraction-Injection Well file data structure 62
Table 5-12 Field Results file data structure 64
Table 6-1 Vapor Intrusion Building Address data structure 66
Table 6-2 Vapor Intrusion Building data structure 66
Table 6-3 Vapor Intrusion Task Parameter data structure 68
Table 6-4 Vapor Intrusion Samples data structure 68
Table 6-5 Vapor Intrusion Test Result QC file data structure 70
Table 6-6 Vapor Intrusion Batches file data structure 77
LIST OF FIGURES
Figure E-l Process flow diagram for the creation and checking of Initial, Field and Chemistry EDD files v
Figure E-2 Process flow diagram for the creation and checking of Initial and Field EDD files vi
Figure 2-1 Relationships between chemistry file data structures 12
Figure 2-2 Facility component definitions 13
Figure 2-3. Example Initial EDD ready for conversion to text file 20
Figure 2-4. Example Chemistry EDD ready for conversion to text file 20
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 x Environmental Protection Agency
-------
Figure 2-5. Examples of QC data fields in a Chemistry EDD 21
Figure 2-5. Examples of QC data fields ina Chemistry EDD (continued) 23
Figure 2-6. Example Field EDD ready for conversion to text file 24
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 xi Environmental Protection Agency
-------
THIS PAGE LEFT BLANK INTENTIONALLY
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 xii Environmental Protection Agency
-------
1. INTRODUCTION TO THE EPA REGION 2 ELECTRONIC DATA DELIVERABLE (EDO)
The EPA Region 2 Superfund Division has developed an electronic data management system to improve
how environmental data from Superfund sites are acquired and managed. The system will accelerate the
review of environmental data submittals, improve service to the regulated community, and enhance the
protection of the environment and the public. A vital element in the electronic transfer of environmental
data is the submittal of data in a standardized, "computer-friendly" format. The specifications and
formatting requirements for the EPA Region 2 EDD were developed to facilitate the transfer of data from
data providers to the EPA.
NOTE: This EDD Comprehensive Specification manual describes the requirements for reporting all
current and future environmental data to EPA Region 2. Environmental data collected and analyzed
prior to the initial use of this EDD specification manual should be reported using the EPA Region 2
"Basic Manual for Electronic Data". EPA recognizes that some information about data collected in the
past may not be readily available and, by reducing the requirements for electronic historical data, is
endeavoring to strike a balance between minimizing the amount of effort involved in inputting
information and maximizing the ability to document remedy progress.
The EPA Region 2 EDD is in part based on standard EDDs used in applications developed by EarthSoft,
Inc. However, the format is designed to be software-independent and easy to achieve. Any spreadsheet,
database, or text editor can be used to create the EDD files. Examples of applications that can be used to
create Region 2 EDDs include Access, FoxPro®, Excel, Quattro®, Lotus® 1-2-3®, and Notepad.
Basically, the EDD is a series of files used to report data. For example, one file is used to report location
data while another is used to report samples collected at a location. Multiple files are used to eliminate
the need to report redundant data. For example, the data for a location (e.g., coordinates and elevations)
are reported once in the location (LOC) file. Many years of sampling and analytical data may be reported
for that location without having to submit the LOC file again.
This specification manual includes examples of EDD files populated with data. In addition, several EDD
templates are currently available on the EPA Region 2 E-Data website
(http://www.epa.gov/region02/superfund/medd.htm') for loading data into the EDD format. The website
also contains a no-cost software program, the Electronic Data Processor (EDP) that needs to be used to
check EDD files before they are submitted to EPA Region 2. The EDP is a single application that checks
all EDD files and provides a much easier user interface for identifying and correcting errors.
This EDD Comprehensive Specification Manual discusses EDD submittals in five separate sections:
• General reporting requirements are discussed in Section 2.
• The Initial file structures (i.e., base map, site, data provider and location) are defined in Section 3.
These files must be submitted prior to, or in conjunction with, the first Chemistry or Geology EDD
submittals.
• The Chemistry file structures are defined in Section 4. In most cases, chemistry data accounts for
the majority of data that is reported.
• The Field file structures are defined in Section 5
• The Vapor Intrusion file structures are defined in Section 6.
• The Valid Values Reference Manual contains tables that list valid values for all data fields.
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 1 Environmental Protection Agency
-------
Each file must be reported exactly as defined in these sections. Any deviations will result in loading
errors.
EPA Region 2 expects all fields referred to as "Required" or "If available" to be filled in. If data for
fields referred to as "If available" or "If applicable" are not available or applicable, respectively, a
description of why these fields are not available or applicable should be included in the cover letter that
accompanies the EDD submittal. Data fields indicated as "Reserved for future use" should not be
reported. These fields were only included so that other EPA regions or states could use the same EDD
but have slightly different data type requirements.
Currently, EPA is working to finalize EDD requirements that would be national standards for Superfund
data for all 10 EPA Regional offices. When this national Superfund EDD is finalized, data providers who
have already begun submitting data according to the EPA Region 2 format will be given time to transition
to any national format changes.
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 2 Environmental Protection Agency
-------
2. GENERAL EDO REPORTING REQUIREMENTS
2.1 File Formats
With the exception of the electronic base map, all data from the EPA Region 2 data providers must be
reported as text files. Each data field must be separated either by tabs (tab-delimited) (indicated by the
suffix "txt" on the file name) or comma-delimited (indicated by the suffix "csv" on the file name). One
other option is to enclose each field in double quotation marks (") (indicated by the suffix "txt" on the file
name). However, because using double quotation marks to delineate fields is typically more time
consuming (unless the data are already in this format), it is anticipated that this method will not be widely
used. Data fields containing no information should not be simply omitted. Instead they should be
represented by the delimiter of choice, e.g., by two tabs in tab-delimited files or two commas in comma-
delimited files (see example in Section 2.8). The maximum length of each text field is indicated in
parentheses in the EDD tables shown in Sections 3, 4, and 5. If the information is less than the maximum
length, there is no need to add spaces to the record to ensure that all spaces are used. Maximum length
requirements imply that the field can be no longer than the specified number of characters. However, it is
completely acceptable to fill the field with fewer characters than the maximum number. Each record ~
which is the term used for each line of information ~ must be terminated with a carriage return/line feed
(created by pressing the "Enter "key in a text editor). Guidance on creating text files can be found in
Section 2.14.
2.2 Initial Data Submittals
The initial data submittal consists of a site base map and three data files: the Site (Site) file, Data Provider
(DataProvider) and the Location (Location) file including facility center point in latitude longitude
coordinate. Initial submittals provide information pertaining to the site, the site EDD contact, and site
sampling locations. The base map, Site file, data provider and Location file generally only need to be
submitted once at the beginning of the project. These files only need to be resubmitted if any changes
occur. Examples of changes that would require resubmittal include changes in site contact information or
location data that changes after being resurveyed. New sampling locations established after the initial
Location file submittal will require a new submittal with data only pertaining to the new locations. Table
2-1 provides general information on the Initial EDD files. Detailed instructions for creating the Initial
EDD files are provided in Section 3, "Formats for Initial Files". Instructions for submitting your EDDs to
EPA Region 2 are presented in Section 2.16.
Table 2-1 General information on the files that comprise the Initial EDD
File Type
Base Map
or any
cover letter
or PDF file
of the Base
Map, any
image files
Data
Provider
File Name
SiteName.dxf ,
or PDF, or doc
SiteNameDate.
EPAID.
DataProvider v3
.txt (or csv)
Created By
Data
provider
Data
Provider
Contents
Basemap of site.
Information about the
data provider
What makes a
row of data
unique?
Not applicable
Not applicable
Dependence of other
files on these data
Not applicable.
Not applicable
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 3
United States
Environmental Protection Agency
-------
File Type
Site
(Section 3.3)
Location
(Section 3.4)
File Name
SiteNameDate.
EPAID.
Site_v3.
txt (or csv)
SiteNameDate.
EPAID.
Location_v3.
txt (or csv)
Created By
Data
provider
Data
provider's
surveyor
Contents
One-time definition of
site including EPA
Region 2 data
providers' contact
information.
One entry for each
location on a site
including a facility
center point. Contains
elevation, coordinate
and general locational
data. Facility center
point is required for the
initial submittal. Data
should only be reported
once for a location.
What makes a
row of data
unique?
site_code
sys_loc_code
Dependence of other
files on these data
The location file
cannot be loaded
without properly
referenced sites
(site_code).
Sample, water levels,
field measurements,
and extraction well
data can only be
reported for locations
that are defined in this
file.
2.3 Chemistry Data Submittals
Chemistry EDDs are submitted after each round of sampling and include the following types of files:
chemistry sample information (Sample), sample Parameter (Sample Parameter), test/results with QC (Test
Result QC), batch information (Batch).
Table 2-2 provides general information on the files that make up the Chemistry EDD. Detailed
instructions for creating the Chemistry EDD files are provided in Section 4, "Formats for Chemistry
Files". Instructions for submitting your EDDs to EPA Region 2 are presented in Section 2.16.
Table 2-2 General information on the files that comprise the Chemistry EDD
File Type
Chemistry
Sample
(Section 4.1)
Chemistry
Sample
Parameter
(Section 4.2)
File Name
SiteNameDate.
EPAID.Sample_v3.
txt (or csv)
SiteNameDate. EPAI
D. SampleParameter_
v3.txt (or csv)
Created
By
Data
provider's
field
sampling
team(s)
Data
provider's
field
sampling
team (s)
Contents
One row for
each sample
collected at the
site.
Parameter data
associated with
a sample sent to
a lab
What makes a row
of data unique?
sys_sample_code
Sys_sample_code
Dependence of
other files on
these data
Tests/results QC
and batch data can
only be reported
for samples that
are defined in this
file.
None
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 4
United States
Environmental Protection Agency
-------
Table 2-2 General information on the files that comprise the Chemistry EDD
File Type
Chemistry
Test/ Result
withQC
Data
(Section 4.3)
Batch
(Section 4.4)
File Name
SiteNameDate.
EPAID.TestResultQC
_v3.txt (or csv)
SiteNameDate.
EPAID.Batch_v3.
txt (or csv)
Created
By
Data
provider's
contractor
lab(s)
Data
provider's
contractor
lab(s)
Contents
Test/Result file
with additional
fields for QC
data.
Data that
relates
laboratory
quality control
samples with
field samples
that were
processed and
analyzed
together.
What makes a row
of data unique?
sys_sample_code
lab_anl_method_
name
analysis_date
analysis_time
total_or_dissolved
test_type
cas_rn
sys_sample_code
lab_anl_method_
name
analysis_date
analysis_time
total_or_dissolved
test_type
test_batch_type
Dependence of
other files on
these data
None.
None.
2.4 Field Data Submittals
Field EDD submittals contain data obtained during subsurface investigations at the site. When initially
submitting the Field EDD, all field EDD files for which information is available should be submitted.
The Field EDD includes files for Drilling Activity (DrillActivity), lithology data (Lithology), general well
information (WEL), well construction information (WellConstruction), geology sample data
(GeologySamples), general information about the water table (WaterTable), down-hole point data
(DownholePoint), soil gas survey data (SoilGas), water table levels (WaterLevel), extraction and injection
well (ExtractionlnjectionWells), and Field Results (FieldResuits). Unlike the Chemistry EDD, where
submittals are typically submitted on a cyclic basis, in most cases the Geology EDD is submitted only
once. Additional Geology EDDs are submitted only if new geology data are collected.
Sites reporting data from monitoring wells installed or from geology-related activities completed more
than one year prior to the date of data submittal are not required to submit the Field EDD files - unless
the monitoring wells are being used for operation and maintenance (O&M) monitoring. . However, for
all newly installed monitoring wells or current geology data collection efforts (i.e., within one year from
the date of data submittal), data providers must submit all applicable Field files as detailed in Section 5.
Table 2-3 provides general information on the files that make up the Field EDD. Detailed instructions for
creating the Field EDD files are provided in Section 5, "Formats for Field Files". Instructions for
submitting your EDDs to EPA Region 2 are presented in Section 2.16.
Table 2-3 General information on the files that comprise the Field EDD
File Type
File Name
Created By
Contents
What makes a row
of data unique?
Dependence of
other files on
these data
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 5
United States
Environmental Protection Agency
-------
File Type
Drilling
Activity
(Section 5.1)
Lithology
(Section 5.2)
Well
(Section 5.3)
Well
Construction
(Section 5.4)
Geology
Samples
(Section 5.5)
Water
Table
(Section 5.6)
Down Hole
Point (CPT)
Data
(Section 5.7)
Soil Gas
Water Level
(Section 5.9)
Extraction-
Injection Well
(Section 5. 10)
File Name
SiteNameDate.
EPAID.
DrillActivity_v3.
txt (or csv)
SiteNameDate.
EPAID .Lithology _v3
.txt (or csv)
SiteNameDate.
EPAID.WEL_v3.
txt (or csv)
SiteNameDate.
EPAID.
WellConstruction_v3
.txt (or csv)
SiteNameDate.
EPAID.
Geology Sample_v3 .
txt (or csv)
SiteNameDate.
EPAID.
WaterTable_v3.
txt (or csv)
SiteNameDate.
EPAID.
DownholePoint_v3 .
txt (or csv)
SiteNameDate.
EPAID.
SoilGas_v3.
Txt (or csv)
SiteNameDate.
EPAID.WaterLevel_
v3.txt (or csv)
SiteNameDate.
EPAID.
Extractionlnj ectionW
ells_v3.
Txt (or csv)
Created By
Data
provider's
geologist
Data
provider's
geologist
Data
provider's
geologist
Data
provider's
geologist
Data
provider's
geologist or
laboratory
Data
provider's
geologist
Data
provider's
geologist
Data
Provider's
geologist
Data
provider's
field
sampling
team(s)
Data
provider's
field
sampling
team(s)
Contents
General Information
regarding soil
borings.
Lithology data for a
borehole.
General information
regarding wells.
Well construction
details recorded
during well
construction.
Results for
geological, physical
properties of
samples.
General information
pertaining to water
table.
Results of all down
hole logging such as
CPT, resistivity, or
other geophysical
logs.
Results of
information
regarding the soil
gas
Groundwater level
data for monitoring
wells
Data that relates to
any extraction wells
that are operating as
part of the remedial
action.
What makes a row
of data unique?
sys_loc_code
event
sys_loc_code
start_depth
sys_loc_code
sys_loc_code
segment_type
start_depth
material_type_
code
Geo_sample_code
sys_loc_code
type
sys_loc_code
depth
param
sys_loc_code
sys_loc_code
measurement_date
measurement_time
sys_loc_code
start_measurement_d
ate
start_measurement_ti
me
Dependence of
other files on
these data
None.
None.
Well
construction
and water level
data can only
be reported for
wells that are
defined in this
file.
None.
None.
None.
None.
None
None.
None.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 6
United States
Environmental Protection Agency
-------
File Type
Field Results
(Section 5. 11)
File Name
SiteNameDate.EPAI
D.FieldResults_v3.T
xt (or csv)
Created By
Data
provider's
field
sampling
team (s)
Contents
Data that relates to
collection of field
parameters or field
results data.
What makes a row
of data unique?
data_provider
sys_sample_code
field_parameter
result_date
result_time
result_unit
sample_matrix_code
reportable_result
value type
Dependence of
other files on
these data
None
2.5 Vapor Intrusion Data Submittals
Vapor Intrusion EDD submittals contain data of sampling taken inside of the contaminated sites or
buildings. The sample (VI_Sample), Test Result QC (VI_TestResultQC), and Batch (VI_Batch) data are
only for Vapor Intrusion data. If the data is collected for Vapor Intrusion, then it is not required to submit
the same Sample (Sample), Test Result QC (TestResultQC), and Batch (Batch) data in the Chemistry
group. Table 2-4 provides general information on the Vapor Intrusion EDD files. Detailed instructions
for creating the Vapor Intrusion EDD files are provided in Section 5, "Format for Vapor Intrusion Files".
Instructions for submitting your EDDs to EPA Region 2 are presented in Section 2.16.
Table 2-4 General information on the files that comprise the Vapor Intrusion EDD
File Type
Vapor
Intrusion
Building
Address
(Section 6.1)
Building data
(Section 6.2)
Vapor
Intrusion
Task
Parameters
(Section 6.3)
Vapor
Intrusion
Samples
(Section 6.4)
File Name
SiteNameDate.EPAI
D.VI_Bldg_Address
_v3.Txt(orcsv)
SiteNameDate.EPAI
D.VI_Building_v3.T
xt (or csv)
SiteNameDate.EPAI
D . VI_Task_Paramete
rs_v3.Txt (or csv)
SiteNameDate.EPAI
D.VI_Samples_v3.T
xt (or csv)
Created By
Data
provider's
Vapor
Intrusion
team (s)
Data
Provider's
Vapor
Intrusion
team (s)
Data
Provider's
Vapor
Intrusion
team (s)
Data
Provider's
Vapor
Intrusion
team (s)
Contents
Address and contact
information for the
building
Building specific
data
Additional
Sampling
parameters collected
in the field and not
analized in the lab
Sampling
Information for
Vapor Intrusion
What makes a row of
data unique?
Building_code
Building_name
Building_code
Building_name
Task_code
Param_code
Data_provider
Sys_loc_code
Sys_sample_code
Sample_matrix_code
Task_code
Sampling_company_cod
e
Sample_start_date
Dependenc
e of other
files on
these data
None
None
None
Tests/results
QCand
batch data
can only be
reported for
samples that
are defined
in this file.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 7
United States
Environmental Protection Agency
-------
Vapor
Intrusion Test
Result QC
(Section 6.5)
Vapor
Intrusion
Batches
(Section 6.6)
SiteNameDate.EPAI
D.VI_TestResultQC_
vS.Txt(orcsv)
SiteNameDate.EPAI
D.VI_Batches_v3.Tx
t (or csv)
Data
Provider's
Vapor
Intrusion
team (s)
Data
Provider's
Vapor
Intrusion
team (s)
Test Result
Batches
Sys_sample_code
Lab_anl_method_name
Analysis_date
Total_or_dissolved
Column_number
Test type
Sys_sample_code
Lab_anl_method_name
Analysis_date
Total_or_dissolved
Column number
Test_type
Test_batch_type
Test batch id
None
None
2.6 File Naming Convention
-Sign and Submit
After using the tools outlined above to resolve all of the issues in a set of Data Files the data is ready to be
submitted for loading into the EQuIS 5 database. The Sign and Submit tool was designed to facilitate
submittal of data to EQuIS Enterprise EDP. Sign and Submit option packages the data files with the
correct naming convention which allows easy submittal of data packages. Use of the Sign and Submit
feature requires a user name and password that may be obtained from the EQuIS Database Administrator.
To use the "Sign and Submit" feature, after data files have been loaded and all of the errors have been
resolved,
1. Select Sign and Submit from the Application Menu. This will open the Sign and Submit window.
User Name: username
Program Code:
Registry ID:
Password i
Save
Figure 13: Sign and Submit Window
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 8
United States
Environmental Protection Agency
-------
2. Enter your User Name and Password as well as the Program Code that applies to the data package
being submitted. The Registry ID will be automatically populated based on the selected Program Code.
For this exercise use your name as the User Name and Password, and 'NYO123456' for the Program
Code. This information will be used to create a user certificate file that EQuIS Enterprise uses to ensure a
valid user is submitting data for the appropriate Program. NOTE: The Program Code and Registry ID
are extremely important for Enterprise Data Submittals; however, the data entered into these sections of
the Sign and Submit screen may be modified by the user as needed.
3. Click the Save button.
4. Users will be prompted to provide a filename and location where you would like to save the file. The
Sign and Submit feature will save an archived ("zipped") file named with the current date, a period, the
Registry ID, a period and the Format File name used to create the EDDs. (Example file name: '20080424.
RegID123.EPARegion2EDD.zip'). The contents of the Zipped file includes text files named for the
sections of the format used to create them.
5. Select Save. Once the zipped EDD Package has been saved the following screen will appear.
EDD Signed and Submitted
Figure 14: Sign and Submit Verification Window
6. Select OK
After the zipped file has been created the EDD Package is ready to be submitted to your regulator for
loading into EQuIS Professional EDP or EQuIS Enterprise EDP.
Each file, except the base map file, must be named according to the following convention:
SiteNameDate.EPAIDCode.EDDFileFormat_v3.txt (or .csv)
The first part of the file name is the site name, followed by the submittal date of the EDD with the format
for the date being YYYYMMDD. The second part of the file name is the 12-character alphanumeric EPA
ID for the facility under investigation. IDs for EPA Region 2 sites are provided in Appendix Table A-22.
The third part of the file name refers to the EDD file format for the file being submitted. The "_v3" suffix
is an EPA marker to identify which version of the EDD specifications is being followed, and should not
be changed by the data provider. The name of the site base map file should include the site name and
EPAID and be saved in .dxf format.
As an example, the sampling data for the 1999 fourth quarter groundwater sampling round at the ABC
site (EPA identification number of XYZ123456789) that is being submitted to EPA on February 19, 2000
would be reported in a file named ABC20000219.XYZ123456789.Sample_v3.txt (or .csv). In the above
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 9
United States
Environmental Protection Agency
-------
example, the chemistry sample file (Sample) is being submitted, therefore the EDD File Format portion of
the file name is Sample_v3. The last part of the file name is an extension that will be "txt" if the file was
saved as a tab-delimited file or "csv" if it was saved as a comma-delimited file. Table 2-4 describes the
naming formats and for the various Initial, Chemistry and Geology EDD files.
Table 2-5 EDD File Naming Formats
File Type
Initial
Initial
Initial
Initial
Chemistry
Chemistry
Chemistry
Chemistry
Field
Field
Field
Field
Field
Field
Field
Field
Field
Field
Field
File Contents
Base Map
Site
Data Provider
Location
Sample
Sample
Test/Results
QC
Batch
Drill Activity
Lithology
Well
Well
Construction
Geology
Samples
Water Table
Down Hole
Point (CPT)
Data
Soil Gas Data
Water Level
Extraction -
Injection Well
Field Results
EDD File Name
Sitename.DXF
SiteNameDate .EPAIDCode . Site v3 .txt
SiteNameDate.EPAIDCode.DataProvider v3 .txt
SiteNameDate. EPAIDCode. Location v3 .txt
SiteNameDate. EPAIDCode. Sample v3.txt
SiteNameDate. EPAIDCode. Sample Parameter v3.txt
SiteNameDate.EPAIDCode.TestResultQC_v3.txt
SiteNameDate.EPAIDCode.Batch v3 .txt
SiteNameDate.EPAIDCode.DrillActivity_v3.txt
SiteNameDate.EPAIDCode.Lithology_v3.txt
SiteNameDate.EPAIDCode.Well_v3.txt
SiteNameDate .EPAIDCode .WellConstruction_v3 .txt
SiteNameDate.EPAIDCode.GeologySamples_v3.txt
SiteNameDate .EPAIDCode . WaterTable_v3 .txt
SiteNameDate.EPAIDCode.DownholePoint_v3.txt
SiteNameDate.EPAIDCode.SoilGas_v3.txt
SiteNameDate.EPAIDCode.WaterLevel v3 .txt
SiteNameDate.EPAIDCode.ExtractionlnjectionWells
_v3.txt
SiteNameDate.EPAIDCode.FieldResults v3 .txt
Submittal
Type
Initial
Initial
Initial
Initial
Recurring
Recurring
Recurring
Recurring
Non-
Recurring
Non-
Recurring
Non-
Recurring
Non-
Recurring
Non-
Recurring
Non-
Recurring
Non-
Recurring
Non Recurring
Recurring
Recurring
Recurring
2.7 Data Integrity Rules
Data providers are responsible for running three types of integrity checks on their data.
• Validity: All codes used in a data set must be valid. Valid values for all coded fields are either
provided in the description columns of the tables in Sections 3, 4, and 5 or in the tables in the
Appendix of this manual. For example, sample matrix information is inputted in the
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 10
United States
Environmental Protection Agency
-------
sample_matrix_code field of the sample file and must be reported using one of the values provided in
Table A-l in the Appendix.
• Row Uniqueness: Row uniqueness must be verified using the guidance provided in Tables 2-1, 2-2,
and 2-3. Row uniqueness is assured when no two rows in a file contain the same values for all the
fields listed under the heading "What makes a row of data unique?" In database terminology this is
called a primary key. For example, no two rows in the sample file can contain the same
sys_sample_code (commonly called a sample identifier). In addition, no two rows ever reported for a
single site can contain the same sys_sample_code. Each sys_sample_code must be unique for a site.
Files that have a primary key consisting of multiple fields, such as the water level file, must have a
different value in at least one of the prmary key fields. For example, no two rows in the water level
file can have the same sys_loc_code, measurement_date. For example, two rows with sys_loc_code
of "SB-01", measurement_date of "05/02/2000 00:00:00" would violate row uniqueness. However,
row uniqueness would not be violated if one row had a sys_loc_code of "SB-01", measurement_date
of "05/02/2000 00:00:00" and the other row had sys_loc_code of "SB-01", measurement_date of
"06/12/2000 00:00:00".
• Row Integrity: The relationship between rows within the files of the EDD must be assured by
enforcing the "referential integrity" rules discussed in Tables 2-1, 2-2, and 2-3 under the column
labeled "Dependence of other files on these data." For example, the values in the sys_sample_code
field in the Test/Result file must match with the corresponding fields in the Sample file. Logical
relationships between the various Chemistry EDD files are shown in Figure 2-1. The lines
connecting the files show which column(s) (or field(s)) are related in the two files. The file on the
side with the "1" at the end of the connecting line contains one row that is related to more than one
row in the related file on the other side. For example, one row in a SITE EDD file may correspond to
many rows in a LOCATION EDD file because there are always more than one, and in most cases
many locations, designated at a site. The logical relationship between the FIELD EDD files and the
Location EDD file is limited to the requirement that all entries in the sys_loc_code fields appear in
the LOCATION EDD file.
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 11 Environmental Protection Agency
-------
Figure 2-1 Relationships between chemistry file data structures.
Site
site_code
program code
site_name
site_task_code
site_descl
site_desc2
contact_name
address 1
address2
city
state
zip code
phone numbeer
alt_phone_number
fax_numbeer
email address
Location
sys_loc_code
latitude
longitude
surf_elev
elev_unit
coord_sys_desc
observation_date
alt_x_coord
alt_y_coord
alt_coord_type_code
alt_identifier
horz_collect_method_code
horz_accuracy_value
horz_accuracy_unit
horz_datum_code
elev_collect_method_code
elev_accuracy_value
elev_accuracy_unit
elev_datum_code
source_scale
subcontractor_name_code
verification_code
reference_point
geometric_type_code
rank
loc_name
loc_desc
loc_type
loc_purpose
primary _site_code
within_facility_yn
loc_county_code
loc_district_code
loc_state_code
loc_maj or_basin
loc_minor_basin
remark
total_depth
depth_to_bedrock
depth_to_top_of_screen
depth_to_bottom_of_screen
top_casing_elev
datum_value
datum_unit
step_or_linear
datum_collection_method_code
datum_desc
datum start date
Sample
sy s_sample_code
sample_name
sample_matrix_code
sample_type_code
sample_source
parent_sample_code
sample_delivery_group
sample_date
sample_time
sys_loc_code
start_depth
end_depth
depthjmit
chain_of_custody
sent_to_lab_date
sample_receipt_date
sampler
sampling_company_code
sampling_reason
sampling_technique
task_code
collection_quarter
composite_yn
composite_desc
sample_class
custom_field_l
custom_field_2
custom_field_3
comment
Test Result QC
sys_sample_code
lab_anl_method_name
analysis_date
total_or_dissolved
column_number
test_type
lab_matrix_code
analysis_location
basis
container_id
dilution_factor
prep_method
prep_date
leachate_method
leachate_date
lab_name_code
qc_level
lab_sample_id
percent_moisture
subsample_amount
subsample_amount_unit
analyst_name
instrument_id
comment
preservative
final_volume
final_volume_unit
cas_rn
chemical_name
result_value
result_error_delta
result_type_code
reportable_result
detect_flag
lab_qualifiers
validator_qualifiers
interpreted_qualifiers
validated_yn
method_detection_limit
reporting_detection_limit
quantitation_limit
result_unit
detection_limit_unit
tic_retention_time
minimum_detectable_conc
counting_error
uncertainty
critical_value
validation_level
result comment
Shaded fields are required to have data. Blue fields define row uniqueness for the specified file.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 12
United States
Environmental Protection Agency
-------
2.8 Definition of a Facility, Site, and Location
To submit and error-free EDD, it is important to understand how EPA Region 2 defines facility, site, and
location for the purposes of this EDD Specification Manual. Each facility (facility_id) will be identified
with its EPA ID number (see Table A-22 in the Appendix.) As EPA requirement, a facility center point
must be populated with the latitude and longitude centroid of the facility (*). The site (site_code) will be
the operable unit identifier. There will always be at least one operable unit per facility. The way the
location term is used is that each site can contain one or more locations, as long as they are distinct points
defined by X and Y universal transverse mercator (UTM) coordinates Examples of locations include soil
borings, monitoring wells, and sampling locations. Each location identifier (sys_loc_code) must be
unique for a facility.
Figure 2-2 provides a diagram of the facility components.
Figure 2-2 Facility component definitions
Facility
Sample ID: SO1234
Facility ID = EPA ID #
Site = Site Operable Unit = site_code Must be unique at a Facility
Location= sample location = sys_loc_code Must be unique at a Facility
2.9 Reporting Null Values
When a field is not listed as required in Sections 3, 4, and 5, and the data is not available or applicable, a
null or blank may be appropriate. However, tabs or commas must still delimit the blank value. In other
words, the number of fields is always the same, whether or not the fields include data. So a blank field in
a tab-delimited file would appear as "" and a blank field in a comma-delimited file would
appear as "„".Table 2-5 shows a number of examples.
Table 2-6 Examples of how to report null values
Example
"data_one""data_two" "data_three"
"data one", "data two", "data three"
Comment
O.K. All fields populated, one tab or comma
between fields.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 13
United States
Environmental Protection Agency
-------
Table 2-6 Examples of how to report null values
Example
"data one
"data one
"data_one
"data one
' "data_three"
',,"data three"
' "data_three"
V'data three"
Comment
O.K. Optional field not populated, 2 tabs or 2
commas between first and third field.
Not O.K. Optional field omitted, only 1 tab or
comma between first and third field.
2.10 Valid Values
Valid values, also known as reference values or code lists, govern the contents of some fields in the
EDDs. In other words, some fields may only be populated with data that matches a value listed in the
EPA Region 2 list of valid values. The lists of valid values are provided in the "Valid Values Table
Reference Manual". A list of all the data fields that must contain valid values is presented in Table 2-6
(below). This list is also cross-referenced to the EDD file(s) the field appears in. If data providers need
to enter a value not already in the Region 2 list in the Appendix, they can request the proposed addition
to the valid value list in the EDD cover letter. The data provider should explicitly state the valid value that
she/he would like added, provide a description of the value, and explain why the addition is necessary. In
the case of requesting a new aboratory code, the data provider should include the full name of the
laboratory and its address. When requesting an addition of an analyte, the data provider must include the
appropriate CAS number or ERPMS code along with a description of the analyte.
Table 2-7 Cross-reference between the valid value tables in appendix and the EDD files
Valid Value Table
Name
Matrix
Reference Point
Horizontal Collection
Method
Horizontal Accuracy
Unit
Horizontal Datum
Elevation Collection
Method
Elevation Datum
Source Scale
Location Type
Qualifier
Result Type
Sample Type
Standard Preparation
Method
Analyte
Lab Analysis Method
Name
Laboratory
Unit
Table
Number
A-l
A-2
A-3
A-4
A-5
A-6
A-7
A-8
A-9
A-10
A-ll
A-12
A-14
A-15
A-16
A-17
A-18
Field Name
sample_matrix_code, lab_matrix_code
reference point
horz collection method code
horz accuracy unit
horz datum code
elev_collect_method_code
elev datum code
source scale
loc type
lab qualifiers, validator qualifiers
result type code
sample type code
lab_prep meth
cas rn, chemical name
lab_anl_method_name
lab name code
various unit fields throughout all files
EDD File
Chemistry
Samples,
Test/Results
Location
Location
Location
Location
Location
Location
Location
Location
Test/Results
Test/Results
Chemistry Samples
Test/Results
Test/Results
Test/ Results
Test/Results
All Files
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 14
United States
Environmental Protection Agency
-------
Valid Value Table
Name
Geology Soil Materials
Well Segment and
Materials
Hydrologic Unit Codes
(HUC)
EPA Facility IDs
Company code
Fraction (Total or
dissolved)
Test Type
Test Batch Type
Table
Number
A-19
A-20
A-21
A-22
A-23
A-24
A-25
A-26
Field Name
material type
segmentjype, material_type_code
loc major basin
facility id, site name
Data_provider
Total_or_dissolved
Test type
Test batch type
EDO File
Lithology, Geology
Samples
Well Construction
Location
Site
Location, Sample,
Test Result, Data
Provider
Test Result, Test
Result QC, Batch
Test Result, Test
Result QC, Batch
Batch
2.11 Reporting Re-Tests
For initial tests, all analytes should be reported. In the case where retests are performed on a sample, the
result that is considered the reportable result should indicate a "Y" (for "yes") in the reportable_result
field. The initial test, and any retest result not considered reportable will have reportable_result set to
"No". Table 2.8 provides examples of reporting re-tests.
Table 2-8 Example of reporting re-tests
Test
Type
Initial
Initial
Initial
dilution 1
Chem
Name
Benzene
Toluene
Xylenes
Benzene
Cas rn
71-43-2
108-88-3
1330-20-7
71-43-2
Result
Value
1000
5
5
780
Detect
Flag
Y
N
N
Y
Lab
Qualifiers
E
U
U
Reportable
Result
No
Yes
Yes
Yes
Result Comment
too concentrated to
quantitate
not detected
not detected
Quantitated
2.12 Reporting Non-Detects
Non-detects must be reported as shown in the example below. Each non-detect row must show an "N" in
the detect_flag field, must have an actual value entered in the reporting_detection_limit and
detection_limit_unit fields, and must contain a null in the result_value_field. The
reporting_detection_limit cannot be negative unless one of the radiological fields (including
minimum_detectable_conc, counting_error, uncertainty, critical_value) are populated. Table 2.9 presents
examples of how to report non-detects.
Table 2-9 Example of reporting non-detects
Cas rn
108-88-3
108-88-3
Result
Value
.15
Detect
Flag
Y
N
Reporting
Detection
Limit
.005
.005
Detection
Limit Unit
ug/ml
ug/ml
Result_comment
not detected
Laboratory
qualifiers
U
U
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 15
United States
Environmental Protection Agency
-------
2.13 Reporting Tentatively Identified Compounds
Tentatively Identified Compounds (TICs) should be reported when available. The naming of TICs should
be applied in a cascade fashion. The TIC should be identified to analyte name if possible. If this is not
possible, then the class of the TIC should be entered. If neither an analyte name or a class can be
identified, the TIC should be identified as Unknown. The EPA Region 2 EDD only allows for reporting
up to 10 TICs. Only the 10 most concentrated or most relevant TICs should be reported. Table 2-10
shows examples of the nomenclature for TICs. As an example, if a sample has three Unknown
Hydrocarbons, then the TICs are labeled UnkHydrocarbl, UnkHydrocarb2, and UnkHydrocarbS. TIC
names are to be reported in the cas_rn field, Pos #31, of the Test/Result file (Tables 4-3 and Table 4-4).
In addition, the result_type_code, Pos # 35 in the Test/Result file should have "TIC" for all TIC records.
Table 2-10 Example nomenclature for TIC reporting
TIC Name
Unknown
Unknown Hydrocarbon
Unknown PAHs
Unknown Aromatics
Unknown VOA
Unknown SV
Number for TIC
-10
-10
-10
-10
-10
-10
Reported Name in cas rn
Unknown 1 - Unknown 10
UnkHydrocarbl - UnkHydrocarbl 0
UnkPAHl - UnkPAHIO
UnkAromaticl - UnkAromaticlO
UnkVOAl - UnkVOAlO
UnkSVl - UnkSVIO
2.14 Data Types
The table below describes the data types used in the chemistry and geology file descriptions. In addition
to the types listed below, certain fields have single and double data types. The single data type stores
numbers from -3.402823 x 1035 to -1.401298 x 10"43 for negative values and from 1.401298 x 1043 to
3.402823 x 10 for positive values, with a decimal precision of up to 7 digits. The double data type
stores numbers from -1.79769313486231 x 10308 to
-4.94065645841247 x 10'J/4 for negative values and from 1.79769313486231 x 10JUS to
4.94065645841247 x 10" for positive values, with a decimal precision of up to 15 digits.
Table 2-11 Data type descriptions
Type
Integer
'¥' or TST
Time
Date
Text
Description
Stores numbers from -32,768 to 32,767 (no
fractions).
Boolean field used to indicate yes or no to a
question. Enter either Y or N.
Time in 24-hr (military) HH:MM format.
Date format is MM/DD/YYYY.
Stores characters and numbers.
Decimal
Precision
None
NA
NA
NA
NA
Comments
Text(5) is standard
length for time.
Length restrictions are
indicated in
parentheses.
2.15 Data Entry Tools Provided to Create the EDD Files
EDD files can be produced using any software with the capability to create text files. These files are
especially easy to create using spreadsheet or database software packages. However, if these are
unavailable, the files can be created using a word processor or text editor. Table 2-12 provides
instructions for creating tab-delimited text files from some widely-used software packages.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 16
United States
Environmental Protection Agency
-------
Table 2-12 Instructions for producing tab-delimited text files from some software packages
Package
Access
Excel
Quattro® v8
Word
Lotus 1-2-3
Type
Database
Spreadsheet
Spreadsheet
Word
Processor
Spreadsheet
Instructions
1. Create tables using file structures in Sections 3 and 4.
2. After data are entered, close table.
3 . Click on table name (under table tab) and then select
"File," "Save As," from the top menu. Save to an external
file or database. Change "Save as Type" to a text file.
Change the file extension from "txt" to "tab." Press OK.
This will start the export wizard.
4. In the export wizard, select "Delimited," then press the
"Next" button. Select "Tab" as the delimiter type and " as
the text qualifier. Press the "Next" button. Select a
destination and name for the file. Press the "Finish"
button.
1. Select "File," "Save As," from the top menu. Change
"Save as Type" to a "Text (Tab Delimited)" file. Press the
"Save" button.
1 . Select "File," "Save As," from the top menu. Change the
"File Type" to "ASCII Text (Tab Delimited)." Press the
"Save Button."
[Note: A word processor is not the best tool for the job! A
large paper size will have to be selected to prevent wrapping
for most files. ] [wrapping?]
1 . Enter data into a table in Word. Any text entered must be
contained within double quotes.
2. Select "Table," "Select Table," from the top menu. When
the table is highlighted, select "Table," "Convert to Text,"
"Separate Text with Tabs."
3. Select "File," "Save As," from the top menu. Change
"Save as Type" to "MS DOS Text (*.txt).
1. Select "File," "Save As," from the top menu. Change
"Save as Type" to a "Comma Separated Value (CSV)"
file. Provide file name. Press the "Save" button.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 17
United States
Environmental Protection Agency
-------
2.16 Using the Electronic Data Processor to Check EDD Formatting
The Electronic Data Processor (EDP) can be used by Data Providers to check EDD files prior to submittal
to EPA Region 2. The EDP is a no-cost application that performs a series of formatting checks on the
files and then identifies any records that have errors along with a description of the errors. This allows
the Data Provider to correct the errors before sending the files to EPA Region 2. EDD files that pass
through the EDP error-free should also result in error-free import at EPA Region 2.
EDP is currently available as a no-cost download from the EPA Region 2 website located at at
http://www.epa.gov/region02/superfund/medd.htm. Instructions on how to install and use the EDP are
also provided on the website.
2.17 Submitting Your EDD to EPA
It is preferred to submit by e-mail, e-mail submittals may be provided with cc: Remedial Project Manager
(RPM). Each EDD must be accompanied by a cover letter that specifies the name of the site, the contact
for any EDD technical questions regarding file names, any exceptions to the EDD format, any requests
for additional valid values, etc. Larger files should be zipped and renamed e.g. *.piz.
All electronic submittals should be sent to: Reqion2 EQUISedd@epa.gov and cc:ed RPM
If you cannot submit files electronically, contact the EDD coordinator.
There are three possible EDD submittal types: an original submittal, an error correction resubmittal, and
an update submittal. These three EDD types are described below.
• Original Submittal: An original EDD submittal contains data being submitted for the first time
to EPA Region 2. EPA Region 2 will process and check the EDD. If there are no errors in any of
the EDD files, EPA will import the data to the permanent database. EPA Region 2 can only
import and accept the EDD submittal if all files in the submittal are error-free. If any of the files
on the EDD contain errors, EPA will send the data provider a letter specifying the errors that
need to be corrected.
• Correction Resubmittal: In the case where an original EDD submittal contains errors, the
entire EDD submittal will be returned to the data provider along with an error report explaining
the problems identified. The data provider should then correct the errors, check the files again
with the EDP, and then resubmit the entire EDD. A response is required within 30 days. It is
important that the resubmitted EDD contain all of the files and the SAME FILE NAMES (i.e.,
use the same site name and submittal date in the file name as was used in the original submittal)
as those in the original submittal. Thus, the EDD resubmittal will be identical to the original
submittal in everyway except the errors are corrected.
• Update Submittal : This type of submittal updates data that has previously been accepted by
EPA Region 2. The files of an update submittal should follow the normal naming convention of
an EDD submittal and contain only data for the records being updated. For example, say a data
provider submits an EDD in 2001 that includes a location file (e.g.,
ABC20010121.EPAID.Location_v3.txt) that contains ten locations, and the EDD is accepted by
EPA Region 2 and loaded into the EPA database. If, in 2003, the site is resurveyed, and it is
discovered that three of the locations' coordinate information has changed due to increased
accuracy, a new location file containing data for only those three locations would need to be
submitted as an update submittal. The update submittal would be named using the current
submittal date of the update (e.g., ABC20031108.EPAID.Location_v3.txt). Note: All required
fields need to be populated for the three locations regardless of whether or not these fields were
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 18 Environmental Protection Agency
-------
updated. The reason for the update submittal and the records that have been changed must be
clearly indicated in the cover letter accompanying the updated EDD.
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 19 Environmental Protection Agency
-------
2.18 Examples of Initial, Chemistry, and Field EDO Files
Examples of Initial, Chemistry and Field EDD files with the first few rows of the EDD populated with a typical data set are presented in Figures 2-
3, 2-4, 2-5, and 2-6. These examples were produced using Excel worksheets. To submit these files, the data provider would save the files as text
delimited files (txt) or comma separated files (csv), check the files using the EDP, and then send the error free files to Region 2. In order to fit the
examples on one page, not all of the fields (i.e., columns) were included for certain files (e.g., Site, Location, Chemistry Sample). The notation
"Additional Fields" has been inserted where, for purposes of these examples, one or more fields have been omitted.. It should be noted that all
fields must appear in the EDD files you submit regardless of whether or not the field is populated (see Section 2.9 regarding reporting blanks, or
"null" values). Special cases discussed in previous sections of this manual, as well as more standard types of data, are illustrated below.
Figure 2-3. Example Initial EDD ready for conversion to text file
Site File:
site_code
Example
facility_id
NJD123456723
site_name
Example Site
site_task_code
site_descl
site_desc2
contact_name
John Smith
addressl
23 Main Street
Additional
Fields
email address
abc(S>abd.com
Location File:
sys_loc_code
MW01
SB-01
MW03
MW04
Latitude
44.24543
44.24304
44.24700
44.24700
Longitude
-73.445678
-73.470923
-73.460123
-73.460123
surf_elev
120.2
126.3
130.1
130.1
elev_u
nit
ft
ft
ft
ft
coord_sys_desc
LAT LONG
LAT LONG
LAT LONG
LAT LONG
observation
date
02/21/1999
02/23/1999
02/22/1999
02/22/1999
alt_x_coord
440022.31
442430.31
442470.22
442356.51
Alt_y coor
d
399612.23
393574.22
399701.25
399701.48
alt_coord_t
ype-code
SP
SP
SP
SP
alt_identi
Her
1
1
1
1
Additional
Fields
comment
Sample File:
Figure 2-4. Example Chemistry EDD ready for conversion to text file
sys_sample_
code
MW01040198
MW02040198
sample_
name
sample_
matrix code
WG
WG
sample_type_
code
N
N
sample_so
urce
Field
Field
parent_sample
code
sample_delivery
_group
sample_
date
04/01/1998
12:00:00
04/01/1998
12:00:00
sys_loc_code
MW01
MW02
Additional
Fields
comment
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 20
United States
Environmental Protection Agency
-------
Test Result QC File:
sys sample
code
MW02040198
MW02040198
MW02040198
lab anl
method_
name
SW8240
SW8240
SW8240
Additional
Fields
total or
dissolved
T
T
T
column
number
test_
type
Initial
Initial
Reanalysis
lab matrix
_code
WG
WG
WG
analysis
location
LB
LB
LB
basis
Wet
Wet
Wet
Additional
Fields
dilution
factor
1.0
1.0
10.0
lab
name
code
ABC
ABC
ABC
qc_
level
quant
quant
quant
lab
sample
id
LAB01
LAB02
LAB02R
Additional
Fields
Test Result QC (Continue):
cas rn
71-43-2
108-88-3
1330-20-7
chemical
name
BENZENE
TOLUENE
XYLENES
result
value
12
result
error
delta
result
type_
code
TRG
TRG
TRG
reportable
result
Yes
Yes
Yes
detect flag
Y
N
N
lab
qualifiers
Validate
d_yn
Y
Y
Y
Method del
ection limit
reporting^
detection
limit
10
10
10
Quantitation
limit
result
units
ug/ml
ug/ml
ug/ml
Additional
Fields
result_
comment
Figure 2-5. Examples of QC data fields in a Chemistry EDO
QC fields in a normal field sample (i.e., sample_type_code = N, TB, etc.)
The following table shows some of the fields in the test/result (TRS) file for a normal field sample. Notice that all QC fields are blank.
cas_rn
93-76-5
94-75-7
94-82-6
result_value
1.56
3.17
2.31
qc_original
cone
qc_spike_
added
qc_spike_
measured
qc_spike_
recovery
qc_dup_
original
cone
qc_dup_
spike
added
qc_dup_
spike
measured
qc_dup_
spike
recovery
QC fields in a normal field sample with surrogates (i.e., sample_type_code = N, TB, etc.)
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 21
United States
Environmental Protection Agency
-------
The following table shows some of the fields in the test/result file (TRS) for a normal field sample. Notice that QC fields are blank except in rows
related to surrogate samples. . Many data providers will only need to populate the recovery field data; the spike-added and spike-measured fields
will not be needed in most situations.
Cas_rn
93-76-5
94-75-7
PHEN2F
result_value
1.56
3.17
result_unit
mg/1
mg/1
mg/1
result_type_
code
TRG
TRG
SUR
qc_original_
cone
qc_spike_added
12.5
qc_spike_
measured
12.9
qc_spike_
recovery
103
QC fields in a laboratory method blank sample (i.e., sample_type_code = LB)
The following table shows some of the fields in the test/result file for a laboratory method blank sample. Notice that all QC fields are blank.
cas rn
93-76-5
94-75-7
94-82-6
result
value
0.01
lab
qualifier
U
U
qc_
original
cone
qc_spike_
added
qc_spike_
measured
qc_spike_
recovery
qc_dup_
original
cone
qc_dup_
spike
added
qc_dup_
spike
measured
qc_dup_
spike
recovery
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 22
United States
Environmental Protection Agency
-------
Figure 2-5. Examples of QC data fields in a Chemistry EDD (continued)
QC fields in a matrix spike (i.e., sample_type_code = MS)
The following table shows some of the fields in the test/result file for a matrix spike sample. Notice that all "dup" QC fields are blank and that the
result_value field is not needed. Also, the qc_rpd field would be blank for these rows. Many data providers will only need to populate the
calculated recovery field (qc spike recovery).
cas rn
93-76-5
94-75-7
94-82-6
result
value
qc_
original
cone
1.56
3.17
2.31
qc_spike_
added
4.18
4.18
4.22
qc_spike_
measured
5.36
7.15
5.66
qc_spike_
recovery
90.9
95.2
79.3
Qc_rpd
qc_dup_
original
cone
qc_dup_
spike
added
qc_dup_
spike
measured
qc_dup_
spike
recovery
QC fields in a matrix spike duplicate (i.e., sample_type_code = SD)
The following table shows some of the fields in the test/result file for a matrix spike duplicate sample. Notice that all "dup" QC fields are filled in
and that the result_value field is not needed. Also, the qc_rpd field would be completed for these rows. Many data providers will only need to
populate the calculated recovery field (qc dup spike recovery).
cas rn
93-76-5
94-75-7
94-82-6
result
value
qc_
original
cone
qc_spike_
added
qc_spike_
measured
qc_spike_
recovery
Qc_rpd
10
12
15
qc_dup_
original
cone
1.56
3.17
2.31
qc_dup_
spike
added
4.23
4.23
4.13
qc_dup_
spike
measured
5.70
7.62
5.33
qc_dup_
spike
recovery
97.8
105
73.1
QC fields in a matrix spike/matrix spike duplicate (i.e., sample_type_code = MSD)
The following table shows some of the fields in the test/result file for a matrix spike/matrix spike duplicate considered as a single sample . (Note:
Matrix spike and matrix spike duplicate samples can be reported either this way or as two separate samples as shown above). Notice that all QC
fields are filled in and the result_value field is not needed. Also, the qc_rpd field would be completed for these rows. Many data providers will
only need to populate the calculated recovery fields (qc spike recovery and qc dup spike recovery).
cas rn
93-76-5
94-75-7
94-82-6
result
value
qc_
original_
cone
1.56
3.17
2.31
qc spike
added
4.18
4.18
4.22
qc spike
measured
5.36
7.15
5.66
qc spike
recovery
90.9
95.2
79.3
Qc rpd
7
10
8
qc dup
original_
cone
1.56
3.17
2.31
qc dup
spike_
added
4.23
4.23
4.13
qc dup
spike_
measured
5.70
7.62
5.33
qc dup
spike_
recovery
97.8
105
73.1
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 23
United States
Environmental Protection Agency
-------
QC fields in a LCS (i.e., laboratory control sample, blank spike, sample_type_code = BS)
The following table shows some of the fields in the test/result file for an LCS sample. The qc_rpd field would be blank for these rows. Many data
providers will only need to populate the calculated recovery field (qc_spike_recovery). LCS duplicate samples (i.e., sample_type_code = BD)
and LCS/LCSD samples (i.e., sample type code = BSD) follow the patterns similar to the SD and MSP samples described above.
cas rn
93-76-5
94-75-7
94-82-6
result
value
qc original
cone
qc spike
added
5.00
1.00
12.5
qc spike
measured
5.26
1.02
12.9
qc spike
recovery
105
102
103
qc dup
original_
cone
qc dup
spike_
added
qc dup
spike_
measured
qc dup
spike_
recovery
Figure 2-6. Example Field EDD ready for conversion to text file
Drill Activity File:
Lithology File:
sys loc
code
W-1A
W-1A
W-1A
W-2A
start
depth
0
10
23
0
material
type
CL
SW
SP
ML
geo unit 1
Glacial
Outwash
Outwash
Alluvial
Well File:
sys loc code
W-1A
W-2A
end_depth
80
110
drill_date
07/12/1999
07/14/1999
Additional
Fields
diameter
8
8
Additional
Fields
purpose
Advanced well additional 40 feet to reach lower aquifer
Advanced well 55 feet to reach bedrock.
Remark 1
grayish brown clay, trace fine sand, med strength, med plastic, rapid dilatancy ,some brick
fragments
med dense, 50% fine to coarse brown sand, 30% gravel, dry, trace clay
dense, 70% coarse brown sand
, 20% gravel,
poorly graded, rounded, moist
Dark brown silt with little fine sand, low strength, nonplastic, rapid dilatancy
Additional
Fields
odor
Additional
Fields
top casing elev
122.0
122.3
datum value
122.0
122.3
datum unit
ft
ft
datum desc
top of casing of well
top of casing of well
Additional
Fields
geologic unit
code
outwash
alluvial
remark
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 24
United States
Environmental Protection Agency
-------
Figure 2-6. Example Field EDD for new monitoring wells or direct push samples ready for conversion to text file (continued)
Well Construction File
sys loc code
W-1A
W-1A
W-1A
W-1A
W-1A
W-1A
W-1A
W-2A
W-2A
W-2A
segment type
surface plug
annular backfill
annular Seal
Filter Pack
Protective Casing
Casing
Screen
protective casing
surface plug
annular backfill
material type code
concrete
neat cement grout
Bentonite pellets
sand pack
steel
stainless steel 304
stainless steel 304
steel
concrete
neat cement grout
start depth
0
1.5
8
8
-2.2
-2.1
24
-2.0
0
1.5
end depth
1.5
8
8
23.1
3.2
24
29
3.0
1.5
10
depth unit
ft
ft
ft
ft
ft
ft
ft
ft
ft
ft
inside diameter
4.5
2.375
2.375
2.375
4
2
2
2
4.5
2.375
Additional
Fields
remark
Geology Sam
sys loc code
W-1A
W-1A
W-2A
pie File:
Geo sample code
ABCD-1
ABCD-2
DEFG-1
sample name
sample top
4
14
5
sample bottom
6
16
7
sample date
04/23/1999
00:00:00
04/23/1999
00:00:00
04/24/1999
Additional
Fields
sample method
split spoon
split spoon
split spoon
material type
SW
sw
SP
Additional
Fields
organic_carbon
units
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 25
United States
Environmental Protection Agency
-------
Figure 2-6. Example Geology EDD for new monitoring wells or direct push samples ready for conversion to text file (continued)
Water Table File:
sys loc code
MW01
MW02
Type
Unconfined
Unconfined
sequence
stable
stable
Depth
21.2
21.0
flowing_yn
y
y
measurement method
electric sensor
electric sensor
capped_pressure
capped pressure
unit
Additional
Fields
temperature
unit
Down Hole Point File:
sys_loc_code
MW01
MW01
MW01
MW01
MW02
MW02
MW02
Depth
10.8
11.2
10.8
11.2
9.5
10.1
11.0
param
Tip Stress
Tip Stress
Sleeve Stress
Sleeve stress
Resistivity
Resistivity
Resistivity
param_value
612
624
6.1
5.8
510
521
489
Water Level File:
sys loc code
MW01
MW02
measurement
date
05/10/1999
13:10:00
05/10/1999
13:45:00
historical ref elev
water level depth
31.1
34.1
water level elev
89.1
89.0
corrected elev
Additional
Fields
remark
Extraction Injection Wells
sys_loc
code
EX-01
EX-02
Start_
measurement
date
05/12/2000 11:23:00
11/12/200012:00:00
end_measure
_date
06/12/2000
11:30:00
12/12/2000
13:10:00
avg_pump_rate
2.5
1.75
pump_rate_unit
mgd
mgd
Additional
Fields
remark
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 26
United States
Environmental Protection Agency
-------
3. FORMATS FOR INITIAL FILES
This section contains information regarding the base map and the two files included in the initial EDD.
These files need to be submitted prior to, or in conjunction with, the first Chemistry EDD or Geology
EDD submittals These files only need to be submitted once unless information in the files changes or
additional information, such a new sampling location, needs to be added. Columns marked "Required"
must be reported for each row in the file. If these fields are not reported, errors will be identified in the
EDD and the EDD will need to be resubmitted. Columns marked "If available" should also be reported if
possible.
3.1 Site Base Maps in the file section
Site base maps must be electronic CAD files in a DXF interchange format. The maps should include all
well locations, waste management units, landfills, buildings, and roads. Do not include any groundwater
contours, contaminant contours, or other temporal type information. If the CAD file is available in real
world locational coordinates, provide the coordinates along with a brief text description of the type of
projection and datum used. (Note: UTM NAD 83 is the data type preferred by EPA Region 2). Also
include text descriptions of the units and scale of the base map. The site base map file should be named
according to the following example:
SiteName.DXF
The file section allows you to load supplementary information into EQuIS, such as Map, drawing files.
Table 3-1 Files
Pos#
1
2
3
4
5
6
7
8
9
10
11
Column Name
File name
File_type
File_date
Title
Author
Confidential _yn
Remark
Place_type
Place_code
Place_subcode
Content
Data type
Text (255)
Text (20)
Date time
Text (255)
Text (255)
Text (1)
Text (255)
Text (50)
Text (50)
Text (50)
Required
Yes
Yes
If available
If available
If available
If available
If available
If available
If available
If available
Description
Name of the file
Type of the file
Date of the file
Title of the file
Author of the file
Whether or not the file is
confidential
Remark for the file
Type of the place tis file
is associated with
Code/identifier of the
place this file is associate
with
Subcode/ identifier of the
place this file is
associated with
Content of the file
Valid Values In
Appendix
No
No
No
No
No
No
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 27
United States
Environmental Protection Agency
-------
3.2. Data Provider
The Data Provider EDD file provides general information about the data provider who is the contact for
the data on the site.
SiteNameDate.EPAIDCode.DataProvider_v3.txt (or .csv)
Table 3-2 Data Provider File Structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
Column Name
Data Provider
Code
Data Provider
Contact Name
Contact
Address 1
Contact
Address2
Contact City
Contact State
Contact zip code
Contact country
Contact Phone
Number
Contact email
address
Data Type
Text (20)
Text(70)
Text(50)
Text (40)
Text (40)
Text (30)
Text(2)
Text(30)
Text (50)
Text(20)
Text(lOO)
Required
Required
Required
Required
Required
If available
Required
Required
Required
Required
Required
If available
Description
Data Provider company code
This is the name of the company who is
responsible for providing the site data.
This is the name of the contact person
who is responsible for providing the site
data.
Data Provider address 1
Data Provider address 2
Data Provider city
Contact state
Contact zip
Data Provider Country
Contact phone number
Contact email address
Valid Values
In Appendix
A-23
A-23
No
No
No
No
No
No
No
No
No
3.3 SITE EDD File
The SITE EDD file provides general information about a site and provides the name, e-mail address, and
other contact information for the main EDD data contact for the site. The SITE file is a required part of
any initial EDD submittal. An example of a Site file is provided in Figure 2-3, section 2.17. NOTE: If
the SITE EDD file was previously submitted, including as part of a "Historic Data EDD",as described in
the Region 2 "EDD Manual for Historical Data", you DO NOT need to resubmit the file again.
Each SITE file must be named according to the following convention:
SiteNameDate.EPAIDCode.Site_v3.txt (or .csv)
Table 3-3 SITE data file structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 28
United States
Environmental Protection Agency
-------
Table 3-3 SITE data file structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Column Name
site_code
Program_Code
site name
site_task_code
site descl
site_desc2
contact_name
address 1
address2
City
State
Zipcode
phone number
alt_phone_number
fax_number
email address
Data Type
Text(3)
Text(20)
Text(60)
Text(20)
Text(255)
Text(255)
Text(50)
Text(40)
Text(40)
Text(30)
Text(2)
Text(lO)
Text(30)
Text(30)
Text(30)
Text(lOO)
Required
Required
If available
Required
If available
If available
If available
Required
Required
If available
Required
Required
Required
Required
If available
If available
Required
Description
Code indicating the site operable unit
for which the data is collected, or
area of concern (AOC). Typically
the code is "01" unless there is a
second or third operable unit at
facility. Codes of "02" and "03"
should be used for second and third
operable units, respectively. Contact
the EPA RPM if unsure of proper
code.
This is equivalent to the EPA
CERCLIS ID number, or SRPID or
other state program code.
Name of site
Code used to identify the task under
which the site or area is investigated.
This field is for informational
purposes only. Field samples are
formally associated with task codes.
General description of the site.
Additional description of site, if
necessary.
Name of person to contact if EPA
Region 2 has any questions about the
EDO.
Site address, part one.
Site address, part two. Default to null
if information is not needed
Site city.
Site state.
Site zip code.
Site contact phone number.
Alternate phone number for site
contact. Default to null where the
data are not available.
Fax number of site contact. Default
to null where the data is not
available.
Site contact e-mail address.
Valid Values
In Appendix
No
Table A-22
Table A-22
No
No
No
No
No
No
No
No
No
No
No
No
No
3.4 Location EDO File
The primary purpose of the Location EDD file is to define the sampling locations for a site. Each EPA ID
must have a center point identified. The location section will be used to enter the center point. This file
is referred to as one of the Initial EDD files because it needs to be submitted ~ and error-free ~ before
EDD files that contain chemistry and geology data can be used. Each row of the Location file contains
the definition of a unique sampling location. Do not create any records (i.e., rows) for any samples not
associated with a specific sampling location, such as field blanks and trip blanks. In the case of multiple
wells located in one borehole, each well in the borehole must have a unique sampling location identifier
(sys_loc_code).
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 29
United States
Environmental Protection Agency
-------
Each sampling location should only be reported once for a site. The only time data a previously reported
location should be resubmitted is if some information about the location changes, such as when a location
is resurveyed after settling has occurred or after a resurvey using an instrument or methodology with
higher accuracy. When resubmitting changes to the Location file, the file should contain rows pertaining
to the affected locations only. As in a typical EDD submittal, all "required" fields should be populated
when updating data. Changes in the resubmittal should be described in the cover letter accompanying the
EDD, and the EPA RPM should receive a copy of the letter or should be otherwise notified. See section
2.16 "Submitting Your EDD to EPA" for more information regarding submitting updated data files.
The data structure of the LOCATION EDD file includes fields (Table 3-2 below) to collect data
requirements of EPA's Locational Data Policy (LDP). LDP requires geographic coordinates and
associated method, accuracy, and description (MAD) codes for all environmental measurements collected
by EPA employees, contractors, and grantees. A key premise of the LDP policy is that secondary use of
these data in geographic information systems (GIS) and statistical mapping programs are significant to the
overall mission of the Agency. To facilitate the integration of data, EPA has established the LDP to
standardize the coding of geologic coordinates and associated attributes. Therefore, in addition to location
coordinates being reported in UTM meters, Region 2 requests that coordinates be reported in latitude and
longitude, along with associated attributes, if the data is available. An example of a Location file is
provided in Figure 2-3, section 2.17.
Each Location file must be named according to the following convention:
SiteNameDate.EPAIDCode.Location_v3.txt (or .csv)
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 30 Environmental Protection Agency
-------
Table 3-4 Location Data File Structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
Column Name
Data Provider
sys_loc_code
Latitude
Longitude
surf_elev
elev_unit
coord_sys_desc
observation_date
alt_x_coord
alt_y_coord
alt_coord_type_code
Data
Type
Text(20)
Text(20)
Number
w/decim
al
precision
up to 15
Number
w/decim
al
precision
up to 15
Number
w/decim
al
precision
up to 15
Text(2)
Text(20)
DateTim
e
Text(20)
Text(20)
Text(8)
Required
Required
Required
Required
Required
Required
Required
Required
If available
If available
If available
If available
Description
Data Prodiver company code
Location ID, such as MW-01,
A24, SW12, or SB-2S, for all
samples collected, including
groundwater samples,
hydropunch samples, surface
water/sediment samples, and
soil samples. For facility
center point, sys loc code =
"F AC CENTER POINT"
Latitude of sampling location
in decimal degrees
(dd.xxxxxx).
Longitude of sampling
location in decimal degrees.
Must be negative for western
hemisphere (-ddd.xxxxxx)
Elevation of the ground
surface, or if location is for
surface water samples, water
surface elevation.
For water surface elevation,
use the average annual
elevation. Note: Subsequent
water surface elevations
should be obtained during the
surface water sampling period
and reported in the Water
Level EDD file (see sections
4.2 and 4.4).
Unit of measurement for
elevations.
Sampling location coordinate
system description. Must be in
decimal degrees, Latitude and
Longitude.
Date observation or site
survey was made.
X_ state plane or UTM
NAD83 coordinate
Y_ state plane or UTM
NAD83 coordinate
Use State Plane or UTM
NAD83. Code for the
coordinate type used for alt_x
and alt_y.
Valid Values
In Appendix
A-23
No
No
No
No
Units must be in
ft/m
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 31
United States
Environmental Protection Agency
-------
Table 3-4 Location Data File Structure
Pos#
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Column Name
alt_Identifier
horz_collect_method_c
ode
horz_accuracy_value
horz_accuracy_unit
horz_datum_code
elev_collect_method_c
ode
elev_accuracy_value
elev_accuracy_unit
elev_datum_code
source_scale
subcontractor name co
de
verification_code
reference_point
geometric_type_code
Rank
loc name
Data
Type
Text(20)
Text(3)
Text(20)
Text(8)
Text(3)
Text(2)
Text(20)
Text(8)
Text(3)
Text(2)
Text(20)
Text(l)
Text(2)
Text(20)
Numeric
Text(40)
Required
It is required
when
"alt_x_coord"
and
"alt_y_coord"
are populated
required
required
required
required
required
If available
If available
If available
Conditional
Required
If available
Reserved for
future use
If available
Reserved for
future use
Reserved for
future use
If available
Description
Leave Null. For use by EPA
Region 2. This field is
associated with the alt_x and
alt_y
Method used to determine the
latitude/longitude
measurements. Horizontal
Collection Method.
Accuracy range (+/-) of the
latitude and longitude. Only
the least accurate
measurement should be
reported, regardless if it is for
latitude or longitude.
Unit of the horizontal
accuracy value..
Reference datum of the
latitude and longitude..
Method used to determine the
ground elevation of the
sampling location.
Accuracy range (+/-) of the
elevation measurement.
Unit of the elevation accuracy
value..
Reference datum for the
elevation measurement
Scale of source used to
determine the latitude and
longitude..
*required if horizontal
Collection Method is
prompted.
Code used to distinguish
subcontractor name.
This field is only to be used by
EPA Region 2 personnel.
Please leave blank.
Describes the place at which
coordinates were established.
Use codes from Table A-2 in
the Appendix.
This field is for by EPA
Region 2 future use. Please
leave blank.
This field is for by EPA
Region 2 future use. Please
leave blank.
Sampling location name.
Valid Values
In Appendix
No
Table A-3
No
Table A-4
Table A-5
Table A-6
Table A-18
Table A-7
Table A-8
No
No
Tabel A-2
No'
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 32
United States
Environmental Protection Agency
-------
Table 3-4 Location Data File Structure
Pos#
28
29
30
31
32
33
34
35
36
37
38
39
40
Column Name
loc_desc
loc_type
loc purpose
site_code
within_facility_yn
loc_county_code
loc_district_code
loc_state_code
loc_major_basin
loc_minor_basin
Remarks
total_depth
depth_to_bedrock
Data
Type
Text(255
)
Text(20)
Text(20)
Text(3)
Text(l)
Text(20)
Text(3)
Text(2)
Text(8)
Text(20)
Text(255
)
Number
w/decim
al
precision
up to 15
Number
w/decim
al
precision
up to 15
Required
If available
If available
If available
Required
Required
If available
If available
If available
If available
If available
If applic-able
If available
If available
Description
Sampling location description.
Description of sampling type,
such as direct push, extraction
well, or sediment. Use
"CENTROID" to identify
facility center point. Use codes
from Table A-9 in the
Appendix.
Sampling location purpose.
Unique code for site or area.
Must match site_code field
from Table 3-1: Site File Data
Structure.
Indicates whether this
sampling location is within
facility boundaries, "Y" for
yes or "N" for no.
Location county code;
controlled vocabulary using
FIPS (Federal Information
Processing Standard) codes.
FIPS codes can be found via
the internet at
http ://www. itl. nist. gov/fipspub
s/.
Location district code;
controlled vocabulary using
FIPS codes.
Location state code; controlled
vocabulary using FIPS codes.
Location major basin;
controlled vocabulary using
HUC (hydrologic unit codes
Location minor basin;
controlled vocabulary using
HUC codes. Any digits after
the 8th (first 8 are reported in
loc_major_basin) should be
reported here.
Location specific comment.
Total depth below ground
surface of boring, in feet.
Depth below ground surface
of bedrock in feet.
Valid Values
In Appendix
No
No
No
Table 3-1
Y = Yes
N=No
No
No
No
Table A-21
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 33
United States
Environmental Protection Agency
-------
Table 3-4 Location Data File Structure
Pos#
41
42
43
44
45
46
47
48
49
Column Name
depth_to top_of_screen
depth_to_bottom_of_sc
reen
top_casing_elev
datum_value
datum_unit
step_or_linear
datum_collect_method
code
datum_desc
Datum_start_date
Data
Type
Number
w/decim
al
precision
up to 15
Number
w/decim
al
precision
up to 15
Number
w/decim
al
precision
up to 15
Number
w/decim
al
precision
up to 15
Text (15)
Text (6)
Text (2)
Text(70)
DateTim
e
Required
If available
If available
If available
Reserved for
future use
Reserved for
future use
Reserved for
future use
Reserved for
future use
Reserved for
future use
Reserved for
future use
Description
Depth in feet below ground
surface to the top of the well
screen. This information is
required to obtain the vertical
location from which the
groundwater sample was
taken.
Leave null if well is not at this
location.
Depth in feet below ground
surface to bottom of well
screen. This information is
required to obtain the vertical
location from which the
groundwater sample was
taken.
Leave null if well is not at this
location.
Elevation of the top of casing
in feet.
Leave null if well is not at this
location.
This field is for by EPA
Region 2 future use. Please
leave null.
This field is for by EPA
Region 2 future use. Please
leave null.
This field is for by EPA
Region 2 future use. Please
leave null.
This field is for by EPA
Region 2 future use. Please
leave null.
This field is for by EPA
Region 2 future use. Please
leave null.
This field is for by EPA
Region 2 future use. Please
leave null.
Valid Values
In Appendix
No
No
No
No
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 34
United States
Environmental Protection Agency
-------
4. FORMATS FOR CHEMISTRY FILES
This section contains tables that define the file structures for the Chemistry EDD. The file structures
include chemistry sample, sample parameter, test/result QC, and Batch file. Please notice that some
columns are labeled as "Reserved for future use." These columns should simply be reported as null
values and are only needed to comply with standard EQuIS® reporting formats. Columns marked
"Required" must be reported for each row. If an EDD is submitted with one or more "Required" fields
not filled in, EPA will not be able to load the EDD into its database, and the EDD will have to be returned
to the data provider for correction(s). Columns marked "If available" should be filled in if at all possible.
4.1 Chemistry Sample EDD File
The Chemistry Sample EDD file contains data for samples collected at a site and location. The unique
identifier for each sample is recorded in the sys_sample_code. For trip blank samples, please record the
sys_sample_code as "TB" plus the date on which the sample was collected in MMDDYY format. For
example a trip blank collected on April 5, 2000 would have a sys_sample_code of TB040500. A
sys_sample_code of 'Trip Blank' is unacceptable because it cannot be distinguished from another trip
blank labeled the same way. For samples that are not associated with a specific sampling location, such
as trip blanks or field blanks, leave the sys_loc_code field (field 10) null. For surface water samples,
record the sample depths, start_depth (field 11) and end_depth (field 12), as depth below the water
surface elevation. The water surface elevation at the time of the sampling should be recorded in the
Water Level file (see Section 4.3). An example of a Chemistry Sample file is provided in Figure 2-4,
section 2.17.
Each Chemistry Sample file must be named according to the following convention:
SiteNameDate.EPAIDCode.Sample_v3.txt (or .csv)
Table 4-1 Chemistry sample file data structure
Pos#
1
2
o
J
4
5
Column Name
Data provider
sys_sample_code
sample_name
sample_matrix_code
sample_type_code
Data
Type
Text (20)
Text(40)
Text(30)
Text(3)
Text(3)
Required
Required
Required
If available
Required
Required
Description
Date provider company code
Unique sample identifier. Each sample at a
facility must have a unique value, including
spikes and duplicates. You have
considerable flexibility in the methods used
to derive and assign unique sample
identifiers; however, uniqueness throughout
the database is required.
Additional sample identification
information as necessary. Is not required to
be unique (i.e., duplicates are OK). Can be
the same value as in the sys sample code
field.
Code that identifies the matrix being
sampled, such as soil, groundwater, or
sediment. For acceptable valid values, see
Table A-l in the Appendix.
Code that distinguishes between different
types of samples, such as normal field
samples versus laboratory method blank
samples. For acceptable valid values see
Table A- 12 in the Appendix.
Valid Values
In Appendix
A-23
No
No
Table A-l
Table A-12
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 35
United States
Environmental Protection Agency
-------
Table 4-1 Chemistry sample file data structure
Pos#
6
7
8
9
10
Column Name
sample_source
parent_sample_code
sample_delivery_
group
sample_date
sys_loc_code
Data
Type
Text(lO)
Text(40)
Text(lO)
DateTime
Text(20)
Required
Required
Required for
field
duplicate
samples
If available
Required
Required*
Description
Identifies where the sample originated. Use
either "Field" or "Lab". Use "Field" for all
samples originating from the field and use
"Lab" if sample originated from the
laboratory.
Unique identifier of the original sample
from which the current sample was derived,
i.e. the "parent" sample. Required for
samples with a sample type code of "BD",
"FD", "FR", "FS", "LR", "MS", "MSD" or
"SD."
EPA and most EPA Region 2 data providers
are accustomed to using the Contract
Laboratory Program (CLP) document
definition of the sample delivery group
(SDG). However, the CLP definition of an
SDG relates to a lab payment group which
is not what is being asked for in this field.
For the purposes of this field in this EDD,
the value entered should correspond more to
the "sampling event/ matrix" with which the
sample is associated. For example, the
SDG for ground water samples should be
different from that for surface water
samples. This will prevent flags associated
with surface water matrix effects from
being propagated to ground water results
Date sample was collected in
MM/DD/YYYY HH:MM:SS format.
Sample collection location. Must be a valid
code for the facility and must match one of
the reported values in the sys loc code
field of the location EDD file (Table 3-2)
submitted in the current or previous EDD.
* Field should be null if sample is not
associated with a specific location, such as
QC samples (e.g., field blank, trip blank)
and this code cannot be the same as
sys sample code
Valid Values
In Appendix
Field
Lab
No
No
MM/DD/YYYY
HH:MM:SS
format.
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 36
United States
Environmental Protection Agency
-------
Table 4-1 Chemistry sample file data structure
Pos#
11
12
13
14
15
16
17
Column Name
start_depth
end_depth
depth_unit
chain_of_custody
sent_to_lab_date
sample_receipt_date
sampler
Data
Type
Number
w/decimal
precision
up to 15
Number
w/decimal
precision
up to 15
Text(15)
Text(40)
DateTime
DateTime
Text(30)
Required
If applic-
able
If applic-
able
If applic-
able
If available
If available
If available
If available
Description
Beginning depth (top) of sample in feet
below ground surface. For surface water
samples, use beginning depth below water
surface elevation. The water surface
elevation at the time sample was collected
should be reported in the Water Level
(GWTR) EDO file.
This field should be left null for most
ground water samples collected from
monitoring wells. The database will base
the start depth for groundwater samples on
the starting depth of the well screen as it is
listed in the well construction (WSG) and
well (WEL) EDO files.
Enter depth for groundwater samples only if
discrete samples are taken at different depth
elevations from a single well, i.e. multiple
well packer samples.
Ending depth (bottom) of sample in feet
below ground surface. For surface water
samples, use ending depth below water
surface elevation. The water surface
elevation at the time sample was collected
should be reported in the Water Level
(GWTR) EDO file.
This field should be left null for most
ground water samples collected from
monitoring wells. The database will base
the end depth for groundwater samples on
the end depth of the well screen as it is
listed in the well construction (WSG) and
well (WEL) EDO files.
Enter depth for groundwater samples only if
discrete samples are taken at different depth
elevations from a single well, i.e. multiple
well packer samples.
Unit of measurement for the sample
beginning and end depths. For valid values,
see Table A- 18 in the Appendix.
Chain of custody identifier. A single sample
may be assigned to only one chain of
custody.
Date sample was sent to lab in
MM/DD/YYYY format.
Date that sample was received at laboratory
in MM/DD/YYYY format.
Name or initials of sampler.
Valid Values
In Appendix
No
No
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 37
United States
Environmental Protection Agency
-------
Table 4-1 Chemistry sample file data structure
Pos#
18
19
20
21
22
23
24
25
26
27
28
29
Column Name
sampling_company_c
ode
sampling_reason
sampling technique
task_code
collection_quarter
composite_yn
composite_desc
sample_class
custom_field_l
custom_field_2
custom_field_3
comment
Data
Type
Text(lO)
Text(30)
Text(40)
Text(20)
Text(5)
Text(l)
Text(255)
Text(lO)
Text (20)
Text(50)
Text(50)
Text(255)
Required
Required
Reserved for
future use
If available
If available
Reserved for
future use
Required
If available
Reserved for
future use
Reserved for
futurn use
Reserved for
future use
Reserved for
future use
If available
Description
Name or initials of consulting company
performing sampling. (This field does not
have a controlled vocabulary, i.e., there is
no table of valid values for this field.)
Reason for Sampling
Sampling technique.
Code used to associate individual samples
to a specific sampling event. The format for
this field is XX-P#-, where XX is the type
of task required (PR = Pre Remedial, RI =
Remedial Investigation, FS = Feasibility
Study, PD = Pre-Design, RD = Remedial
Design, RA = Remedial Construction, PC =
Post Construction, RM = Removal Action,
BD = Before Dredge, AD = After Dredge,
BR = Brown Fields, SP = Special Project);
P# is the phase; For example, if sampling
was performed for a Phase 1 Post
Construction site, the task code would be
PC-PI
Report as null.
Is sample a composite sample? Enter "Y"
for yes or "N" for no.
Description of composite sample. If sample
is not a composite, leave this field null.
Report as null.
Report as null.
Report as null.
Report as null.
Any comments regarding the sample.
Valid Values
In Appendix
No
No
No
No
No
Y=Yes
N=No
No
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 38
United States
Environmental Protection Agency
-------
4.2 Chemistry Sample Parameter EDD Files
The Chemistry Sample Parameter (SampleParameter) EDD files contain data relating data associated with
a sample sent to a lab.
Each Sample Parameter EDD file must be named according to the following convention:
SiteNameDate.EPAIDCode.SampleParameter_v3.txt (or .csv)
Table 4-2 Chemistry Sample Parameter file data structure
Pos#
1
2
o
5
4
5
6
7
Column Name
sys_sample_code
Param code
Measurement_date
Param_unit
Param_value
Measurement meth
od
Remark
Data Type
Text(40)
Text(20)
DateTime
Text (15)
Text (255)
Text (20)
Text (2000)
Required
Required
Required
Required
If available
Description
Sample identifier of the sample that was
tested and analyzed. Must match one of
the reported values in the
sys_sample_code field of the Sample_v3
file submitted in the current or previous
EDD.
Uique code for sample parameter type
Date of sample parameter measurement in
MM/DD/YYYY HH:MM:SS format.
Unit of measurement for subsample
amount.
Sample parameter value.
Measurement method
Parameter measurement specific
comment.
Valid Values
In Appendix
Table A-18
No
4.3 Chemistry Test/Result with QC Data EDD File
The Chemistry test/results with QC (TRSQC) EDD file contains data from analytical tests performed on
samples along with quality control data.
Each Chemistry test/results with QC EDD file must be named according to the following convention:
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 39
United States
Environmental Protection Agency
-------
SiteNameDate.EPAIDCode.TestResultQC_v3.txt (or .csv)
Table 4-3 Chemistry test/results with QC data file structure
Pos#
1
2
3
4
5
6
7
8
9
10
Column Name
sys_sample_code
lab_anl_method_
name
analysis_date
total_or_dissolved
column number
test type
lab_matrix_code
analysis_location
Basis
container_id
Data
Type
Text(40)
Text(35)
DateTime
Text(l)
Text(2)
Text(lO)
Text(3)
Text(2)
Text(lO)
Text(30)
Required
Required
Required
Required
Required
Required
Required
Required
Required
Required
Reserved for
future use
Description
Sample identifier of the sample that
was tested and analyzed. Must match
one of the reported values in the
sys_sample_code field of the
Sample_v3 file submitted in the current
or previous EDD.
Laboratory analytical method name or
description. For acceptable valid
values. Default to "Unknown" if data
is unavailable.
Date of sample analysis in
MM/DD/YYYY HH:MM:SS format.
May refer to either beginning or end of
the analysis. For measurements taken
in the field (e.g., pH, dissolved
oxygen), use the same date as sample
date
Must be either "D" for dissolved or
filtered [metal] concentration, or "T"
for everything else.
Column number, if null, "NA" will be
placed in this field
Type of test.
Code that identifies the matrix, such as
soil, groundwater, and sediment.
The matrix of the sample when it is
analyzed may be different from the
matrix of the sample when it is
collected (e.g. leachates), so this field
is available at both the sample and test
level.
Must be either "FI" for field instrument
or probe (i.e, "in the field"
measurements such as pH, temperature,
conductivity, and dissolved oxygen),
"FL" for mobile field laboratory
analysis, or "LB" for an analysis done
at a fixed-based laboratory.
Must be either "Wet" for wet-weight
basis reporting, "Dry" for dry-weight
basis reporting, or "NA" for tests for
which this distinction is not applicable.
EPA prefers that results are reported on
the basis of dry weight where
applicable.
Report as null.
Valid Values
In Appendix
Table A-16
A-24
No
A-25
Table A-l
FI = Field
Instrument
FL = Mobile
Field lab
LB = Fixed
based lab
Wet= wet-
weight
Dry=dry
weight
N/A = not
applicable
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 40
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC data file structure
Pos#
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Column Name
dilution_factor
prep_method
prep_date
leachate_method
leachate_date
lab_name_code
qc_level
lab_sample_id
percent_moisture
subsample amount
subsample_amount_uni
t
analyst_name
instrament_id
Comment
Preservative
final volume
final_volume_unit
Data
Type
Number
w/decimal
precision
up to 7
Text(35)
DateTime
Text(15)
DateTime
Text(20)
Text(lO)
Text(20)
Text(5)
Text(14)
Text(15)
Text(30)
Text(50)
Text(255)
Text(20)
Numeric
Text(15)
Required
Required
If available
If available
Required if
leached
Required if
leached
Required
Required
Required
If available
If available
If available
Reserved for
future use
Reserved for
future use
If available
If available
If available
If available
Description
Effective test dilution factor.
Laboratory sample preparation method
name or description. Must use valid
value from Table A- 14 in the
Appendix.
Beginning date of sample preparation.
Laboratory leachate generation method
name or description. The method name
should be sufficient to reflect the
operation methodology used by the
laboratory (see analysis method
discussion).
Beginning date of leachate preparation
Unique identifier of the laboratory as
defined by the EPA. Controlled
vocabulary;
May be either "screen" for screening
data or "quant" For quantitative data.
Default value is "quant."
Laboratory LIMS sample identifier. If
necessary, a field sample may have
more than one LIMS lab_sample_id
(maximum one per each test event).
Percent moisture of the sample portion
used in this test; this value may vary
from test to test for any sample.
Numeric format is "NN.MM," i.e.,
70.1% could be reported as "70.1" but
not as "70.1%."
Amount of sample used for test.
Unit of measurement for subsample
amount. Must use valid value from
Table A- 18 in the Appendix.
Report as null.
Report as null.
Comments about the test, if necessary.
Sample preservative used.
The final volume of the sample after
sample preparation. Include all dilution
factors.
The unit of measure that corresponds to
the final amount.
Valid Values
In Appendix
No
Table A-14
MM/DD/YYY
Y HH:MM:SS
format
No
MM/DD/YYY
YHH:MM:SS
format
Table A-17
Screen =
screening
Quant =
quantitative
No
No
No
Table A- 18
No
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 41
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC data file structure
Pos#
28
29
30
31
32
33
34
35
36
37
Column Name
cas rn
chemical name
Result_value
Result_error_delta
Result_type_code
reportable_result
detect_flag
Lab_qualifiers
validator_qualifiers
Interpreted_qualifiers
Data
Type
Text(15)
Text(75)
Numeric
Text(20)
Text(lO)
Text(lO)
Text(2)
Text(lO)
Text(lO)
Text(lO)
Required
Required
Required
Required *
If available
Required
Required
Required
If available
If available
If available/
Required
Description
Analyte code..
Chemical name.
Analytical result reported at an
appropriate number of significant
digits. May be blank for non-detect
results.
* Required if detect_flag = "Y" and
result type code is "TRG" or "TIC".
Error range applicable to the result
value; typically used only for
radiochemistry results.
Must be either "TRG" for a target or
regular result, "TIC" for a tentatively
identified compound, "SUR" for
surrogates, "IS" for internal standards,
or "SC" for spiked compounds. Use
"TRG" for measurements taken from
the field (e.g., pH, dissolved oxygen)
Must be either "Yes" for results that are
considered to be reportable, or "No" for
other results. This field has many
purposes. For example, it can be used
to distinguish between multiple results
where a sample is retested after
dilution. It can also be used to indicate
which of the first or second column
result should be considered primary.
The proper value of this field in both of
these two examples should be provided
by the laboratory.
Maybe either "Y" for detected analytes
or "N" for non-detects. "Y" should be
used for detected target compounds and
TICs only (i.e. result type code is
"TRG" or "TIC").
Also use "Y" for estimated (above
detection limit but below the
quantitation limit) or ">" and "<" for
tests such as flash point. Note that "<"
must not be used to indicate non-
detects.
Qualifier flags assigned by the
laboratory.
Qualifier flags assigned by the person
who validates the laboratory data..
Interpreted qualifier flag assigned by
the data provider. The interpret
qualifier is required if lap_qualifer or
validator qualifier are populated
Valid Values
In Appendix
Table A-15
Table A-15
No
No
No
Yes
No
Y= detected
N = non-
detects
No
No
A-10
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 42
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC data file structure
Pos#
38
39
40
41
42
43
44
45
46
47
48
49
50
Column Name
Validator_qualifiers
method_detection_limit
reporting_detection_lim
it
quantitation_limit
Result_unit
detection_limit_
unit
tic_retention_time
Minimum_detectable_c
one
Counting_error
Uncertainty
Critical_value
Validation_level
result comment
Data
Type
Text (1)
Text(20)
Numeric
Text(20)
Text(15)
Text(15)
Text(8)
Numeric
Numeric
Text (10)
Numeric
Text (20)
Text(255)
Required
Required
If available
Required if
detect flag
= N
If available
Required if
result_value
is NOT null
Required if
detect flag
= N
Reserved for
future use
If available
If available
Required if
counting_err
or is
populated
If available
Reserved for
future use
If available
Description
Must be either "Y" for validate or "N"
for not validate.
Report as null. The minimum
concentration of an analyte that can be
measured and reported with 99%
confidence that the analyte
concentration is greater than zero, as
determined for a specific procedure.
Must be reported if sample result is
"non-detect." The minimum
concentration of an analyte that can be
measured and reported with 99%
confidence that the analyte
concentration is greater than zero, as
determined for a specific procedure,
which is equal to or greater than the
MDL.
Concentration level above which
results can be quantified with
confidence. The value must reflect
conditions such as dilution factors and
moisture content, and must be sample
specific.
Units of measurement for the result.
Must use valid values from Table A- 18
in the Appendix.
Units of measurement for the detection
limit(s). Must use valid value from
Table A- 18 in the Appendix.
Report as null.
Minimum detectable concentration or
activity. This value should be in the
same units as the result value.
Counting error as reported by the
laboratory. This value should be in the
same units as the result value.
The uncertainty of the counting error,
value values include "1 sigma" or "2
sigma". This field is required if the
counting error field is populated
Critical value as reported by the
laboratory.
EPA defined validation level
Result specific comments.
Valid Values
In Appendix
Y= organic
N=inorganic
No
No
No
Table A- 18
Table A- 18
No
No
No
"1 sigma" , "2
sigma"
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 43
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC data file structure
Pos#
51
52
53
54
55
56
Column Name
qc_original_conc
qc_spike_added
qc_spike_measured
qc_spike_recovery
qc_dup_original_
cone
qc_dup_spike_
added
Data
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Required
If applicable
If
Applicable
If applicable
If applicable
If applicable
If applicable
Description
The concentration of the analyte in the
original (unspiked) sample. Might be
required for spikes and spike duplicates
(depending on user needs). Not
necessary for surrogate compounds or
LCS samples (where the original
concentration is assumed to be zero).
The concentration of the analyte added
to the original sample. Might be
required for spikes, spike duplicates,
surrogate compounds, LCS and any
spiked sample (depending on user
needs).
The measured concentration of the
analyte. Use zero for spiked
compounds that were not detected in
the sample. Might be required for
spikes, spike duplicates, surrogate
compounds, LCS and any spiked
sample (depending on user needs).
The percent recovery calculated as
specified by the laboratory QC
program. Always required for spikes,
spike duplicates, surrogate compounds,
LCS and any spiked sample. Report as
percentage multiplied by 100 (e.g.,
report "120%" as "120").
The concentration of the analyte in the
original (unspiked) sample. Might be
required for spike or LCS duplicates
only (depending on user needs). Not
necessary for surrogate compounds or
LCS samples (where the original
concentration is assumed to be zero).
The concentration of the analyte added
to the original sample. Might be
required for spike or LCS duplicates,
surrogate compounds, and any spiked
and duplicated sample (depending on
user needs). Use zero for spiked
compounds that were not detected in
the sample. Required for spikes, spike
duplicates, surrogate compounds, LCS
and any spiked sample. Also complete
the qc-spike-added field.
Valid Values
In Appendix
No
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 44
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC data file structure
Pos#
57
58
59
60
61
62
63
Column Name
qc_dup_spike_
measured
qc_dup_spike_
recovery
qc_rpd
qc_spike_lcl
qc_spike_ucl
qc_rpd_cl
qc_spike_status
Data
Type
Numeric
Numeric
Text(8)
Text(8)
Text(8)
Text(8)
Text(lO)
Required
If applicable
If applicable
If applicable
If applicable
If applicable
If applicable
If applicable
Description
The measured concentration of the
analyte in the duplicate. Use zero for
spiked compounds that were not
detected in the sample. Might be
required for spike and LCS duplicates,
surrogate compounds, and any other
spiked and duplicated sample
(depending on user needs). Also
complete the qc spike measured field.
The duplicate percent recovery
calculated as specified by the
laboratory QC program. Always
required for spike or LCS duplicates,
surrogate compounds, and any other
spiked and duplicated sample. Also
complete the qc_spike_recovery field.
Report as percentage multiplied by 100
(e.g., report "120%" as "120").
The relative percent difference
calculated as specified by the
laboratory QC program. Required for
duplicate samples as appropriate.
Report as percentage multiplied by 100
(e.g., report "30%" as "30").
Lower control limit for spike recovery.
Required for spikes, spike duplicates,
surrogate compounds, LCS and any
spiked sample. Report as percentage
multiplied by 100 (e.g., report "60%" as
"60").
Upper control limit for spike recovery.
Required for spikes, spike duplicates,
surrogate compounds, LCS and any
spiked sample. Report as percentage
multiplied by 100 (e.g., report "120%"
as "120").
Relative percent difference control
limit. Required for any duplicated
sample. Report as percentage
multiplied by 100 (e.g., report "25%" as
"25").
Used to indicate whether the spike
recovery was within control limits. Use
the "*" character to indicate failure,
otherwise leave blank. Required for
spikes, spike duplicates, surrogate
compounds, LCS and any spiked
sample.
Valid Values
In Appendix
No
No
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 45
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC data file structure
Pos#
64
65
66
Column Name
qc_dup_spike_
status
qc_rpd_status
Lab_SDG
Data
Type
Text(lO)
Text(lO)
Text (20)
Required
If applicable
If applicable
Description
Used to indicate whether the duplicate
spike recovery was within control
limits. Use the "*" character to indicate
failure, otherwise leave blank. Required
for any spiked and duplicated sample.
Used to indicate whether the relative
percent difference was within control
limits. Use the "*" character to indicate
failure, otherwise leave blank. Required
for any duplicated sample.
Lab Sample Delivery Group (SDG)
identifier. A single sample may be
assigned to multiple Sample Delivery
Group (SDG) based on different
analysis.
Valid Values
In Appendix
No
No
No
4.4 Chemistry Batch Data EDO File
The Chemistry Batch (BATCH) EDD file contains data that relate the individual samples to the
laboratory batch identifier. For the most part, as with the TestResultQC EDD file, the BATCH EDD file
will only need to be submitted by EPA contractors that are submitting quality data elements with their
reports. The purpose of this EDD file is so laboratory quality control samples can be associated with the
correct field samples with which they were processed and analyzed. This EDD file has been structured to
allow samples to have different batch IDs for various phases of analysis (e.g., preparation phase, analysis
phase). The majority of samples will only have one batch ID assigned by the laboratory. It is important
that the values in the sys_sample_code, lab_anl_method_name, analysis_date, analysis_time,
total_or_dissolved and testjype fields match those found in the TestResultQC EDD files. Each
Chemistry batch file must be named according to the following convention:
SiteNameDate.EPAIDCode.EPAR2BAT _v2.txt (or .csv)
Table 4-4 Chemistry batch file data structure
Pos#
1
2
o
3
4
Column Name
sys_sample_code
lab_anl_method_
name
analysis_date
total_or_dissolved
Data type
Text(40)
Text(35)
Datetime
Text(l)
Required
Required
Required
Required
Required
Description
Sample identifier of the sample that was
tested and analyzed. Must match one of
the reported values in the
sys_sample_code field of the Sample_v3
file (Table 4-1) submitted in the current
or previous EDD.
Laboratory analytical method name or
description. For acceptable valid values,
see Table A-16 in the Appendix. Default
to "Unknown" if data is unavailable.
Date of sample analysis. May refer to
either beginning or end of the analysis.
Must be either "D" for dissolved or
filtered [metal] concentration; should be
"T" for everything else
Valid Values
In Appendix
No
Table A-16
MM/DD/YYYY
HH:MM:SS
format.
A-24
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 46
United States
Environmental Protection Agency
-------
Pos#
5
6
7
8
Column Name
column_number
test_type
test_batch_type
test batch id
Data type
Text(2)
Text(lO)
Text(8)
Text(20)
Required
Reserved
for future
use
Required
Required
Required
Description
Report as null.
Type of test.
Lab batch type.
This is a required field for all batches.
Unique identifier for all lab batches.
Valid Values
In Appendix
No
A-25
A-26
No
5. FORMATS FOR FIELD FILES
This section contains tables that define the file structures for the FIELD EDD. The file structures include
drilling activity, lithology, well, well construction, geology samples, water table, down hole point, Soil
Gas, Water level, extraction injection wells, and field results data . The columns marked "Required" must
be reported for each row in the file. If an EDD is submitted with one or more "Required" fields not filled
in, EPA will not be able to load the EDD into its database, and the EDD will have to be returned to the
data provider for correction(s). The columns marked "If available" should also be reported whenever
possible. Examples of the EDD files that make up the Field EDDs are provided in Figure 2-6, section
2.17.
5.1 Drill Activity EDD File
The drill activity (DRA) EDD file contains general information pertaining to the drilling activities
resulting from the soil boring. Each drill activity file must be named according to the following
convention:
SiteNameDate.EPAIDCode.DrillActivity v3.txt (or .csv)
Table 5-1 Drill activity file data structure
Pos#
1
2
o
3
4
5
Column Name
sys_loc_code
drill_event
start_depth
end_depth
start_date
Data
Type
Text (20)
Text (20)
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Date Time
Required
Required
Required
If
available
If
available
If
available
Description
Soil boring or well installation location.
Must be a valid code for the facility and
must match one of the reported values in the
sys_loc_code field of the location EDD file
(Table 3-2) submitted in the current or
previous EDD.
Used to identify drilling event Examples of
drilling events could be "initial" for initial
drilling or "second" for a subsequent
drilling at the same sys loc code .
The start depth, in feet below ground
surface, of the drilling.
End depth, in feet below ground surface of
the drilling.
Date drilling began
Valid Values
In Appendix
No
No
No
No
MM/DD/YYYY
format.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 47
United States
Environmental Protection Agency
-------
Pos#
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Column Name
Diameter
diameter_unit
drill_method
fluid
viscosity
hammer_wt
hammer fall
lift_mechanism
new_yn
repair_yn
deepen_yn
abandon_yn
replace_yn
public_yn
Purpose
Data
Type
Number
w/decimal
precision
up to 7
Text (15)
Text (50)
Text (50)
Text (50)
Text (50)
Text (50)
Text (50)
Text (1)
Text (1)
Text (1)
Text (1)
Text (1)
Text (1)
Text (70)
Required
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
Description
Diameter of boring.
Unit corresponding to measured diameter.
See Table A- 18 in the Appendix for
appropriate value.
Method used to drill boring.
Description of fluid used during drilling.
Viscosity of drilling fluid.
Weight of hammer, in pounds, used for
sampling.
Distance of hammer fall during sampling in
inches.
Type of mechanism used to lift hammer.
This field is to indicate whether this is a
new boring. Enter "Y" for yes or "N" for
no.
Is this drilling event to repair an existing
boring? "Y" for yes or "N" for no.
Is this drilling event to deepen an existing
boring? "Y" for yes or "N" for no.
Has the boring been abandoned? "Y" for
yes or "N" for no.
Is this boring event to replace an existing
boring? "Y" for yes or "N" for no.
Is well being install for a public use? "Y"
for yes or "N" for no.
Describe the purpose of the boring event.
Valid Values
In Appendix
No
Table A- 18
No
No
No
No
No
No
Y = yes
N= no
Y = yes
N= no
Y = yes
N= no
Y = yes
N= no
Y = yes
N= no
Y = yes
N= no
No
5.2 Lithology EDO File
The lithology (LTH) EDD file contains all the lithology data for soil borings. For each lithologic unit, 16
fields are available for populating with data about the boring. Optional comments can be recorded in the
remark 1 and remark2 fields to describe depth-specific observations within a lithologic unit. Each
lithology EDD file must be named according to the following convention:
SiteNameDate.EPAIDCode.Lithology_v3.txt (or .csv)
Table 5-2 Lithology file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Valued
In Appendix
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 48
United States
Environmental Protection Agency
-------
Table 5-2 Lithology file data structure
Pos#
1
2
o
3
4
5
6
7
8
9
10
11
12
13
14
15
Column Name
sys_loc_code
start_depth
material_type
geo_unit_code_l
geo_unit_code_2
remark 1
remark_2
Moisture
Permeable
consolidated_yn
Color
Observation
Consistency
Sorting
Grainsize
Data
Type
Text(20)
Number
w/decimal
precision
up to 15
Text(40)
Text(20)
Text(20)
Text(255)
Text(255)
Text(l)
Text(20)
Text(l)
Text(30)
Text(255)
Text(20)
Text(20)
Text(20)
Required
Required
Required
Required
if
geo unit
null
If
available
If
available
if applic-
able
if applic-
able
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
Description
Soil boring or well installation location.
Must be a valid code for the facility and
must match one of the reported values in
the sys_loc_code field of the location
EDO file (Table 3-2) submitted in the
current or previous EDD.
The start depth, in feet below ground
surface, of the lithologic unit.
The type of material that composes the
lithologic unit. See Table A- 19 in the
Appendix for appropriate values.
The data provider's interpretation of the
hydrogeologic unit present at this
lithologic unit, e.g., aquifer 1, aquitard 1,
aquifer 2, upper clay unit. See Figure A-
2 in the Appendix for examples.
Alternate geologic unit grouping. This
can be a sub-classification of
geologic_unit_code_l or a layer used for
groundwater flow/transport computer
modeling that contains the lithologic unit.
See Figure A-2 in the Appendix for
examples.
Comments (if any) on the lithologic unit.
Additional comments on the lithologic
unit.
Was any moisture detected within the
lithologic unit? "Y" for yes or "N" for no.
Description of the permeability of the
lithologic unit such as "impervious,"
"semi," "pervious," or "very."
Was lithologic unit consolidated? "Y" for
yes or "N" for no.
Color of the lithologic unit.
General field observations of the
lithologic unit.
Description of the consistency of the soil,
such as "very soft," "soft," "firm," "hard"
or "very hard."
Geologic description of the grain size
distribution of the lithologic unit. Use
"poor" for soil with a wide range of
particle sizes or "well" for soil with a
narrow range of particle sizes.
Description of grain size.
Valid Valued
In Appendix
No
No
Table A- 19
No
No
No
No
Y = yes
N=No
No
Y=yes
N=no
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 49
United States
Environmental Protection Agency
-------
Table 5-2 Lithology file data structure
Pos#
16
Column Name
Odor
Data
Type
Text(20)
Required
If
available
Description
Description of odor from the soil.
Valid Valued
In Appendix
No
5.3 Well EDO File
The well (WEL) EDD file contains general information relating to well installation. Each well file must
be named according to the following convention:
SiteNameDate.EPAIDCode.Well_v3.txt (or .csv)
Table 5-3 Well file data structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
12
13
Column
Name
sys_loc_code
Well_id
well_descripti
on
well owner
well_purpose
well status
top_casing_
elev
datum_value
datum unit
datum_desc
step_or_linear
start_date
datum_collect
_method_code
Data
Type
Text(20)
Text(30)
Text(30)
Text(30)
Text (20)
Text (20)
Number
w/decimal
precision
up to 15
Number
w/decimal
precision
up to 15
Text(15)
Text (70)
Text (6)
DateTime
Text (2)
Required
Required
If available
If applic-
able
If available
If available
If available
If available
Required
Required
Required
If available
Required
If available
Description
Well installation location Must be a valid
code for the facility and must match one of
the reported values in the sys_loc_code
field of the location EDD file (Table 3-2)
submitted in the current or previous EDD.
Well identification number
Used for additional well description if
necessary.
Name of entity that owns the well.
Purpose of well.
Current status of well.
Elevation of the top of well casing.
Elevation must be in feet.
Elevation of datum used to reference
measurement of water level depths. (EPA
normally uses top of well casing for datum.)
Unit of measure for the well datum..
Description of the datum, such as "top of
well casing."
Use only for re-surveys of well elevations.
If a section of the well casing was removed
or added use "step" as the value. If nothing
was added or removed from the last survey,
use "linear" as the value.
Date that datum was first used to take
measurements.
Method used to determine the datum
elevation. Use codes from Table A-6 in the
Appendix
Valid Value
In Appendix
No
No
No
No
No
No
No
No
Table A- 18
No
No
MM/DD/YYYY
format.
Table A-6
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 50
United States
Environmental Protection Agency
-------
Table 5-3 Well file data structure
Pos#
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Column
Name
depth_of_well
depth unit
depth_measure
method
stickup height
stickup unit
sump length
sump unit
Installation_da
te
construct_start
date
construct_com
plete date
construct_
contractor
pump_type
pump capacity
pump_unit
pump_yield
pump_yield_
method
weep_hole
head_configur
ation
access_port_y
n
casingjoint_t
ype
Perforator use
d
intake_depth
Disinfected_yn
historical_
reference_elev
Data
Type
Number
w/decimal
precision
up to 15
Text (15)
Text (20)
Text (8)
Text (15)
Text (20)
Text (15)
Date
DateTime
DateTime
Text (20)
Text (20)
Text (6)
Text (15)
Text (6)
Text (20)
Text (1)
Text (50)
Text (1)
Text (50)
Text (50)
Number
w/decimal
precision
up to 15
Text (1)
Number
w/decimal
precision
up to 15
Required
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
If available
Reserved for
future use
Description
Depth below ground surface of the well
bottom.
Unit of measurement for depth.
Method of measuring depth of well.
Height of casing above ground surface.
Unit of measure for the stickup height
Length of sump.
Unit of measure for the sump length. .
Date of well installation
Date well construction began
Date well construction was completed
Name of contractor that installed well.
Type of pump used at well such as
centrifugal, propeller, jet, helical, rotary,
etc.
Capacity of pump.
Unit of measure for the pump capacity and
yield.
The yield of the pump.
Method used for pump yield.
Is there a weep hole? "Y" for yes or "N" for
no.
Description of the well-head.
Is there an access port? "Y" for yes or "N"
for no.
Type of casing joint, such as "threaded,"
"flush," or "solvent-welded."
Description of well perforation, such as
"slotted," "drilled," or "wound."
Depth in feet below ground surface of the
well intake.
Was well disinfected? "Y" for yes or "N"
for no.
Leave null .
Valid Value
In Appendix
No
Table A- 18
No
No
Table A- 18
No
Table A- 18
MM/DD/YYYY
format.
MM/DD/YYYY
format.
MM/DD/YYYY
format.
No
No
No
Table A-18
No
No
Y=yes
N=No
No
Y=yes
N=No
No
No
Feet
Y=yes
N=No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 51
United States
Environmental Protection Agency
-------
Table 5-3 Well file data structure
Pos#
38
39
Column
Name
geologic_unit_
code
Remark
Data
Type
Text (20)
Text (255)
Required
If available
If available
Description
Geologic unit in which the well intake is
installed.
Available for general remarks.
Valid Value
In Appendix
No
No
5.4 Well Construction EDO File
The well construction (WSG) file contains information relating to well construction and well segments.
Information is required for all well segments within each well, including surface plug, protective casing,
well casing, annular backfill, annular seal, screen, and filter pack. In order to obtain the depth of
groundwater samples, it is particularly important that the depths of the top and bottom of the well screen
be submitted for each well. Each well construction EDD file must be named according to the following
convention:
SiteNameDate.EPAIDCode.WellConstruction_v3.txt (or .csv)
Table 5-4 Well construction file data structure
Pos#
1
2
o
J
4
5
6
7
8
9
Column
Name
sys_loc_code
segment_type
material_type_
code
start_depth
end_depth
depth unit
inner_diameter
outer_diameter
diameter_unit
Data
Type
Text(20)
Text(20)
Text(20)
Number
w/decimal
precision
up to 15
Number
w/decimal
precision
up to 15
Text(15)
Number
w/decimal
precision
up to 15
Number
w/decimal
precision
up to 15
Text(15)
Required
Required
Required
Required
Required
Required
Required
If
available
If
available
If
available
Description
Well installation location. Must be a valid
code for the facility and must match one
of the reported values in the sys_loc_code
field of the location EDD file (Table 3-2)
submitted in the current or previous EDD.
Type of segment within well (e.g.,
protective casing, well casing, screen,
etc.).
Material description of well segment. Use
values.
Depth, in feet below ground surface, of
the top of the described segment
Depth, in feet below ground surface, of
the bottom of the described segment.
The unit of depth measurements.
The inside diameter of the described
segment.
The outside diameter of the described
segment.
The unit of diameter measurements
Valid Value
In Appendix
No
Table A-20
Table A-20
No
No
Table A-18
No
No
Table A-18
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 52
United States
Environmental Protection Agency
-------
Table 5-4 Well construction file data structure
Pos#
10
11
12
13
14
15
16
17
18
19
Column
Name
Thickness
thickness unit
slot_type
slot_size
slot_size_unit
perf_length
screen_type
material_quant
ity
material_densi
ty
Remark
Data
Type
Number
w/decimal
precision
up to 15
Text(15)
Text(20)
Number
w/decimal
precision
up to 15
Text(15)
Number
w/decimal
precision
up to 15
Text(15)
Text(20)
Text(20)
Text(255)
Required
If
available
If
available
if applic-
able
if applic-
able
if applic-
able
if applic-
able
if applic-
able
If
available
If
available
If
available
Description
Thickness of the described well segment.
The unit of measurement for thickness.
Type of slots in screen segment such as
bridge, shutter, and continuous.
Width of slots.
The unit of measurement for slot size..
Length of perforated portion of screen in
feet.
Type of screen.
Quantity of material used in pounds.
Applicable to annular seal/fill material.
Density of the annular seal material in
lbs/ft3.
Remarks regarding the segment.
Valid Value
In Appendix
No
Table A- 18
No
No
Table A-18
No
No
No
No
No
5.5 Geology Samples EDO File
The Geology Samples (GSMP) EDD file contains geotechnical sample information. (Samples results
related to chemical analyses should be reported using the Chemistry EDD.) Each Geology sample EDD
file must be named according to the following convention:
SiteNameDate.EPAIDCode.GeologySamples_v3.txt (or .csv)
Table 5-5 Geology samples file data structure
Pos#
1
Column
Name
sys_loc_code
Data
Type
Text(20)
Required
Required
Description
Sample collection location. Must be a
valid code for the facility and must match
one of the reported values in the
sys_loc_code field of the location EDD
file (Table 3-2) submitted in the current
or previous EDD.
Valid Values
In Appendix
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 53
United States
Environmental Protection Agency
-------
Table 5-5 Geology samples file data structure
Pos#
2
o
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Column
Name
geo_sample_
code
sample_name
sample_top
sample_
bottom
sampling_date
sample_
method
material_type
sample_desc
geologic_
unit code
liquid_limit
plastic_limit
shrinkage_
limit
flow_index
plasticity_
index
Activity
Data
Type
Text(40)
Text(50)
Number
w/decimal
precision
up to 15
Number
w/decimal
precision
up to 15
DateTime
Text(30)
Text(40)
Text(255)
Text(20)
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Required
Required
If
available
Required
Required
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
Description
Unique sample identifier. Considerable
flexibility is given in the methods used to
derive and assign unique sample
identifiers, but uniqueness throughout the
database is the only restriction enforced.
Use to provide a name or description of
sample. Does not have to be a unique
throughout database.
Depth, in feet below ground surface, to
top of sample.
Depth, in feet below ground surface, to
bottom of sample.
Date sample was collected.
Method used to obtain sample, e.g., split
spoon or Shelby tube.
Material type of geologic sample. .
General description of the sample or
sampling activities.
Code used to identify the geologic unit of
the sample.
Liquid limit (LL) of the sample.
Plastic Limit (PL) of the sample.
Shrinkage limit of the sample.
Flow index of the sample.
Plasticity index of the sample.
Activity of the sample.
Valid Values
In Appendix
No
No
No
No
MM/DD/YYYY
HH:MM:SS
format
No
Table A-19
No
No
No
No
No
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 54
United States
Environmental Protection Agency
-------
Table 5-5 Geology samples file data structure
Pos#
17
18
19
20
21
22
23
24
25
26
27
28
29
Column
Name
E
e_max
e_min
N
specific_
gravity
W
opt_w
S
K
K_unit
unit_wt
sat_unit_wt
dry_unit_wt
Data
Type
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Text(15)
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Required
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
Description
Void ratio of the sample.
Maximum void ratio of the sample.
Minimum void ratio of the sample.
Porosity of the sample.
Specific gravity of the sample.
Water content of the sample.
Optimum water content.
Degree of saturation of the sample.
Hydraulic conductivity of the sample.
Unit of measure for K. .
Unit weight of the sample.
Saturated unit weight of the sample.
Dry unit weight of the sample.
Valid Values
In Appendix
No
No
No
No
No
No
No
No
No
Table A-18
No
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 55
United States
Environmental Protection Agency
-------
Table 5-5 Geology samples file data structure
Pos#
30
31
32
33
34
35
36
37
Column
Name
dry_unit_wt_
max
dry_unit_wt_
mm
density_unit
rel_density
rel
compaction
Consistency
organic_
carbon
organic_
carbon unit
Data
Type
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Text(15)
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Text (20)
Number
w/decimal
precision
up to 7
Text (15)
Required
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
Description
Maximum dry unit weight of the sample.
Minimum dry unit weight of the sample.
Unit of measure for the densities of the
sample.
Relative density of the sample.
Relative compaction of the sample.
Description of the consistency of the soil
sample such as very soft, soft, firm, hard
or very hard.
Organic carbon content of sample.
Unit of measurement of organic content.
Use values from Table A- 18 of the
Appendix.
Valid Values
In Appendix
No
No
Table A-18
No
No
No
No
No
5.6 Water Table EDO Files
The water table (TBL) EDD file stores data pertaining the water table and is used to record groundwater
data during drilling activities. Each water table EDD file must be named according to the following
convention:
SiteNameDate.EPAIDCode.WaterTable_v3.txt (or .csv)
Table 5-6 Water table file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 56
United States
Environmental Protection Agency
-------
Table 5-6 Water table file data structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
12
Column
Name
sys_loc_code
Type
Sequence
Depth
flowing_yn
measurement_
method
capped_pressu
re
capped_pressu
re_
unit
reference_poin
t
reference_elev
ation
Temperature
temperature_u
nit
Data
Type
Text (20)
Text (20)
Text (20)
Number
w/decimal
precision
up to 15
Text (1)
Text (50)
Number
w/decimal
precision
up to 15
Text (15)
Text (50)
Number
w/decimal
precision
up to 15
Number
w/decimal
precision
up to 15
Text (15)
Required
Required
Required
Required
Required
If available
If available
If available
If available
If available
Required
If available
If available
Description
Soil boring or well installation location.
Must be a valid code for the facility and
must match one of the reported values in
the sys_loc_code field of the location
EDO file (Table 3-2) submitted in the
current or previous EDD.
Aquifer designation, such as unconfinedl,
confinedl, orconfined2.
Designation of when water level
measurement was taken. Use
"unstabilized" if measurement was taken
before water stabilized and use
"stabilized" if measurement taken after
stabilization.
Depth of water table, in feet, below
reference point.
Is the water table flowing? " Y" for yes or
"N" for no.
Method of measuring water table depth.
Hydrostatic pressure of confined aquifer.
Unit of measure for capped pressure. Use
values from Table A- 18 in the Appendix.
Description of reference point from which
depth measurements were taken.
Elevation of the reference point from
which depth measurement were taken.
Elevation must be in feet.
Temperature of water in the water table.
Unit of temperature. Use values from
Table A- 18 in the Appendix.
Valid Values
In Appendix
No
No
No
Feet
Y=yes
N=No
No
No
Table A- 18
No
No
No
Table A- 18
5.7 Geology Down Hole Point Data EDD File
The Geology down hole point data (DHP) EDD file stores data from down hole logging methods such as
Cone Penetrometer Tests and geophysics. All down hole logging data should be submitted electronically.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 57
United States
Environmental Protection Agency
-------
Report the parameter being measured in the "param" field, such as resistivity, and report the measured
value at the depth of the measurement. Table 5-8 presents the DHP EDD file structure.
Each Geology down hole point data EDD file must be named according to the following convention:
SiteNameDate.EPAIDCode.DownholePoint_v3.txt (or .csv)
Table 5-7 Geology Down Hole Point File Data Structure
Pos#
1
2
o
6
4
5
Column
Name
sys_loc_code
Depth
Param
param_value
Param_unit
Data
Type
Text(20)
Number
w/decimal
precision
up to 15
Text(20)
Number
w/decimal
precision
up to 15
Text(15)
Required
Required
Required
Required
Required
If
available
Description
Sample collection location. Must be a valid
code for the facility and must match one of the
reported values in the sys_loc_code field of
the location EDD file (Table 3-2) submitted in
the current or previous EDD.
Depth of measurement below ground surface
in feet.
The parameter being measured, such as tip
stress, resistivity, or pore pressure.
The measured value of the parameter.
Measured unit of the parameter
Valid Values
In Appendix
No
No
No
No
No
Table 5-8 Example of down hole point data file
Sys_loc_code
MW01
MW01
MW01
MW01
MW02
MW02
MW02
Depth
10.8
11.2
10.8
11.2
9.5
10.1
11.0
Param
Tip Stress
Tip Stress
Sleeve Stress
Sleeve stress
Resistivity
Resistivity
Resistivity
Param_Value
612
624
6.1
5.8
510
521
889
5.8 Soil Gas Data EDD File
The soil gas (SoilGas) data file contains soil gas survey data.
Each Soil Gas data EDD file must be named according to the following convention:
SiteNameDate.EPAIDCode.SoilGas v3.txt (or .csv)
Table 5-9 Soil Gas Survey file data structure
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 58
United States
Environmental Protection Agency
-------
Pos#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Column Name
sys loc code
survey date
Parameter_code
Reading_depth
Reading unit
Reading
Depth_unit
Sampling method
Instalment type
East
North
Secondary_east
Secondary north
Lithology code
Area desc
Equipment code
Borehole drill met
hod
Technician
Remark
Data
Type
Text(20)
Date
Text(20)
Text(8)
Text(15)
Text(15)
Text(15)
Text(lO)
Text(15)
Text(14)
Text(14)
Text(14)
Text(14)
Text(lO)
Text(70)
Text(60)
Text(lO)
Text(50)
Text(255)
Required
Required
Required
Required
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
If Available
Description
Sample collection location
Sample survay date
Parameter measured by soil gas
survey
Depth of soil gas survey
measurement
Parameter measured by soil gas
survey
Soil gas survey measurement
Unit of measure of soil gas survey
measurement
Sampling method
Instrument type
Easting coordinate of soil gas
survey measurement
Northing coordinate of soil gas
survey measurement
Secondary easting coordinate of
soil gas survey measurement
Secondary easting coordinate of
soil gas survey measurement
Lithology code
Discription of area
Equipment_code
Drilling method
Technician
remark
Valid Values
In Appendix
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
5.9 Water Level
The Water Level (WaterLevel) EDD file contains information on water levels measured during sampling
activities. Groundwater levels and surface water elevations should be reported using this file; however, in
most cases, the file will be used to report groundwater levels. When surface water samples are collected,
however, this EDD file should be used to record water surface elevations at the time the samples were
collected. Surface water elevations reported in this file will be used as the reference elevation for surface
water sample depths (i.e., start_depth, field 11, and end_depth, field 12 in the Chemistry Sample (Sample)
EDD file. See Table 4-1). When using the Water Level EDD file for reporting surface water data, only
the first six fields (fields 1 through 6) and the "remark" field (field 17) should be populated. All fields in
the Water Level EDD file, however, should be populated for groundwater elevation data (if data is
available). An example of a Water Level file is provided in Figure 2-4, section 2.17. Each water level
file must be named according to the following convention:
SiteNameDate.EPAIDCode.WaterLevel v3.txt (or .csv)
Table 5-10 Water Level file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 59
United States
Environmental Protection Agency
-------
Table 5-10 Water Level file data structure
Pos#
1
2
o
J
4
5
6
7
Column
Name
sys_loc_code
Measurement
date
historical_
reference_elev
water_level_de
pth
water_level_el
ev
corrected dept
h
corrected_elev
ation
Data
Type
Text(20)
DateTime
Number
w/decimal
precision
up to 15
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Number
w/decimal
precision
up to 7
Required
Required
Required
Required
Required
If
available
If
available
If
available
Description
Water level measurement location.
Must be a valid code for the facility and
must match one of the reported values
in the sys_loc_code field of the location
EDO file (Table 3-2) submitted in the
current or previous EDD.
Date of water level measurement
If exact date is not known, enter the
best estimate for the date of sampling.
If an estimated date is entered, note this
and provide an explanation for how the
estimate was made in both the EDD
cover letter and in the comment field
in this file (field 10).
For groundwater samples, the value in
this field should be the elevation, in
feet above mean sea level, of the
reference point used to take
measurements of the water level depth.
Typically the reference point for
groundwater measurements is the top
of the well casing.
For surface water samples, the value in
this field should be the elevation of the
surface water in feet above mean sea
level.
If elevation is given in units other than
feet above mean sea level, please
indicate the unit used in the remarks
field ( field 17).
For groundwater, the value in this field
should be the depth of ground water
below the elevation defined in
historical reference elev field ( field
5).
For surface water, the value in this field
should be the default value of "0"
Elevation of water level. Elevation
must be in feet.
Depth of water level after any
necessary corrections, e.g., if free
product was encountered.
Corrected water level elevation that
corresponds to the corrected depth.
Elevation must be in feet.
Valid Values
In Appendix
No
MM/DD/YYYY
HH:MM:SS
format
No
No
Feet
No
feet
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 60
United States
Environmental Protection Agency
-------
Table 5-10 Water Level file data structure
Pos#
8
9
10
11
12
13
14
15
16
17
18
19
Column
Name
measured dept
h_
of_well
depth_unit
Technician
dry_indicator_
yn
measurement_
method
batch_number
dip_or_elevati
on
Remark
Lnapl_cas_rn
Lnapl_depth
Dnapl_cas_rn
Dnaple_depth
Data
Type
Number
w/decimal
precision
up to 7
Text (15)
Text (30)
Text (1)
Text (20)
Text (10)
Text (10)
Text (255)
Text (15)
Text
Number
with
precision
of up to 7
Text (15)
Number
with
precision
of up to 7
Required
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
available
If
applicable
If
applicable
If
applicable
If
applicable
Description
The depth below ground surface to the
bottom of the well.
Unit used for depth measurements. See
Table A- 18 in the Appendix for
appropriate values.
Name of technician measuring water
level
This field is used to indicate whether or
not a well is dry - "Y" for yes or "N"
for no.
Method used to make water level
measurements.
Batch number of group of
measurements.
Use either "elevation" or "dip." Use
"elevation" if water level measurement
is above the datum (i.e., artesian well)
or "dip" if water level is below datum.
Any necessary remarks related to
groundwater or surface water
information provided in this EDD file.
Analyte code of the light non-aqueous
phase liquid (Inapl) present in the well.
Use appropriate valid value from Table
A- 15 in the EDD Specification Manual
Valid Value Appendix.
Depth to the top surface of the Inapl in
feet below the reference elevation.
Analyte code of the dense non-aqueous
phase liquid (dnalp) present in the
well..
Depth to the top surface of the dnapl in
feet below the reference elevation
Valid Values
In Appendix
No
Table A- 18
No
Y=yes
N=No
No
No
Elevation
Dip
No
Table A- 15
No
Table A- 15
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 61
United States
Environmental Protection Agency
-------
Table 5-10 Water Level file data structure
Pos#
20
Column
Name
Task_code
Data
Type
Text(20)
Required
If
available
Description
Code used to associate individual
samples to a specific sampling event.
The format for this field is XX-P#
where XX is the type of task required
(PR = Pre Remedial, RI = Remedial
Investigation, FS = Feasibility Study,
PD = Pre-Design, RD = Remedial
Design, RA = Remedial Construction,
PC = Post Construction, RM =
Removal Action, BD = Before Dredge,
AD = After Dredge, BR = Brown
Fields, SP = Special Project); P# is the
phase; For example, if sampling was
performed for a Phase 1 Post
Construction site, the task code would
be PC-PL
Valid Values
In Appendix
No
5.10 Extraction - Injection Well EDO File
The Extraction-Injection Well (EIW) EDD file should be submitted on a regular (e.g., quarterly) basis for
all sites where extraction and/or injection wells are a part of the remedial action at the site. I The purpose
of the EIW EDD file is to provide EPA Region 2 with designed pumping rates as well as the actual
pumping rates for each well during a particular reporting period. This information will be useful for
determining if the remedial system is successfully capturing the contaminant plume. An example of a
Extraction-Injection Well file is provided in Figure 2-4, section 2.17. Each Extraction-Injection Well
EDD file must be named according to the following convention:
SiteNameDate.EPAIDCode.ExtractionInjectionWells_v3.txt (or .csv)
Table 5-11 Extraction-Injection Well file data structure
Pos#
1
2
3
4
Column Name
sys_loc_code
start_measure_date
end_measure_date
avg_pump_rate
Data
Type
Text(20)
DateTime
Date
Number
w/decimal
precision
up to 15
Required
Required
Required
Required
Required
Description
Well installation location. Must be a
valid code for the facility and must
match one of the reported values in the
sys_loc_code field of the location EDD
file (Table 3-2) submitted in the current
or previous EDD.
Date that the pumping rate
measurements began.
Date that the pumping rate
measurements concluded in
MM/DD/YYYY HH:MM:SS format.
Average pumping rate. Recommended
method is to use volume pumped
divided by the reported date span, i.e.,
from the (start_measurement_date to
end measurement date)
Valid Values
In Appendix
No
MM/DD/YYYY
HH:MM:SS format
MM/DD/YYYY
HH:MM:SS format
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 62
United States
Environmental Protection Agency
-------
Table 5-11 Extraction-Injection Well file data structure
Pos#
5
6
7
8
9
10
11
12
Column Name
pump_rate_unit
pct_operating_time
operating_
mode
design_rate
design_rate_unit
rate_measurement_t
ype
suction
remark
Data
Type
Text(15)
Text(3)
Text(14)
Text(14)
Text(14)
Text(14)
Text(14)
Text(255)
Required
Required
If Available
Required
Required
Required
If available
If available
If available
Description
Unit of measure for the pumping rate.
Use values from Table A- 18 in the
Appendix.
Percentage of the measurement time
interval during which the well was
operating. Use a value from 0 to 100
(do not include the percent symbol,
"%").
Mode in which well was operating
during the reported interval.
Pumping rate as specified in the
approved remedial design report for
fully capturing site groundwater
contamination.
Unit of measure for the design pumping
rate. Use values from Table A- 18 in the
Appendix.
Type of measurements used for
averaging.
Vacuum in well (e.g., wellpoint
vacuum) or well casing (e.g., vacuum
well), reported in equivalent feet of
water.
Remarks regarding the pumping rate
measurements.
Valid Values
In Appendix
Table A- 18
No
EXTRACTION,
INJECTION,
RECIRCULATION,
PULSE, DEVEL,
UNUSE.
No
Table A- 18
TOTALIZER
(totalizing flow
meter), MANIFOLD
(estimated from total
manifold flow),
ESTIMATE
(estimate from prior
values), AVERAGE
(average of
instantaneous
measurements
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 63
United States
Environmental Protection Agency
-------
5.11 Field Parameters
During purging of the well, monitor and record the field indicator parameters (turbidity, temperature,
specific conductance, pH, Eh, and DO) approximately every five minutes. These parameters must be
submitted using EPARSFRES section. Each Field Results file must be named according to the following
convention:
SiteNameDate.EPAIDCode.FieldResults_v3.txt (or .csv)
Table 5-12 Field Results file data structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
12
13
Column Name
data provider
sys_loc_code
sys_sample_code
field parameter
start depth
end depth
depth unit
result_date
result time
result value
result unit
quantitation limit
task_code
Data
Type
Text (20)
Text(20)
Text (255)
Text (15)
Numeric
Numeric
Text(2)
DateTime
Text(8)
Text(14)
Text(15)
Text(20)
Text(20)
Required
Required
Required
Required
Required
If available
If available
If available
Required
Required
Required
Required
If available
If available
Description
Data provider company code
Well installation location. Must be a
valid code for the facility and must
match one of the reported values in the
sys_loc_code field of the location EDD
file (Table 3-2) submitted in the current
or previous EDD.
Sample identifier of the sample that
was tested and analyzed. Must match
one of the reported values in the
sys_sample_code field of the
Sample_v3 file submitted in the current
or previous EDD.
Field Parameter
Sample start depth
Sample end depth
Sample depth unit.
Result Date/time
Time result was collected.
Result value.
Result unit.
Quantitation limit
Code used to associate individual
samples to a specific sampling event.
The format for this field is XX-P#
where XX is the type of task required
(PR = Pre Remedial, RI = Remedial
Investigation, FS = Feasibility Study,
PD = Pre-Design, RD = Remedial
Design, RA = Remedial Construction,
PC = Post Construction, RM =
Removal Action, BD = Before Dredge,
AD = After Dredge, BR = Brown
Fields, SP = Special Project); P# is the
phase; For example, if sampling was
performed for a Phase 1 Post
Construction site, the task code would
be PC-PL
Valid Values
In Appendix
No
No
No
Table A-15
No
No
No
mm/ddVyr hh:mm:ss
format
hh: mm:ss format
No
Table A- 18
No
No
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 64
United States
Environmental Protection Agency
-------
Table 5-12 Field Results file data structure
Pos#
14
15
16
17
18
19
20
21
Column Name
sample_matrix_code
qualifier
sampling_company_c
ode
sampling reason
sampling method
reportable result
value type
remark
Data
Type
Text(20)
Text(20)
Text(20)
Text(40)
Text(40)
Text(lO)
Text(lO)
Text(225)
Required
Required
If available
If available
If available
If available
Required
Required
If available
Description
Sample Code that identifies the matrix
being sampled, such as soil,
groundwater, or sediment. For
acceptable valid values, see Table A-l
in the Appendix, matrix code
Interpreted qualifier flag assigned by
the data provider
Name or initials of consulting company
performing sampling. (This field does
not have a controlled vocabulary, i.e.,
there is no table of valid values for this
field.)
Reason for sampling
Sampling method
Reportable result
How value was derived
Remark
Valid Values
In Appendix
Table A-l
Table A-10
No
No
No
No
No
Actual
Calculated
Estimated
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 65
United States
Environmental Protection Agency
-------
6. FORMATS FOR VAPOR INTRUSION FILES
Vapor Intrusion data submittals contain data of sampling taken inside of the contaminated sites or
buildings.
6.1 Vapor Intrusion Building Address EDD File
The Vapor Intrusion Building Address (VI_Bldg_Address) contains address and contact information for
the building.
Each Vapor Intrusion file must be named according to the following convention:
SiteNameDate.EPAIDCode.VI_Bldg_Address_v3.txt (or .csv)
Table 6-1 Vapor Intrusion Building Address data structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Column Name
building code
building name
contact_name
address 1
address2
city
state
zip_code
county
phone number
alt_phone number
fax_number
email_address
remark
Data Type
Text(20)
Text (60)
Text (50)
Text (40)
Text (40)
Text (30)
Text (2)
Text (10)
Text (50)
Text (30)
Text (30)
Text(30)
Text(lOO)
Text(2000)
Required
Required
Required
Description
Unique code that identifies the
building within the facility (i.e.
B001,B002, etc.)
Name of site
Building contact name
Building address, part one.
Building address, part two
Building city
Building state
Building zipcode
Building county
Building contact phone number
Alternative site phone number
Building contact fax number.
Building contact email address.
Remark
Valid Values
In Appendix
6.2 Vapor Intrusion Building EDD Files
The Vapor Intrusion Building (VI_Building) contains specific data about the building.
Each Vapor Intrusion building file must be named according to the following convention:
SiteNameDate.EPAIDCode.VI Building v3.txt (or .csv)
Table 6-2 Vapor Intrusion Building data structure
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 66
United States
Environmental Protection Agency
-------
Pos#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Column Name
building_code
building_name
building_type
building_size
num_floors
construct_year
foundation_depth
foundation_depth_
unit
foundation_type
foundation_wall_m
aterial
foundation_floor_m
aterial
foundation_wall_thi
ckness
fou ndation_f loor_th
ickness
foundationjtiickne
ss unit
attached_garage_y
n
radon_mitigation_y
n
heat_fuel_type
heat_system_type
central_air_yn
sump_yn
voc_mitigation_yn
remark
custom_field_l
custom_field_2
custom_field_3
custom_field_4
custom_field_5
Data Type
Text(20)
Text(255)
Text(20)
Text(20)
Numeric
Numeric
Numeric
Text(15)
Text(20)
Text(20)
Text(20)
Numeric
Numeric
Text(15)
Text(l)
Text(l)
Text(255)
Text(255)
Text(l)
Text(l)
Text(l)
Text(2000)
Text(255)
Text(255)
Text(255)
Text(255)
Text(255)
Required
Required
Required
Description
Unique code that identifies the
building within the facility (i.e.
B001, B002, etc.)
Building name (i.e. Denison Medical
Building)
Type of building (i.e. Residential,
Industrial, etc.)
Size of building (Small, Medium,
Large)
Number of floors in the building
Year of construction
Foundation depth (below ground
surface)
Foundation depth unit
Foundation type (i.e. Basement,
crawlspace, ect.)
Foundation wall material
Foundation floor material
Foundation wall thickness
Foundation floor thickness
Foundation thickness units
Existance of an attached garage
(Y/N)?
Existance of radon mitigation
system (Y/N)?
Type of heating fuels (i.e. Natural
gas)
Type of heating system (i.e. Forced
hot air)
Existance of central air system
(Y/N)?
Existance of sump pump (Y/N)?
VOC mitigation flag (Y/N)?
Building remarks
Valid Values
In Appendix
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 67
United States
Environmental Protection Agency
-------
6.3 Vapor Intrusion Task Parameter EDD File
The Vapor Intrusion Task Parameter (VI_Task_Parameter) contains additional sampling parameter
collected in the field and not analyized in the lab.
Each Vapor Intrusion Task Parameter file must be named according to the following convention:
SiteNameDate.EPAIDCode.VI_Task_Parameter_v3.txt (or .csv)
Table 6-3 Vapor Intrusion Task Parameter data structure
Pos#
1
2
3
4
5
6
7
8
Column Name
task_code
param_code
task_desc
building_use_type
measurement_date
param_value
param_unit
remark
Data Type
Text(40)
Text(20)
Text(255)
Text(20)
DateTime
Text(255)
Text(15)
Text(2000)
Required
Required
Required
Required
Description
Related task code for the parameter
Parameter code which related to
the parameter type (i.e. TEMP)
Task description
The use of the building at the time
of the sampling event
Measurement date
The value of the parameter
The unit of measure of the
parameter
Additional remarks or descriptor for
the parameter
Valid Values
In Appendix
Table A-18
6.4 Vapor Intrusion Sample EDD file
The Vapor Intrusion Sample (VI_Samples) contains samples information.
Each Vapor Intrusion Sample file must be named according to the following convention:
SiteNameDate.EPAIDCode.VI_Samples_v3.txt (or .csv)
Table 6-4 Vapor Intrusion Samples data structure
Pos#
1
2
3
4
5
Column Name
data_provider
sys_loc_code
sys_sample_code
sample_matrix_cod
e
task_code
Data Type
Text(20)
Text(20)
Text(40)
Text(3)
Text(40)
Required
REQUIRED
REQUIRED
REQUIRED
REQUIRED
REQUIRED
Description
Data provider name
Location identifier of sample
collection
Unique sample identifier
Code which distinguishes between
different type of sample matrix
Sampling task code
Valid Values
In Appendix
Table A-l
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 68
United States
Environmental Protection Agency
-------
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
sampling_company
code
sample_start_date
sent_to_lab_date
chain_of_custody
sample_end_date
sample_duration
sample_duration_u
nit
floor_material
slab_thickness
subfloor_material
subfloor_moisture
seal_type
seal_adequate_yn
purge_yn
purge_pid
purge_pid_unit
vac_gauge_initial
vac_gauge_final
vac_gauge_unit
vapor_loc_desc
sampling_reason
sampling_method
sampler
remark
Text(20)
DateTime
DateTime
Text(40)
DateTime
Text(20)
Text(15)
Text(20)
Text(20)
Text(20)
Text(20)
Text(20)
Text(l)
Text(l)
Numeric
Text(15)
Numeric
Numeric
Text(15)
Text(255)
Text(30)
Text(40)
Text(50)
Text(2000)
REQUIRED
REQUIRED
Name or initials of sampling
company.
Sample start date and time
Date sample was sent to laboratory
for analysis
Chain of custody
Sample end date and time
The sampling duration
Sample duration units
Lowest level floor material at
sample location
Slab thickness at sample location
(in inches)
Material found below the foundation
floor
Moisture content at subslab sample
location (i.e. Dry, Damp, Saturated)
Type of seal used during sampling
(i.e. Beeswax, Clay, Teflon Tape)
Did the sample probe seal pass the
tracer test (Y/N)?
Was the sample equipment purged
in accordance with work plan
(Y/N)?
PID instrument reading
PID instrument reading units (i.e.
ppb)
Vacuum gauge reading immediately
after start
Vacuum gauge reading immediately
before end
Vacuum gauge instrument units
(i.e. inches of water)
Soil vapor intrusion location
description
Reason for sampling
Sampling method
Person taking sample.
Remark
Table A-18
6.5 Vapor Intrusion Test Result QC
The Vapor Intrusion Test Result QC (VI_TestResultQC) contains data concerning analytical tests
performed on samples with quality control data elements.
Each Vapor Intrusion Test Result QC file must be named according to the following convention:
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 69
United States
Environmental Protection Agency
-------
SiteNameDate.EPAIDCode.VI_TestResultQC_v3.txt (or .csv)
Table 6-5 Vapor Intrusion Test Result QC file data structure
Pos#
1
2
3
4
5
6
7
8
Column Name
sys_sample_code
la b_a n l_method_na
me
analysis_date
total_or_dissolved
column_number
test_type
lab_matrix_code
analysisjocation
Data
Type
Text(40)
Text(35)
DateTime
Text(l)
Text(2)
Text(lO)
Text(3)
Text(2)
Required
REQUIRE
D
REQUIRE
D
REQUIRE
D
REQUIRE
D
REQUIRE
D
REQUIRE
D
Description
Unique sample identifier. Each
sample at a facility must have a
unique value, including spikes and
duplicates. You have considerable
flexibility in the methods used to
derive and assign unique sample
identifiers, but uniqueness
throughout the database is the only
restriction enforced by EQuIS®.
Laboratory analytical method name
or description. A controlled
vocabulary column, valid values can
be found in the appendix in table
lab anl method name.
Date and time of sample analysis in
'MM/DD/YYYY HH:MM:SS' format.
May refer to either beginning or
end of the analysis as required by
EPA.
Must be either 'D' for dissolved or
filtered [metal] concentration, or T
for everything else
Report as null.
Type of test. Valid values include
'Initial', 'Reextractl', 'Reextract2',
'ReextractS', 'Reanalysis',
'Dilutionl', 'Diluton2', and 'DilutonS'.
Code which distinguishes between
different type of sample matrix. For
example, soil samples must be
distinguished from ground water
samples, etc. See matrix valid value
table in the appendix. The matrix of
the sample as analyzed may be
different from the matrix of the
sample as retrieved (e.g.
leachates), so this field is available
at both the sample and test level.
Must be either 'FI' for field
instrument or probe, 'FL' for mobile
field laboratory analysis, or 'LB' for
fixed_based laboratory analysis.
Valid Values
In Appendix
Table A-16
Table A-25
Table A-l
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 70
United States
Environmental Protection Agency
-------
9
10
11
12
13
14
15
16
17
18
19
20
21
22
basis
containerjd
dilution_factor
prep_method
prep_date
leachate_method
leachate_date
lab_name_code
qc_level
lab_sample_id
percent_moisture
subsample_amount
subsample_amount
_unit
analyst_name
Text(lO)
Text(30)
Numeric
Text(20)
DateTime
Text(15)
DateTime
Text(20)
Text(lO)
Text(40)
Text(5)
Text(14)
Text(15)
Text(30)
Must be either 'Wet' for wet_weight
basis reporting, 'Dry' for dry_weight
basis reporting, or 'NA' for tests for
which this distinction is not
applicable. The EPA prefers that
results are reported on the basis of
dry weight where applicable.
Report as null.
Effective test dilution factor. If
value is less than 1, then you need
to put 'concentration factor' in the
comment column.
Laboratory sample preparation
method name or description. A
controlled vocabulary (i.e., see
Prep_mthd_var valid values in the
appendix).
Beginning date and time of sample
preparation in 'MM/DD/YYYY
HH: MM :SS' format.
Laboratory leachate generation
method name or description. The
method name should be sufficient
to reflect operation of the
laboratory (see analysis method
discussion).
Beginning date and time of leachate
preparation in 'MM/DD/YYYY
HH: MM :SS' format.
Unique identifier of the laboratory
as defined by the EPA. Controlled
vocabulary, see lab valid value table
in the appendix.
May be either 'screen' or 'quant'.
Laboratory LIMS sample identifier.
If necessary, a field sample may
have more than one LIMS
lab_sample_id (maximum one per
each test event).
Percent moisture of the sample
portion used in this test; this value
may vary from test to test for any
sample. Numeric format is
'NN.MM', i.e., 70.1% could be
reported as 70.1' but not as
70.1%'.
Amount of sample used for test.
Unit of measurement for subsample
amount. Controlled vocabulary, see
Unit valid values table in appendix.
Report as null.
Table A-14
Table A-23
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 71
United States
Environmental Protection Agency
-------
23
24
25
26
27
28
29
30
31
32
33
34
35
36
instrument_id
comment
preservative
final_volume
final_volume_unit
cas_rn
chemical_name
result_value
result_error_delta
result_type_code
reportable_result
detect_flag
lab_qualifiers
validator_qualifiers
Text(50)
Text(255)
Text(20)
Numeric
Text(15)
Text(15)
Text(75)
Numeric
Text(20)
Text(lO)
Text(lO)
Text(2)
Text(lO)
Text(lO)
REQUIRE
D
REQUIRE
D
REQUIRE
D
REQUIRE
D
REQUIRE
D
Report as null.
Comments about the test as
necessary.
Sample preservative used.
The final volume of the sample
after sample preparation. Include
all dilution factors.
The unit of measure that
corresponds to the final_volume.
Use values in analyte valid value
table.
Use the name in the analyte valid
value table.
Analytical result reported at an
appropriate number of significant
digits. Maybe blank for
non detects.
Error range applicable to the result
value; typically used only for
radiochemistry results.
Must be either TRG' for a target or
regular result, TIC' for tentatively
identified compounds, 'SUR' for
surrogates, 'IS' for internal
standards, or 'SC for spiked
compounds.
Must be either 'Yes' for results
which are considered to be
reportable, or 'No' for other results.
This field has many purposes. For
example, it can be used to
distinguish between multiple results
where a sample is retested after
dilution. It can also be used to
indicate which of the first or second
column result should be considered
primary. The proper value of this
field in both of these two examples
should be provided by the
laboratory (only one result should
be flagged as reportable).
Maybe either Y for detected
analytes or 'N' for non_detects. Use
'Y' for estimated (above detection
limit but below the quantitation
limit) or '<' and '>' for tests such as
flash point. Note that '<' must not
be used to indicate non_detects
(use 'N' for non_detects instead).
Qualifier flags assigned by the
laboratory.
Qualifier flags assigned by the
validation firm.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 72
United States
Environmental Protection Agency
-------
37
38
39
40
interpreted_qualifie
rs
validatecLyn
method_detection_l
imit
report! ng_detection
Jimit
Text(lO)
Text(l)
Text(20)
Numeric
REQUIRE
D
Qualifier flags assigned by the
validation firm. This is a controlled
vocabulary column, valid values can
be found in the qualifiers table in
appendix.
Indicates if the result has been
validated.
Lowest concentration that can be
detected by an instrument with
correction for the effects of sample
matrix and method-specific
parameters such as sample
preparation.
MDLs are explicitly determined as
set forth in 40 CFR Part 136. They
are defined as three times the
standard deviation of replicate
spiked analyses. This represents
99% confidence that the analyte
concentration is greater than zero.
The organic methods in the EPA
500 series, EPA 600 series, and
Standard Methods all give typical
MDLs for clean water samples.
Generally these clean-water MDLs
(corrected for %moisture, sample
size, and dilution) are used for
reporting limits,
but the laboratory may use MDLs
that they have generated. MDLs
generated by the laboratory using
the sample matrix of interest are
the most reliable. If the clean-water
MDLs are used, remember that they
do not include all of the upward
correction
necessary to account for the effects
of sample matrix. This is important
to remember especially for risk
assessments and highly
contaminated samples.
Concentration level above which
results can be quantified with
confidence. It must reflect
conditions such as dilution factors
and moisture content.
Required for all results for which
such a limit is appropriate. The
reporting_detection_limit column
must be reported as the sample
specific detection limit.
Table A-10
Y= "Yes"
N= "No"
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 73
United States
Environmental Protection Agency
-------
41
42
43
44
45
46
47
48
49
50
51
quantitationjimit
result_unit
detection_limit_unit
tic_retention_time
minimum_detectabl
e_conc
counting_error
uncertainty
critical_value
validationjevel
result_comment
qc_original_conc
Text(20)
Text(15)
Text(15)
Text(8)
Numeric
Numeric
Text(lO)
Numeric
Text(20)
Text(255)
Numeric
Quantitation limits refer to a
minimum concentration of an
analyte that can be measured
within specified limits of precision
and accuracy. They are generally
5-10 times the detection limit.
Thus, when quantitation limits are
used as reporting limits, the
laboratory is saying that the analyte
is not present in a sufficient amount
to be reliably quantified (i.e., at a
concentration above the
quantitation limit).
It may be present and even
positively identified or "seen" at a
lower concentration.
Units of measurement for the
result. Controlled vocabulary, see
Units valid value table in the
appendix.
Units of measurement for the
detection limit(s). Controlled
vocabulary, see Units valid value
table in the appendix. This field is
required if a
reporting_detection_limit is
reported.
Report as null.
Minimum detectable concentration
or activity. This value should be in
the same units as the result value.
Counting error as reported by the
laboratory. This value should be in
the same units as the result value.
The uncertainty of the counting
error, valid values include "1 sigma"
or "2 sigma" This field is required if
the counting_error field is
populated.
Critical value as reported by the
laboratory.
EPA defined validation level
Result specific comments.
The concentration of the analyte in
the original (unspiked) sample.
Might be required for spikes and
spike duplicates (depending on user
needs). Not necessary for surrogate
compounds or LCS samples (where
the original concentration is
assumed to be zero).
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 74
United States
Environmental Protection Agency
-------
52
53
54
55
56
57
qc_spike_added
qc_spike_measured
qc_spike_recovery
qc_dup_original_co
nc
qc dup spike adde
d
qc_dup_spike_mea
sured
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
The concentration of the analyte
added to the original sample. Might
be required for spikes, spike
duplicates, surrogate compounds,
LCS and any spiked sample
(depending on user needs).
The measured concentration of the
analyte. Use zero for spiked
compounds that were not detected
in the sample. Might be required for
spikes, spike duplicates, surrogate
compounds, LCS and any spiked
sample (depending on user needs).
The percent recovery calculated as
specified by the laboratory QC
program. Always required for
spikes, spike duplicates, surrogate
compounds, LCS and any spiked
sample. Report as percentage
multiplied by 100 (e.g., report
"120%" as "120").
The concentration of the analyte in
the original (unspiked) sample.
Might be required for spike or LCS
duplicates only (depending on user
needs). Not necessary for surrogate
compounds or LCS samples (where
the original concentration is
assumed to be zero).
The concentration of the analyte
added to the original sample. Might
be required for spike or LCS
duplicates, surrogate compounds,
and any spiked and duplicated
sample (depending on user needs).
Use zero for spiked compounds that
were not detected in the sample.
Required for spikes, spike
duplicates, surrogate compounds,
LCS and any spiked sample. Also
complete the qc-spike-added field.
The measured concentration of the
analyte in the duplicate. Use zero
for spiked compounds that were not
detected in the sample. Might be
required for spike and LCS
duplicates, surrogate compounds,
and any other spiked and
duplicated sample (depending on
user needs). Also complete the qc-
spike-measured field.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 75
United States
Environmental Protection Agency
-------
58
59
60
61
62
63
64
qc_dup_spike_reco
very
qc_rpd
qc_spike_lcl
qc_spike_ucl
qc_rpd_cl
qc_spike_status
qc_dup_spike_statu
s
Numeric
Text(8)
Text(8)
Text(8)
Text(8)
Text(lO)
Text(lO)
The duplicate percent recovery
calculated as specified by the
laboratory QC program. Always
required for spike or LCS duplicates,
surrogate compounds, and any
other spiked and duplicated sample.
Also complete the qc-spike-recovery
field. Report as percentage
multiplied by 100 (e.g., report
"120%" as "120").
The relative percent difference
calculated as specified by the
laboratory QC program. Required
for duplicate samples as
appropriate. Report as percentage
multiplied by 100 (e.g., report
"30%" as "30").
Lower control limit for spike
recovery. Required for spikes,
spike duplicates, surrogate
compounds, LCS and any spiked
sample. Report as percentage
multiplied by 100 (e.g., report
"60%" as "60").
Upper control limit for spike
recovery. Required for spikes,
spike duplicates, surrogate
compounds, LCS and any spiked
sample. Report as percentage
multiplied by 100 (e.g., report
"60%" as "60").
Relative percent difference control
limit. Required for any duplicated
sample. Report as percentage
multiplied by 100 (e.g., report
"25%" as "25").
Used to indicate whether the spike
recovery was within control limits.
Use the "*" character to indicate
failure, otherwise leave blank.
Required for spikes, spike
duplicates, surrogate compounds,
LCS and any spiked sample.
Used to indicate whether the
duplicate spike recovery was within
control limits. Use the "*" character
to indicate failure, otherwise leave
blank. Required for any spiked and
duplicated sample.
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 76
United States
Environmental Protection Agency
-------
65
66
qc_rpd_status
lab_SDG
Text(lO)
Text(20)
Used to indicate whether the
relative percent difference was
within control limits. Use the "*"
character to indicate failure,
otherwise leave blank. Required for
any duplicated sample.
Lab Sample Delivery Group (SDG)
identifier. A single sample may be
assigned to multiple Sample
Delivery Group (SDG) based on
different analysis.
6.6 Vapor Intrusion Batch EDO File
Each Vapor Intrusion Batch file must be named according to the following convention:
SiteNameDate.EPAIDCode.VI_Batches_v3.txt (or .csv)
Table 6-6 Vapor Intrusion Batches file data structure
Pos#
1
2
3
4
5
Column Name
sys_sample_code
la b_a n l_method_na
me
analysis_date
total_or_dissolved
column_number
Data
Type
Text(40)
Text(35)
DateTime
Text(l)
Text(2)
Required
REQUIRED
REQUIRED
REQUIRED
REQUIRED
REQUIRED
Description
Unique sample identifier. Each
sample must have a unique value,
including spikes and duplicates.
Laboratory QC samples must also
have unique identifiers. The
laboratory and the EQuIS®
Chemistry user have considerable
flexibility in the methods they use
to derive and assign unique sample
identifiers, but uniqueness
throughout the database is the only
restriction enforced by EquIS®
Chemistry.
Laboratory analytical method name
or description. A controlled
vocabulary column, valid values can
be found in the appendix in table
ab anl method name.
Date and time of sample analysis in
'MM/DD/YYYY HH:MM:SS' format.
May refer to either beginning or
end of the analysis as required by
EPA.
Must be either 'D' for dissolved or
filtered [metal] concentration, or T
for everything else
Column number, if null, "NA" will be
placed in this field
Valid Values
In Appendix
Table A-16
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 77
United States
Environmental Protection Agency
-------
6
7
8
test_type
test_batch_type
test_batch_id
Text(lO)
Text(lO)
Text(20)
REQUIRED
REQUIRED
Type of test. Valid values include
'Initial', 'Reextractl', 'Reextract2',
'ReextractS', 'Reanalysis',
'Dilutionl', 'Diluton2', and 'DilutonS'.
Lab batch type. Valid values include
'Prep', 'Analysis', and 'Leach'. This is
a required field for all batches.
Unique identifier for all lab batches.
Table A-25
Table A-26
Region 2 Comprehensive Electronic Data Deliverable
Version 2.0 78
United States
Environmental Protection Agency
-------
7. TECHNICAL SUPPORT
EPA Region 2 provides technical support for users of this Comprehensive EDD Specification Manual.
For questions concerning data, data formats, and EDD submittal procedures, please contact EDD EQUIS
Coordinator. For more general questions relating to the site, please contact the EPA RPM assigned to the
site.
Region 2 Comprehensive Electronic Data Deliverable United States
Version 2.0 79 Environmental Protection Agency
------- |