p \
i sis'
EPA Region 5
11 West Jackson Blvd. Chicago, IL 60604
Electronic Data Deliverable (EDD)
Comprehensive Manual Version 4.2
V
March, 2019
EQuIS Professional version 6.6 »EDD format version 3.0.11
-------
THIS PAGE LEFT BLANK INTENTIONALLY
Region 5 EDD Comprehensive Specification Manual United States
Version 4.2 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
Crossland, 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 (Region 2), and John Canar, Region
5 and updated on March, 2019 to meet the standards and requirements of EPA Region 5.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 i
United States
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 5 EDD Comprehensive Specification Manual
Version 4.2 ii
United States
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 5.
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 5 Superfund Division.
This EDD Comprehensive Specification manual describes the requirements for reporting all current and
future environmental data to EPA Region 5. 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 5 "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 5 EDD is comprised of four groups: Field. Lab. Basic, and Facility.
The first group of the EDD is the Field, which contains the data for the point of contact, site information,
Locations, as well as drilling activities, lithology, well installation, well construction and well segment,
geotechnical sample information, water levels, water table, downhole logging methods, Extraction and
Injection wells, and Soil Gas survey data. Those files are:
Field- the folloing three files can be submitted once unless there are new/ additional locations to the site
¦ Data Provider (named as "EPAR5DATAPROVIDER_v3" is the point of contact for EDD and
file providing the information)
¦ Subfacility (named as "EPAR5SUBFACILITY_v3", which is the general information about the
site)
¦ Location (named as "EPAR5LOC_v3", which is the information regarding the sampling
locations)
The following files are included in the Field section, which contains the field data, please submit the data
when they are available:
¦ Drilling Activity (named as "EPAR5DRA_v3", which is the information about drilling activities
resulting form the soil borings.)
¦ Lithology (named as "EPAR5LTH_v3", which is the lithology information for the borings.)
¦ Well (named as "EPAR5EPAR5WEL_v3", which contains the monitoring well information
related to well instruction)
¦ Well Construction (named as "EPAR5WSG_v3", which contains the well construction details
and well segment data.)
¦ Geology Sample (named as "EPAR5GSMP_v3", which contains the geotechnical sample
information)
¦ Water Level (named as "EPAR5GWTR_v3", which contains the information on water levels
measured from the soil borings or wells.)
¦ Water Table (named as "EPAR5TBL_v3", which contains the information pertaining the water
table)
Region 5 EDD Comprehensive Specification Manual
Version 4.2 iii
United States
Environmental Protection Agency
-------
¦ Downhole Logging (named as "EPAR5DHP_v3", which contains the data from downhole
logging methods such as Cone Penetrometer Tests and geophysics.)
¦ Extraction and Injection Wells (named as "EPAR5EIW_v3", which contains the data about
extraction and Injection wells)
¦ Soil Gas (named as "EPAR5EPAR5SoilGas_v3", which contains the imports soil gas survey
data.)
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 lab data.
Lab
The Lab EDD files contain data related to chemistry field measurements, sample collection information,
sample tests and result QC. The Lab EDD files are the:
• Sample (named as "EPAR5SMP_v3", which contains the information about sample collection)
• Test Result (named as "EPAR5TRS_v3", which contains the information concerning analytical
tests and lab results performed on samples.)
• Test Result QC (named as "EPAR5TRSQC_v3", which contains the information about the
analytical test performed on samples with quality control data elements)
• Batch (named as "EPAR5BAT_v3", which contains the data that related the individual samples to
the batch identifier.)
Basic Submittals
The Basic EDD files contain historical operation and maintenance (O&M) data. The EDD files are the:
• Basic Location (named as "EPAR5_BasicLOC_v3", which contains the information about
sampling locations from historical data)
• Basic Water Level (named as "EPAR5_BasicWTR_v3", which contains the information
regarding groundwater level measurements)
• Basic Chemistry Sample (named as "EPAR5_BasicChem_v3", which contains the information
about sample collection)
• Basic Geology (named as "EPAR5_BasicGEO_v3", which contains the information about
geology data)
F aciltiv
The facility data includes 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.
¦ Files (named as "Files_v3", which contains any supplementary information about site such as a
base map, a cover letter about the data, data provider, or the site sampling information.)
Of the files listed above, the Lab 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 Field, Lab, and/or Facility 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
Region 5 EDD Comprehensive Specification Manual
Version 4.2 iv
United States
Environmental Protection Agency
-------
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-l and E-2, decision points are included in the EDD creation process to ensure that
Field EDD files have been submitted for a site, as well as to prevent redundancy when getting ready to
submit Lab EDDs. For example, one of the Field EDDs called the SUBFACILITY 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 Field 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 5 is to check it using the Electronic Data
Processor (EDP) software application that is currently provided on the EPA Region 5 website (located at
https://www.epa.gov/superfund/region-5-superfund-electronic-data-submission). This software
application will identify any formatting errors in the files that must be corrected prior to submitting the
EDD.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 v
United States
Environmental Protection Agency
-------
Figure E-l Process flow diagram for the creation and checking of Field, and Lab EDD files
Define the columns in the
selected software according to
the tables in sections 3 & 4
Select a Data Entry
Product
Get information and download
EDD Region 5 EDD from:
https://www.epa.gov/superfund/reqion-
5-superfund-electronic-data-submission
Enter Data provider,
SUBFACILITY Data (Field
EDD File)
Has site ever been
reported?
Enter Location Data
(Field EDD 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 EDD Files
to Region 5
Email
Check with EDP and Correct Errors. If no errors
follow the EDD submission process in this
document.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 vi
United States
Environmental Protection Agency
-------
Figure E-2 Process flow diagram for the creation and checking of Field EDD files
NO
Yes
Access or
Excel?
No
Has site ever
been reported?
Yes
No
Has location ever
been reported?
Yes
Enter Drilling
Activity Date
Enter Geo
Sample Data
Enter Lithology
Data
Enter Water
Level Data
Enter Well
Contruction
Data
Enter Well Data
Enter Data provider,
SUBFACILITY Data (Field
EDD File)
Enter Water Table
Data
Send EDD Files to
Region 5 email
Select a Data Entry
Product
Enter downhole Point
Data (e.g. CPT)
Enter Location Data
(Field EDD File)
Define the columns in
the selected software
according to tables in
section 3 and 5
Check with EDP and Correct Errors. If no
errors, follow the EDD submission process
in this document.
Get information and download
EDD Region 5 EDD from:
https://www.epa. gov/superfund/region-5 -
superfund-electronic-data-sub mission
Region 5 EDD Comprehensive Specification Manual
Version 4.2 vii
United States
Environmental Protection Agency
-------
THIS PAGE LEFT BLANK INTENTIONALLY
Region 5 EDD Comprehensive Specification Manual United States
Version 4.2 viii Environmental Protection Agency
-------
TABLE OF CONTENTS
EXECUTIVE SUMMARY iii
1. INTRODUCTION TO THE EPA REGION 5 ELECTRONIC DATA DELIVERABLE (EDD) 1
2. GENERAL HDD REPORTING REQUIREMENTS 3
2.1 File Formats 3
2.2 Field Data Submittals 3
2.3 Lab Data Submittals 6
2.4 File Naming Convention 7
2.5 Data Integrity Rules 10
2.6 Definition of a Facility, Site, and Location 13
2.7 Reporting Null Values 13
2.8 Valid Values 14
2.9 Reporting Re-Tests 15
2.10 Reporting Non-Detects 15
2.11 Reporting Tentatively Identified Compounds 16
2.12 Data Types 16
2.13 Data Entry Tools Provided to Create the EDD Files 17
2.14 Using the Electronic Data Processor to Check EDD Formatting 19
2.15 Submitting Your EDD to EPA Region 5 19
2.16 Examples of Field, and Lab EDD Files 21
3. FORMATS FOR Facility Files and Field Files 28
3.1 Facility EDD Files 28
3.2. Field Files 29
3.3 SUBFACILITY EDD File 29
3.4 Location EDD File (EPAR5LOC_v3) 30
3.5 Drill Activity EDD File 35
3.6 Lithology EDD File 36
3.7 Well EDD File 38
3.8 Well Construction EDD File 40
3.9 Geology Samples EDD File 41
3.10 Water Levels 44
3.11 Water Table EDD Files 47
3.12 Geology Down Hole Point Data EDD File 48
3.13 Extraction - Injection Well (EPAR5EIW_v3) EDD File 49
3.14 Soil Gas Data EDD File 51
4. FORMATS FOR LAB FILES 52
4.1 Lab Sample EDD File 52
4.2 Lab Test Results EDD Files 55
4.3 Lab Test/Result with QC Data EDD File 59
4.4 Lab Batch Data (EPAR5BAT_v3) EDD File 66
5. TECHNICAL SUPPORT 67
Region 5 EDD Comprehensive Specification Manual
Version 4.2 ix
United States
Environmental Protection Agency
-------
LIST OF TABLES
Table 2-1 General information on the files that comprise the first three files in the Field EDD section 3
Table 2-2 General information on the files that comprise the field files in the Field EDD section 5
Table 2-3 General information on the files that comprise the Chemistry EDD 6
Table 2-4 EDD File Naming Formats 9
Table 2-5 Examples of how to report null values 13
Table 2-6 Cross-reference between the valid value tables in appendix and the EDD files 14
Table 2-7 Example of reporting re-tests 15
Table 2-8 Example of reporting non-detects 15
Table 2-9 Example nomenclature for TIC reporting 16
Table 2-10 Datatype descriptions 16
Table 2-11 Instructions for producing tab-delimited text files from some software packages 18
Table 3-1 Files (Files_v3) structure 28
Table 3-2 Data Provider (EPAR5DataProvider_v3) File Structure 29
Table 3-3 SUBFACILITY (EPAR5SUBFACILITY_v3) data file structure 30
Table 3-4 Location Data (EPAR5LOC_v3) File Structure 31
Table 3-5 Drill activity (EPAR5DRA_v3) file data structure 35
Table 3-6 Lithology (EPAR5LTH_v3) file data structure 37
Table 3-7 Well (EPAR5WEL_v3) file data structure 38
Table 3-8 Well construction (EPAR5WSG_v3) file data structure 40
Table 3-9 Geology samples (EPAR5GSMP_v3) file data structure 41
Table 3-10 Water Level (EPAR5GWTR_v3) file data structure 45
Table 3-11 Water table (EPAR5TBL_v3) file data structure 47
Table 3-12 Geology Downhole Point (EPAR5DHP_v3) File Data Structure 49
Table 3.12a Example of downhole point data file 49
Table 3-13 Extraction-Injection Well (EPAR5EIW_v3) file data structure 50
Table 3-14 Soil Gas (EPAR5SoilGas_v3) Survey file data structure 51
Table 4-1 Lab sample (EPAR5SMP_v3) file data structure 52
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure 55
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure 60
Table 4-4 Lab batch file (EPAR5BAT_v3) data structure 66
LIST OF FIGURES
Figure E-l Process flow diagram for the creation and checking of Field, and Lab EDD files vi
Figure E-2 Process flow diagram for the creation and checking of Field EDD files vi
Figure 2-1 Relationships between Lab file data structures 12
Figure 2-2 Facility component definitions 13
Figure 2-3. Example Field EDD ready for conversion to text file 21
Figure 2-4. Example Lab EDD ready for conversion to text file 21
Figure 2-5. Examples of QC data fields in a Chemistry EDD 22
Figure 2-5. Examples of QC data fields in a Chemistry EDD (continued) 24
Figure 2-6. Example Field EDD ready for conversion to text file 25
Extraction Injection Wells 27
Region 5 EDD Comprehensive Specification Manual
Version 4.2 x
United States
Environmental Protection Agency
-------
THIS PAGE LEFT BLANK INTENTIONALLY
Region 5 EDD Comprehensive Specification Manual United States
Version 4.2 xi Environmental Protection Agency
-------
1. INTRODUCTION TO THE EPA REGION 5 ELECTRONIC DATA DELIVERABLE (EDD)
The EPA Region 5 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 5 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 5. Environmental data collected and analyzed
prior to the initial use of this EDD specification manual should be reported using the EPA Region 5
"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 5 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 5 EDDs include Access, FoxPro®, Excel, 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 (EPAR5LOC_v3) 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 5 E-Data website
(https://www.epa.gov/superfund/region-5-superfund-electronic-data-submission') 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 5. 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 three separate sections:
• General reporting requirements and submission process are discussed in Section 2.
• The Facility and Field file structures (i.e.data provider, subfacility, location, water level) are defined
in Section 3.
• The Lab file structures are defined in Section 4. In most cases, lab data accounts for the majority of
data that is reported.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 1
United States
Environmental Protection Agency
-------
Each file must be reported exactly as defined in these sections. Any deviations will result in loading
errors.
EPA Region 5 expects all fields referred to as "Required", "Not required" or "If available" to be filled in.
If data for fields referred to as "If available" meaning the data can be reported when available, such as the
result values and the unit. If users reported the result values, it is preferred to repor the unit as well. Data
fields indicated as "Not required" meaning the fields are not required fields. 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 5 format will be given time to transition
to any national format changes.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 2
United States
Environmental Protection Agency
-------
2. GENERAL EDD REPORTING REQUIREMENTS
2.1 File Formats
With the exception of the electronic base map, all data from the EPA Region 5 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.16). The maximum length of each text field is indicated in
parentheses in the EDD tables shown in Sections 3 and 4. 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).
2.2 Field Data Submittals
The Field data submittal consists of the initial data submittal and the field data including: Data Provider
(DataProvider), Subfacility, and the Location (Location) file including facility center point in latitude
longitude coordinate, and the field data including drilling activities, lithology, well installation, well
construction and well segments, geotechnical sample information, water levels, water table, downhole
logging methods, extraction and injections wells, and Soil gas survey data. The first three files in the
Field submittals provide information pertaining to the site, the site EDD contact, and site sampling
locations. These files 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 first three files
in the Field EDD section, sometimes; data provider will submit a cover letter or base maps in the Files_v3
in the Facility secion. Table 2-2 provides general information on the field data files in the Field EDD
section.
Table 2-1 General information on the files that comprise the first three files in the Field EDD
section
File Type
File Name
Created By
Contents
What makes a
row of data
unique?
Dependenc
e of other
files on
these data
Data
Provider
EPAR5DATAPROVIDER
_v3.txt (or csv)
Data
Provider
Information about the
data provider
DataProvider
Not
applicable
Region 5 EDD Comprehensive Specification Manual
Version 4.2 3
United States
Environmental Protection Agency
-------
File Type
File Name
Created By
Contents
What makes a
row of data
unique?
Dependenc
e of other
files on
these data
Subfacility
(Section 3.3)
EPAR5 SUBFACILITY^
3.txt (or csv)
Data provider
One-time definition of
site including EPA
Region 5 data
providers' contact
information.
Facilitycode,
subfacilityname
5
subfacility_task_
code... etc
The location
file cannot
be loaded
without
properly
referenced
subfacility
(facilitycod
e).
Location
(Section 3.4)
EPAR5LOC_v3.
txt (or csv)
Data provider's
surveyor
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.
sysloccode
Sample,
water levels,
field
measuremen
ts, and
extraction
well data
can only be
reported for
locations
that are
defined in
this file.
Data provider, Subfacility, and location files are generally only need to be submitted once at the
beginning of the project, along with the Files_v3 file in the Facility section.
File Type
File Name
Created by
Contents
What makes a
row of data
unique?
Dependence
of other
files on
these data
File_v3
The site's base map in
Lat/Long and the file
format must be in .dxf or
drawing (.dwg) or ArcGIS
Shape files.
Another file type can be
documents or pdf, such as
cover letter or any kind of
documents.
Data provider
#1. Basemap of sites
in (.dxf), drawing
(.dwg), or ArcGIS
Shape File.
#2. Cover letter or any
documents in .pdf or
doc files
Not applicable
Not
applicable.
Field EDD submittals contain data obtained during subsurface investigations at the site. When submitting
the Field EDD, all field EDD files for which information is available should be submitted. The Field
EDD includes files for Drilling Activity (EPAR5DRA_v3), lithology data (EPAR5LTH_v3), general well
information (EPAR5EPAR5WEL_v3), well construction information (EPAR5WSG_v3), geology sample
data (EPAR5GSMP_v3), general information about the water table (EPAR5GWTR_v3), Water Table
(EPAR5TBL_v3), downhole logging methods point data (EPAR5DHP_v3), extraction and injection well
Region 5 EDD Comprehensive Specification Manual
Version 4.2 4
United States
Environmental Protection Agency
-------
(ExtractionlnjectionWells), soil gas survey data (SoilGas). Unlike the Lab 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 (Q&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 3.
Table 2-2 provides general information on the files that make up the field files in the Field EDD. Detailed
instructions for creating the Field EDD files are provided in Section 3, "Formats for Field Files".
Instructions for submitting your EDDs to EPA Region 5 are presented in Section 2.15.
Table 2-2 General information on the files that comprise the field files in the Field EDD section
File Type
File Name
Created By
Contents
What makes a row of
data unique?
Dependence
of other files
on these data
Drilling
Activity
(Section 3.5)
EPAR5DRA_v3.
txt (or csv)
Data
provider's
geologist
General Information
regarding soil
borings.
sysloccode
drillevent
None.
Lithology
(Section 3.6)
EPAR5LTH_v3.txt
(or csv)
Data
provider's
geologist
Lithology data for
the borings.
sysloccode
startdepth
None.
Well
(Section 3.7)
EPAR5 WEL_v3.
txt (or csv)
Data
provider's
geologist
General information
regarding well
installation.
sysloccode
Well
construction
and water
level data can
only be
reported for
wells that are
defined in
this file.
Well
Construction
(Section 3.8)
EPAR5WSG_v3.txt
(or csv)
Data
provider's
geologist
Well construction
details recorded
during well
construction and
well segments.
sysloccode
segmenttype
startdepth
enddepth
material_type_
code
depth unit
None.
Geology
Samples
(Section 3.9)
EP AR5 GSMP_v3.
txt (or csv)
Data
provider's
geologist or
laboratory
Contains
geotechnical sample
information
Sysloccode,
geosamplecode
None.
Water Level
(Section 3.10)
EP AR5 G WTR_v3. tx
t (or csv)
Data
provider's
field
sampling
team(s)
Contains water
levels measured
from he soil borings
or wells
sysloccode
measurementdate
None.
Water
Table
(Section 3.11)
EPAR5TBL_v3.
txt (or csv)
Data
provider's
geologist
General information
pertaining to water
table.
sysloccode
type
None.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 5
United States
Environmental Protection Agency
-------
File Type
File Name
Created By
Contents
What makes a row of
data unique?
Dependence
of other files
on these data
Downhole
Point (CPT)
Data
(Section 3.12)
EPAR5DHP_v3.
txt (or csv)
Data
provider's
geologist
Results of all
downhole logging
such as CPT,
resistivity, or other
geophysical logs.
sysloccode
depth
param
None.
Extraction-
Injection Well
(Section 3.13)
EPAR5EIW_v3.
Txt (or csv)
Data
provider's
field
sampling
team(s)
Data that relates to
any extraction wells
that are operating as
part of the remedial
action and injection
wells.
sysloccode
startmeasurementdate
endmeasurementdate
None.
Soil Gas
(Section 3.14)
EP AR5 SoilGas_v3.
Txt (or csv)
Data
Provider's
geologist
Results of
information
regarding the soil
gas
sysloccode
None
2.3 Lab Data Submittals
Lab EDDs are submitted after each round of sampling and include the following types of files: chemistry
sample information (EPAR5SMP_v3), Test Result (EPAR5TRS_v3), test/results with QC
(EPAR5TRSQC_v3), batch information (EPAR5BAT_v3).
Table 2-3 provides general information on the files that make up the Lab EDD files. Detailed instructions
for creating the Lab EDD files are provided in Section 4, "Formats for Lab EDD Files". Instructions for
submitting your EDDs to EPA Region 5 are presented in Section 2.15.
Table 2-3 General information on the files that comprise the Chemistry EDD
File Type
File Name
Created
By
Contents
What makes a row
of data unique?
Dependence of
other files on
these data
Sample
(Section 4.1)
EP AR5 SMP_v3.
txt (or csv)
Data
provider's
field
sampling
team(s)
One row for
each sample
collected at the
site.
syssamplecode
samplematrixcode
sampletypecode
samplesource
sampledate
Tests/results QC
and batch data can
only be reported
for samples that
are defined in this
file.
Test Result
(Section 4.2)
EPAR5TRS_v3.txt
(or csv)
Data
provider's
field
sampling
team (s)
Contains data
concerning
analytical tests
and results
performed on
samples.
Syssamplecode
Labanlmethodna
me
Analysisdate
None
Region 5 EDD Comprehensive Specification Manual
Version 4.2 6
United States
Environmental Protection Agency
-------
Table 2-3 General information on the files that comprise the Chemistry EDD
File Type
File Name
Created
By
Contents
What makes a row
of data unique?
Dependence of
other files on
these data
Test/ Result
with QC
Data
(Section 4.3)
EPAR5TRSQC_v3.tx
t (or csv)
Data
provider's
contractor
lab(s)
Test/Result file
with additional
fields for QC
data.
syssamplecode
lab_anl_method_
name
analysisdate
analysistime
totalordissolved
testtype
casrn
None.
Batch
(Section 4.4)
EPAR5BAT_v3.
txt (or csv)
Data
provider's
contractor
lab(s)
Data that relate
the individual
samples to the
batch identifier
syssamplecode
lab_anl_method_
name
analysisdate
analysistime
totalordissolved
testtype
test batch type
None.
2.4 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 6.5.1 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 which can be obtained from the EPA Region 5 database
administrator. Please email to canar.iohn@epa.gov for the information.
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.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 7
United States
Environmental Protection Agency
-------
Sign and Submit" |—£3—1|
User Name: I
Password:
Facility ID:
0
Save Password | Save
Figure 13: Sign and Submit Window
2. Enter your User Name and Password, and select the facility ID from the drop down that applies to the
data package being submitted. If the Facilty ID does not exist, users can send a request to Region 5
contact to add it to the list.
3. Click the Save button, and verify if the facility you selected is corrected:
Sign and Submit
£3
EPAR5 Sign And Submit
o Are you sure this is the correct facility?
Yes
No
Figure 14: verify the facility
4. Click "Yes". 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 Facility ID, a period and the Format File name used to create the EDDs. (Example file
name: '20160811. MID000000001.EPAR5.zip"). The contents of the Zipped file include 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.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 8
United States
Environmental Protection Agency
-------
erName: usemame
EQuIS Professional
35
IC
EDD Signed and Saved
OK
Figure 15: saved the EDD file
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 EDD file naming convention
Each file, except the base map file, must be named according to the following convention:
EDDFileFormat_v3.txt (or .csv)
This is the same file name as it is shown in th EPA Region 5 EDD fomat. The name of the site base map
file should include the site name and EPAID and be saved in .dxf format.
Table 2-4 describes the naming formats and for the various Initial, Chemistry and Geology EDD files.
Table 2-4 EDD File Naming Formats
File
Type
File Contents
EDD File Name
Submittal
Type
Facility
File
Sitename.DXF, *.dwg, or shape files from ArcGIS, or
Sitename.doc files from MS WORD for cover letters
Non-
Recurring
Field
Data Provider
EPAR5DataProvider v3.txt
Initial
Field
Subfacility
EPAR5 Subfacility v3.txt
Initial
Field
Location
EPAR5LOC v3.txt
Initial
Field
Drill Activity
EPAR5DRA v3.txt
Non-
Recurring
Field
Lithology
EPAR5LTH v3.txt
Non-
Recurring
Field
Well
Wel_v3 .txt
Non-
Recurring
Field
Well
Construction
EPAR5WSG_v3.txt
Non-
Recurring
Field
Geotechnical
Sample
EPAR5GSMP_v3.txt
Non-
Recurring
Field
Water Level
EPAR5GWTR v3 .txt
Recurring
Field
Water Table
EPAR5TBL v3.txt
Non-
Recurring
Region 5 EDD Comprehensive Specification Manual
Version 4.2 9
United States
Environmental Protection Agency
-------
Table 2-4 EDD File Naming Formats
File
Type
File Contents
EDD File Name
Submittal
Type
Field
Down Hole
Point (CPT)
Data
EPAR5DHP_v3.txt
Non-
Recurring
Field
Extraction -
Injection Well
EPAR5EIW_v3.txt
Recurring
Field
Soil Gas Data
EPAR5SoilGas v3.txt
Non
Recurring
Lab
Sample
EPAR5SMP v3.txt
Recurring
Lab
Test Result
EPAR5TRS v3.txt
Recurring
Lab
Test/Results
QC
EPAR5TRSQC_v3.txt
Recurring
Lab
Batch
EPAR5BAT v3 .txt
Recurring
2.5 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, and 4 or in the tables in the Appendix
of this manual. For example, sample matrix information is inputted in the samplematrixcode 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 Lab EDD files are shown in Figure 2-1. The lines connecting the
Region 5 EDD Comprehensive Specification Manual
Version 4.2 10
United States
Environmental Protection Agency
-------
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 SUBFACILTY 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 is limited to the
requirement that all entries in the sys loc code fields appear in the LOCATION EDD file.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 11
United States
Environmental Protection Agency
-------
Figure 2-1 Relationships between Lab file data structures.
Location
Data_provider
Subfacility
1
subfacility _code
Facility _code
sys_loc_code
x_coord
ycoord
subfacility _name
surfelev
subfacility _task_code
subfacility _desc 1
elevunit
coord_type_code
observation_date
subfacility _desc2
longitude
latitude
alt_identifier
contact_name
horz_collect_method_code
addressl
horz accuracy value
horzaccuracyunit
address2
horz_datum_code
city
elev_collect_method_code
elev_accuracy_value
state
zip code
elev_accuracy_unit
elev_datum_code
source_scale
phone numbeer
subcontractor_name_code
verification_code
alt_phone_number
reference_point
fax_numbeer
geometric_type_code
rank
email address
loc_name
loc_desc
locjype
locpurpose
—~
primary site code
within_facility_yn
00
loc_county_code
loc_district_code
loc_state_code
loc_major_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
sys_sample_code
sample_name
sample_matrix_code
sampletypecode
sample_source
parent_sample_code
sample_delivery_group
sample_date
sample_time
sys_l°c_c°de
start_depth
end_depth
depth_unit
chain_of_custody
sent_to_lab_date
sample_receipt_date
sampler
sampling_company_code
sampling_reason
sampliiig_teclinique
task_code
collectionquarter
composite_yn
composite_desc
sample_class
custom_field_l
custom_field_2
custom_field_3
comment
Test Result QC
sys_sample_code
lab_aiil_method_name
aiialysis_date
total_or_dissolved
column_number
test_type
lab_matrix_code
aiialysis_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
aiialyst_name
instrument_id
comment
preservative
fmal_volume
fmal_volume_unit
cas_m
chemical_name
result_value
result_error_delta
result_type_code
sys_lo
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 5 EDD Comprehensive Specification Manual
Version 4.2 12
United States
Environmental Protection Agency
-------
2.6 Definition of a Facility, Site, and Location
To submit and error-free EDD, it is important to understand how EPA Region 5 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
j Site
/ Operable \
Unit 1 \
^Sys loc code:MW01
I Site
Operable
Unit 2 \
/\. Sys loc code:M^)2 J
\ \ Sys loc code:^¥03
/ ®Sys loc code: SB01
/ Site /
( Operable /
VUnit3 j/
Sample ID: S01234
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.7 Reporting Null Values
When a field is not listed as required in Sections 3, and 4 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-5 Examples of how to report null values
Example
Comment
"data_one""data_two" "data_three"
"data one","data two","data three"
O.K. All fields populated, one tab or comma
between fields.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 13
United States
Environmental Protection Agency
-------
Table 2-5 Examples of how to report null values
Example
Comment
"data one" "data_three"
"data one"„"data three"
O.K. Optional field not populated, 2 tabs or 2
commas between first and third field.
"data_one" "data_three"
"data one","data three"
Not O.K. Optional field omitted, only 1 tab or
comma between first and third field.
2.8 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 5 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 5 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-6 Cross-reference between the valid value tables in appendix and the EDD files
Valid Value Table
Name
Table
Number
Field Name
EDD File
Matrix
A-l
samplematrixcode, labmatrixcode
Chemistry
Samples,
Test/Results
Geometric type
A-2
Geometric type code
Location
Horizontal Collection
Method
A-3
horzcollectionmethodcode
Location
Horizontal Accuracy
Unit
A-4
horzaccuracyunit
Location
Horizontal Datum
A-5
horz datum code
Location
Elevation Collection
Method
A-6
elev_collect_method_code
Location
Elevation Datum
A-7
elev datum code
Location
Material
A-8
Material type
Basic Geology
Location Type
A-9
loc type
Location
Qualifier
A-10
lab qualifiers, validator qualifiers
Test/Results
Result Type
A-ll
result type code
Test/Results
Sample Type
A-12
sample type code
Chemistry Samples
Geologic Unit
A-13
Geologic_unit_code
Geotechnical
Samples
Standard Preparation
Method
A-14
lab_prep_meth
Test/Results
Analyte
A-15
cas rn, chemical name
Test/Results
Lab Analysis Method
Name
A-16
labanlmethodname
Test/ Results
Region 5 EDD Comprehensive Specification Manual
Version 4.2 14
United States
Environmental Protection Agency
-------
Valid Value Table
Name
Table
Number
Field Name
EDD File
Laboratory
A-17
lab name code
Test/Results
Unit
A-18
various unit fields throughout all files
All Files
Geology Soil Materials
A-19
material_type
Lithology, Geology
Samples
Well Segment and
Materials
A-20
segment_type, material_type_code
Well Construction
Hydrologic Unit Codes
(HUC)-Basin
A-21
locmajorbasin
Location
EPA Facility IDs
A-22
facility id, site name
Site
Company code
A-23
Data_provider
Location, Sample,
Test Result, Data
Provider
Total or dissolved
A-24
T otalordissolved
Test Result, Test
Result QC, Batch
Test Type
A-25
Test_type
Test Result, Test
Result QC, Batch
Test Batch Type
A-26
Test batch type
Batch
Reference Point
A-31
reference point
Location
Source scale
A-32
Source scale
Location
2.9 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-7 provides examples of reporting re-tests.
Table 2-7 Example of reporting re-tests
Test
Type
Chem
Name
Cas rn
Result
Value
Detect
Flag
Lab
Qualifiers
Reportable
Result
Result Comment
Initial
Benzene
71-43-2
1000
Y
E
No
too concentrated to
quantitate
Initial
Toluene
108-88-3
5
N
U
Yes
not detected
Initial
Xylenes
1330-20-7
5
N
U
Yes
not detected
dilution 1
Benzene
71-43-2
780
Y
Yes
Quantitated
2.10 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
detectionlimitunit fields, and must contain a null in the resultvaluefield. 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-8 presents
examples of how to report non-detects.
Table 2-8 Example of reporting non-detects
| Cas
Laboratory ||
rn
Result
Detect
Reporting Detection
Result comment
Region 5 EDD Comprehensive Specification Manual
Version 4.2 15
United States
Environmental Protection Agency
-------
Value
Flag
Detection
Limit
Limit Unit
qualifiers
108-88-3
.15
Y
.005
ug/ml
U
108-88-3
N
.005
ug/ml
not detected
U
2.11 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 nor a class can be
identified, the TIC should be identified as Unknown. The EPA Region 5 EDD only allows for reporting
up to 10 TICs. Only the 10 most concentrated or most relevant TICs should be reported. Table 2-9
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 UnkHydrocarb3. 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-9 Example nomenclature for TIC reporting
TIC Name
Number for TIC
Reported Name in cas rn
Unknown
1-10
Unknown 1 - Unknown 10
Unknown Hydrocarbon
1-10
UnkHydrocarbl - UnkHydrocarbl0
Unknown PAHs
1-10
UnkPAHl - UnkPAHIO
Unknown Aromatics
1-10
UnkAromaticl - UnkAromaticlO
Unknown VOA
1-10
UnkVOAl - UnkVOAlO
Unknown SV
1-10
UnkSVl -UnkSVIO
2.12 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 1038 to -1.401298 x 10~45 for negative values and from 1.401298 x 1045 to
3.402823 x 1038 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~324 for negative values and from 1.79769313486231 x 10308 to
4.94065645841247 x 10~324 for positive values, with a decimal precision of up to 15 digits.
Table 2-10 Data type descriptions
Type
Description
Decimal
Precision
Comments
Integer
Stores numbers from -32,768 to 32,767 (no
fractions).
None
'Y' or TNT
Boolean field used to indicate yes or no to a
question. Enter either Y orN.
NA
Time
Time in 24-hr (military) HH:MM:SS format.
NA
Text (8) is standard
length for time.
Date
Date format is MM/DD/YYYY.
NA
Text
Stores characters and numbers.
NA
Length restrictions are
indicated in
parentheses.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 16
United States
Environmental Protection Agency
-------
2.13 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-11 provides
instructions for creating tab-delimited text files from some widely-used software packages.
Region 5 EDD Comprehensive Specification Manual
Version 4.2 17
United States
Environmental Protection Agency
-------
Table 2-11 Instructions for producing tab-delimited text files from some software packages
Package
Type
Instructions
Access
Database
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.
Excel
Spreadsheet
1. Select "File," "Save As," from the top menu. Change
"Save as Type" to a "Text (Tab Delimited)" file. Press the
"Save" button.
Quattro® v8
Spreadsheet
1. Select "File," "Save As," from the top menu. Change the
"File Type" to "ASCII Text (Tab Delimited)." Press the
"Save Button."
Word
Word
Processor
[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).
Lotus 1-2-3
Spreadsheet
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 5 EDD Comprehensive Specification Manual
Version 4.2 18
United States
Environmental Protection Agency
-------
2.14 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 5. 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 5. EDD files that pass
through the EDP error-free should also result in error-free import at EPA Region 5.
EDP is currently available as a no-cost download from the EPA Region 5 website located at at
https://www.epa.gov/superfund/region-5-superfund-electronic-data-submission. Instructions on how to
install and use the EDP are also provided on the website.
2.15 Submitting Your EDD to EPA Region 5
Each EDD must be checked using the EDP and the most updated EDD format before submitting to EPA
Region 5. Please follow the three steps below to submit your EDD data:
Email to get the username. password:
-Send email to canar.iohn@epa.gov to get the username, and password. Data providers are
required to get the username, and password to use the Sign and Submit process to create a EDD zip
package after the data has been checked with the EDP with no errors. The Sign and Submit process
allows data provider to save the EDD in their preferred folder or directory. The EDD zip package should
be named using the naming convention that was shown in section 2.4.
Email to EPA Region 5 EOuIS Enterprise Database:
- Once the EDD zip file has been created, the EDD is ready to be emailed to EPA EQuIS
Enterprise processor. Please follow the following 2 steps:
1. Change the file extention from ".zip" to "edd". In other words, your EDD is zipped in EDP,
such as "20160811. MID000000001.EPAR5.zip", you need to change the file extention to ".edd",
meaning the file name will become "20160811. MID000000001.EPAR5.edd"
2. Send the ".edd" file to to EPAR5 @EQuISOnline.com
Notify EPA Region 5 when the data is sent to the EPA Region 5 EQuIS Enterprise database:
Please notify the EDD database adminstrator canar.iohn@epa.gov for each EDD that has been
emailed to the EPA Region 5 EQuIS Enterprise database.
EDD submittal types
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 5. EPA Region 5 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 5 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
Region 5 EDD Comprehensive Specification Manual
Version 4.2 19
United States
Environmental Protection Agency
-------
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 5. The files of an update submittal should contain only data for the records being
updated. For example, say a data provider submits an EDD in 2014 that includes a location file
(e.g., EPAR5LOC_v3.txt) that contains ten locations, and the EDD is accepted by EPA Region 5
and loaded into the EPA database. If, in 2016, 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 included in a cover letter and name the file
correctly. Note: All required fields need to be populated for the three locations regardless of
whether or not these fields were 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 5 EDD Comprehensive Specification Manual
Version 4.2 20
United States
Environmental Protection Agency
-------
2.16 Examples of Field, and Lab EDD Files
Examples of Field and Lab 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 5. In order to fit the examples
on one page, not all of the fields (i.e., columns) were included for certain files (e.g., Subfacility, Location, and 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.7 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 Field EDD ready for conversion to text file
Subfacilty File (EPAR5SUBFACILITY v3):
subfacility_co
de
subfacility_na
me
subfacility _task_c
ode
subfacility_des
cl
subfacility_de
sc2
contact_name
addressl
01
Facility Name
John Smith
23 Main Street
email address
abc(S?abd.com
Location File (EPAR5LOC v3):
Data provid
Facility cod
sys loc code
X coord
Y coord
surf elev
elev
coord type co
observatio
Longitude
Latitude
identifie
er
e
unit
de
n date
r
ABD
MID0000001
MW01
573535.16
46185.25
120.2
ft
UTM Zone 16
02/21/2015
440022.31
399612.23
1
ABD
MID0000001
SB-01
571535.28
46185.22
126.3
ft
UTM Zone 16
02/23/2015
9
442430.31
393574.22
1
ABD
MID0000001
MW03
571525.28
47558.33
130.1
ft
UTM Zone 16
02/22/2015
442470.22
399701.25
1
ABD
MID0000001
MW04
561528.33
46004.25
130.1
ft
UTM Zone 16
02/22/2015
442356.51
399701.48
1
comment
Sample File (EPAR5SMP v3):
Figure 2-4. Example Lab EDD ready for conversion to text file
Data_provider
sys_sample_
code
sample_
name
sample_
matrix code
sample_type_
code
sampleso
urce
parentsample
code
sampledelivery
group
sample_
date
sys_l°c_c°de
ABD
MW-
01 20150401
WG
N
Field
04/01/201512
:00:00
MW01
ABDE
MW-
02 20150401
WG
N
Field
04/01/2015
12:00:00
MW02
Additional
Fields
Region 5 EDD Comprehensive Specification Manual
Version 4.2 21
United States
Environmental Protection Agency
comment
-------
Test Result QC File (EPAR5TRSQC v3):
sys_sample_
lab anl
Additional
total or
column
test
lab matrix
analysis_
basis
code
method_
name
Fields
dissolved
number
type
_code
location
MW-
SW8240
T
Initial
WG
LB
Wet
01 20150401
MW-
SW8240
T
Initial
WG
LB
Wet
01 20150401
MW-
SW8240
T
Reanalysis
WG
LB
Wet
01 20150401
dilution_
factor
lab_
name_
code
qc_
level
lab_
sample
id
1.0
ABC
quant
LAB01
1.0
ABC
quant
LAB02
10.0
ABC
quant
LAB02R
Additional
Fields
Test Result QC (EPAR5TRSQC v3) (Continue):
casrn
chemical_
name
result_
value
result_
error_
delta
result_
type_
code
reportable
_result
detect_flag
lab_
qualifiers
Validate
d_yn
Methoddet
ection_limit
reporting_
detection
limit
Quantitation
_limit
result_
units
71-43-2
BENZENE
12
TRG
Yes
Y
Y
10
ug/ml
108-88-3
TOLUENE
TRG
Yes
N
Y
10
ug/ml
1330-20-7
XYLENES
TRG
Yes
N
Y
10
ug/ml
result_
comment
Figure 2-5. Examples of QC data fields in a Chemistry EDD
QC fields in a normal field sample (i.e., sample type code = N, TB, etc.)
casrn
result_value
qcoriginal
_conc
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
93-76-5
1.56
94-75-7
3.17
94-82-6
2.31
Region 5 EDD Comprehensive Specification Manual
Version 4.2 22
United States
Environmental Protection Agency
-------
QC fields in a normal field sample with surrogates (i.e., sampletypecode = N, TB, etc.)
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.
Casrn
result_value
result_unit
result_type_
code
qc_original_
cone
qc_spike_added
qc_spike_
measured
qe_spike_
recovery
93-76-5
1.56
mg/1
TRG
94-75-7
3.17
mg/1
TRG
PHEN2F
mg/1
SUR
12.5
12.9
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.
casrn
result_
value
lab_
qualifier
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
93-76-5
U
94-75-7
U
94-82-6
0.01
Region 5 EDD Comprehensive Specification Manual
Version 4.2 23
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., sampletypecode = 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 fie
d (qc spike recovery).
casrn
result_
value
qc_
original_
cone
qc_spike_
added
qc_spike_
measured
qc_spike_
recovery
Qc_rpd
qc_dup_
original_
cone
qc_dup_
spike_
added
qc_dup_
spike_
measured
qc_dup_
spike_
recovery
93-76-5
1.56
4.18
5.36
90.9
94-75-7
3.17
4.18
7.15
95.2
94-82-6
2.31
4.22
5.66
79.3
QC fields in a matrix spike duplicate (i.e., sample type code = SDj
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
casrn
result_
value
qc_
original_
cone
qc_spike_
added
qc_spike_
measured
qc_spike_
recovery
Qc_rpd
qc_dup_
original_
cone
qc_dup_
spike_
added
qc_dup_
spike_
measured
qc_dup_
spike_
recovery
93-76-5
10
1.56
4.23
5.70
97.8
94-75-7
12
3.17
4.23
7.62
105
94-82-6
15
2.31
4.13
5.33
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).
casrn
result_
value
qc_
original_
cone
qc_spike_
added
qc_spike_
measured
qc_spike_
recovery
Qc_rpd
qc_dup_
original_
cone
qc_dup
spike_
added
qc_dup
spike_
measured
qc_dup
spike_
recovery
93-76-5
1.56
4.18
5.36
90.9
7
1.56
4.23
5.70
97.8
94-75-7
3.17
4.18
7.15
95.2
10
3.17
4.23
7.62
105
94-82-6
2.31
4.22
5.66
79.3
8
2.31
4.13
5.33
73.1
Region 5 EDD Comprehensive Specification Manual
Version 4.2 24
United States
Environmental Protection Agency
-------
QC fields in a LCS (i.e., laboratory control sample, blank spike, sampletypecode = 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.
casrn
result
_value
qc_original
_conc
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
93-76-5
5.00
5.26
105
94-75-7
1.00
1.02
102
94-82-6
12.5
12.9
103
Figure 2-6. Example Field EDD ready for conversion to text file
Drill Activity File:
sys_l°c_c°de
drill_event
start_depth
end_depth
drill_date
diameter
W-4A
la
40
80
07/12/1999
8
W-6B
2c
45
110
07/14/1999
8
Additional
Fields
purpose
Advanced well additional 40 feet to reach lower aquifer
Advanced well 55 feet to reach bedrock.
Litholog
y File:
sys_loc_
code
start_
depth
material_
type
geo_unit_l
W-1A
0
CL
Glacial
W-1A
10
SW
Outwash
W-1A
23
SP
Outwash
W-2A
0
ML
Alluvial
Additional
Fields
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
Well File:
sys_l°c_c°de
W-1A
W-2A
Additional
Fields
top_casing_elev
datum_value
datum_unit
datum_desc
122.0
122.0
ft
top of casing of well
122.3
122.3
ft
top of casing of well
Additional
Fields
geologic_unit_
code
remark
outwash
alluvial
Region 5 EDD Comprehensive Specification Manual
Version 4.2 25
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_l°c_c°de
segment_type
material_type_code
start_depth
end_depth
depth_unit
inside_diameter
W-1A
surface plug
concrete
0
1.5
ft
4.5
W-1A
annular backfill
neat cement grout
1.5
8
ft
2.375
W-1A
annular Seal
Bentonite pellets
8
8
ft
2.375
W-1A
Filter Pack
sand pack
8
23.1
ft
2.375
W-1A
Protective Casing
steel
-2.2
3.2
ft
4
W-1A
Casing
stainless steel 304
-2.1
24
ft
2
W-1A
Screen
stainless steel 304
24
29
ft
2
W-2A
protective casing
steel
-2.0
3.0
ft
2
W-2A
surface plug
concrete
0
1.5
ft
4.5
W-2A
annular backfill
neat cement grout
1.5
10
ft
2.375
Additional
Fields
remark
Geology Sam
pie File:
sys_l°c_c°de
Geo_sample_code
sample_name
sample_top
samplejbottom
sample_date
Additional
Fields
sample_method
material_type
Additional
Fields
organiccarbon
units
W-1A
ABCD-1
4
6
04/23/1999
00:00:00
split spoon
SW
W-1A
ABCD-2
14
16
04/23/1999
00:00:00
split spoon
sw
W-2A
DEFG-1
5
7
04/24/1999
split spoon
SP
Region 5 EDD Comprehensive Specification Manual
Version 4.2 26
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_l°c_c°de
Type
sequence
Depth
flowing_yn
measurement_method
capped_pressure
cappedpressure
unit
MW01
Unconfmed
stable
21.2
y
electric sensor
MW02
Unconfmed
stable
21.0
y
electric sensor
Additional
Fields
temperature
unit
Downhole Point File:
sys_l°c_c°de
Depth
param
param_value
MW01
10.8
Tip Stress
612
MW01
11.2
Tip Stress
624
MW01
10.8
Sleeve Stress
6.1
MW01
11.2
Sleeve stress
5.8
MW02
9.5
Resistivity
510
MW02
10.1
Resistivity
521
MW02
11.0
Resistivity
489
Water Level File:
sys_l°c_c°de
measurement
date
historical_ref_elev
water_level_depth
w ater_level_elev
corrected_elev
MW01
05/10/1999
13:10:00
31.1
89.1
MW02
05/10/1999
13:45:00
34.1
89.0
Additional
Fields
remark
Extraction
njection Wells
sysjoe
_code
Start_
measurement
date
end measure
date
avg pump rate
pumprateunit
EX-01
05/12/2000 11:23:00
06/12/2000
11:30:00
2.5
mgd
EX-02
11/12/2000 12:00:00
12/12/2000
13:10:00
1.75
mgd
Additional
Fields
remark
Region 5 EDD Comprehensive Specification Manual United States
Version 4.2 27 Environmental Protection Agency
-------
3. FORMATS FOR Facility Files and Field Files
This section contains information regarding the base map and the two files included in the Facility EDD.
These files need to be submitted prior to, or in conjunction with, the first Field 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 Facility EDD Files
Site Base Maps in the file section (Files_v3)
Site base maps can be submitted in CAD files in a DXF interchange format, or drawing (.dwg) file, or
Shapfiles generated from ArcGIS. 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 5). 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 (or dwg, or shape files)
The file section allows you to load supplementary information into EQuIS, such as Map, drawing files.
The naming convention of the File_v3 is:
File_v3.txt (or .csv)
Table 3-1 Files (Files_v3) structure
Pos#
Column Name
Data type
Required
Description
Valid Values In
Appendix
1
File name
Text (255)
Yes
Name of the file
No
2
Filetype
Text (20)
Yes
Type of the file
No
3
Filedate
Date time
If available
Date of the file
No
4
Title
Text (255)
If available
Title of the file
No
5
Author
Text (255)
If available
Author of the file
No
6
Confidential _yn
Text (1)
If available
Whether or not the file is
confidential
No
7
Remark
Text (255)
If available
Remark for the file
No
8
Placetype
Text (50)
If available
Type of the place tis file
is associated with
No
9
Placecode
Text (50)
If available
Code/identifier of the
place this file is associate
with
No
10
Placesubcode
Text (50)
If available
Subcode/ identifier of the
place this file is
associated with
No
11
Content
Content of the file
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 28
United States
Environmental Protection Agency
-------
3.2. Field Files-DATAPROVIDER
This section contains tables that define the file structures for the FIELD EDD. The file structures include
the first three initial EDD files: Data Provier, Subfacility, and Locations, also the drilling activity,
lithology, well, well construction, geotechnical samples, water levels, Water Table, downhole point,
extraction injection wells, and Soil Gas 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.16.
Data Provider (EPAR5DATAPROVIDER_v3)
The Data Provider EDD file provides general information about the data provider who is the contact for
the data on the site.
EPAR5DataProvider_v3.txt (or .csv)
Table 3-2 Data Provider (EPAR5DataProvider_v3) File Structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
1
DataProvider
Text(20)
Required
This is the name of the company who is
responsible for providing the site data.
A-23
2
DataContact
Person
Text(30)
Not
Required
This is the name of the contact person
who is responsible for providing the site
data.
No
3
DataContact
Addressl
Text (40)
Not
required
Data Provider address 1
No
4
DataContact
Address2
Text (40)
Not
required
Data Provider address 2
No
5
DataContact
City
Text (30)
Not
required
Data Provider city
No
6
DataContact
State
Text(5)
If Available
Contact state
No
7
DataContactzi
pcode
Text(10)
Not
required
Contact zip
No
8
DataContact
email
Text(60)
Required
Contact email address
No
9
DataContact
Phone
Text(30)
Not
Required
Contact phone number
No
3.3 SUBFACILITY EDD File
The SUBFACILITY 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. An example of a
Subfacility file is provided in Figure 2-3, section 2.16. NOTE: If the SUBFACILITY EDD file was
previously submitted, including as part of a "Historic Data EDD", as described in the Region 5 "EDD
Manual for Historical Data", you DO NOT need to resubmit the file again.
Each SUBFACILITY file must be named according to the following convention:
EPAR5SUBFACILITY_v3.txt (or .csv)
Region 5 EDD Comprehensive Specification Manual
Version 4.2 29
United States
Environmental Protection Agency
-------
Table 3-3 SUBFACILITY (EPAR5SUBFACILITY v3) data file structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
1
SUBFACILITYc
ode
Text(20)
Required
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.
No
2
subfacility name
Text(60)
Required
Name of site
Table A-22
3
sitetaskcode
Text(40)
Required
Code used to associate individual
samples to a specific sampling event.
The format for this field is XX-P#, XX
is the type of task required and P# is
the phase.
No
4
subfacility descl
Text(255)
If available
General description of the site.
No
5
subfacility_desc2
Text(255)
If available
Additional description of site, if
necessary.
No
6
contactname
Text(50)
Required
Name of person to contact if EPA
Region 5 has any questions about the
EDD.
No
7
addressl
Text(40)
Required
Site address, part one.
No
8
address2
Text(40)
Not required
Site address, part two. Default to null
if information is not needed
No
9
City
Text(30)
Required
Site city.
No
10
State
Text(2)
Required
Site state.
No
11
Zipcode
Text(10)
Required
Site zip code.
No
12
phone number
Text(30)
Required
Site contact phone number.
No
13
alt_phone_number
Text(30)
If available
Alternate phone number for site
contact. Default to null where the
data are not available.
No
14
faxnumber
Text(30)
If available
Fax number of site contact. Default
to null where the data is not
available.
No
15
email address
Text(lOO)
Required
Site contact e-mail address.
No
3.4 Location EDD File (EPAR5LOC_v3)
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).
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
Region 5 EDD Comprehensive Specification Manual
Version 4.2 30
United States
Environmental Protection Agency
-------
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.15 "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-4 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 5 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.16.
Each Location file must be named according to the following convention:
EPAR5LOC_v3.txt (or .csv)
Table 3-4 Location Data (EPAR5LOC_v3) File Structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
1
Data Provider
Text(20)
Required
Data Prodiver company code
A-23
2
Facility code
Text (20)
Required
Facility ID
A-22
3
sysloccode
Text(20)
Required
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 =
"FAC CENTER POINT"
No
4
Xcoord
Number
w/decimal
precision
up to 15
Required
Sampling location numeric x
UTM NAD83 coordinate in
meters.
No
5
Ycoord
Number
w/decimal
precision
up to 15
Required
Sampling location numeric y
UTM NAD83 coordinate in
meters.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 31
United States
Environmental Protection Agency
-------
Table 3-4 Location Data (EPAR5LOC_v3) File Structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
6
surfelev
Number
w/decimal
precision
up to 15
Not Required
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).
No
7
elevunit
Text(15)
Required
Unit of measurement for
elevations.
Units must be in
ft/m
8
coordtypecode
Text(20)
Required
Sampling location coordinate
system description. Must be
'UTM Zone nn'
No
9
observationdate
DateTime
Not required
Date observation or site
survey was made.
No
10
Longitude
Text(20)
Not required
X_ state plane or UTM
NAD83 coordinate
No
11
Latitude
Text(20)
Not required
Y_ state plane or UTM
NAD83 coordinate
No
12
identifier
Text(20)
Not required
Use State Plane or UTM
NAD83. Code for the
coordinate type used for alt x
and alt_y.
Values are:
'UTM ZONE 17',
'UTM ZONE 18',
'SP'
No
13
horz collect method c
ode
Text(2)
If available
Method used to determine the
latitude/longitude
measurements. Horizontal
Collection Method.
Table A-3
14
horzaccuracyvalue
Text(20)
Not required
Accuracy range (+/-) of the
latitude and longitude. Only
the least accurate
measurement should be
reported, regardless if it is for
latitude or longitude.
No
15
horzaccuracyunit
Text(l)
If available
Unit of the horizontal
accuracy value.
Table A-4.
Enumeration list
contains the
codes and
description
16
horzdatumcode
Text(l)
If available
Reference datum of the
x coord and y coord
Table A-5
Region 5 EDD Comprehensive Specification Manual
Version 4.2 32
United States
Environmental Protection Agency
-------
Table 3-4 Location Data (EPAR5LOC_v3) File Structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
17
elevcollectmethodc
ode
Text(2)
If available
Method used to determine the
ground elevation of the
sampling location.
Table A-6
18
elevaccuracyvalue
Text(20)
Not required
Accuracy range (+/-) of the
elevation measurement.
19
elevaccuracyunit
Text(8)
Not required
Unit of the elevation accuracy
value.
Table A-18.
Enumberation
list contains the
codes and
description.
20
elevdatumcode
Text(l)
If available
Reference datum for the
elevation measurement
Table A-7
21
sourcescale
Text(2)
Not required
Scale of source used to
determine the x coord and
y coord.
Table A-32
22
subcontractornameco
de
Text(20)
If available
Code used to distinguish
subcontractor name.
Table A-23
23
verificationcode
Text(l)
Not required
This field is only to be used by
EPA Region 5 personnel.
Please leave blank.
No
24
reference_point
Text(2)
Not required
Describes the place at which
coordinates were established.
Use codes from Table A-2 in
the Appendix.
Tabel A-31
Enumeration list
is available in
this field.
25
geometrictypecode
Text(20)
If available
Value: 'POINT'
A-2
26
Rank
Numeric
Not required
This field is for by EPA
Region 5 future use. Please
leave blank.
No
27
loc name
Text(40)
Not required
Sampling location name.
No
28
loc desc
Text(255)
Not required
Sampling location description.
No
29
loctype
Text(10)
If available
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.
Table A-9
30
loc purpose
Text(20)
Not required
Sampling location purpose.
No
31
Primarysubfacilityco
de
Text(20)
Required
Unique code for site or area.
Must match subfacility code
field from Table 3-3:
Subfacility File Data
Structure.
No
32
within_facility_yn
Text(l)
Required
Indicates whether this
sampling location is within
facility boundaries, "Y" for
yes or "N" for no.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 33
United States
Environmental Protection Agency
-------
Table 3-4 Location Data (EPAR5LOC_v3) File Structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
33
loccountycode
Text(20)
Not required
Location county code;
controlled vocabulary using
FIPS (Federal Information
Processing Standard) codes.
FIPS codes can be found via
the internet at
https://www.epa.gov/envir
o/state-fips-code-listing
No
34
locdistrictcode
Text(20)
Not required
Use the EPA region code
'005'
No
35
locstatecode
Text(10)
If available
Location state code; controlled
vocabulary using FIPS codes.
No
36
locmajorbasin
Text(8)
If available
Location major basin;
controlled vocabulary using
HUC (hydrologic unit codes
Table A-21
37
locminorbasin
Text(20)
Not required
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.
No
38
Remarks
Text(255
)
Not required
Location specific comment.
No
39
totaldepth
Number
w/decimal
precision
up to 15
Not required
Total depth below ground
surface of boring, in feet.
No
40
depthtobedrock
Number
w/decimal
precision
up to 15
Not required
Depth below ground surface
of bedrock in feet.
No
41
depthto topofscreen
Number
w/decimal
precision
up to 15
Not required
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.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 34
United States
Environmental Protection Agency
-------
Table 3-4 Location Data (EPAR5LOC_v3) File Structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
42
depthtobottomofsc
reen
Number
w/decimal
precision
up to 15
Not required
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.
No
43
topcasingelev
Number
w/decimal
precision
up to 15
Not required
Elevation of the top of casing
in feet.
Leave null if well is not at this
location.
No
44
datumvalue
Number
w/decimal
precision
up to 15
Not required
Datum value
No
45
datum unit
Text (15)
If available
Datum unit
Table A-18
46
steporlinear
Text (6)
Not required
This field is for by EPA
Region 5 future use. Please
leave null.
Value: 'Step', 'Linear'
No
47
datumcollectmethod
code
Text (2)
Not required
Datum collect method
No
48
datum desc
Text(70)
Not required
Datum description
No
49
Datum start date
DateTime
Not required
Datum start date
No
3.5 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:
EPAR5DRA_v3.txt (or .csv)
Table 3-5 Drill activity (EPAR5DRA_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
1
sysloccode
Text (20)
Required
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-4) submitted in the current or
previous EDD.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 35
United States
Environmental Protection Agency
-------
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
2
drillevent
Text (20)
Required
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.
No
3
startdepth
Number
w/decimal
precision
up to 7
Not
required
The start depth, in feet below ground
surface, of the drilling.
No
4
enddepth
Number
w/decimal
precision
up to 7
Not
required
End depth, in feet below ground surface of
the drilling.
No
5
drilldate
Date Time
Not
required
Date drilling began
MM/DD/YYYY
format.
6
Diameter
Number
w/decimal
precision
up to 7
Not
required
Diameter of boring.
No
7
diameterunit
Text (15)
If
available
Unit corresponding to measured diameter.
See Table A-18 in the Appendix for
appropriate value.
Table A-18
8
drillmethod
Text (50)
Not
required
Method used to drill boring.
No
9
fluid
Text (50)
Not
required
Description of fluid used during drilling.
No
10
viscosity
Text (50)
Not
required
Viscosity of drilling fluid.
No
11
hammerwt
Text (50)
Not
required
Weight of hammer, in pounds, used for
sampling.
No
12
hammerfall
Text (50)
Not
required
Distance of hammer fall during sampling in
inches.
No
13
liftmechanism
Text (50)
Not
required
Type of mechanism used to lift hammer.
No
14
new_Yn
Text (1)
Not
required
This field is to indicate whether this is a
new boring. Enter "Y" for yes or "N" for
no.
Y = yes
N= no
15
repair_yn
Text (1)
Not
required
Is this drilling event to repair an existing
boring? "Y" for yes or "N" for no.
Y = yes
N= no
16
deepen_yn
Text (1)
Not
required
Is this drilling event to deepen an existing
boring? "Y" for yes or "N" for no.
Y = yes
N= no
17
abandon_yn
Text (1)
Not
required
Has the boring been abandoned? "Y" for
yes or "N" for no.
Y = yes
N= no
18
replace_yn
Text (1)
Not
required
Is this boring event to replace an existing
boring? "Y" for yes or "N" for no.
Y = yes
N= no
19
public_yn
Text (1)
Not
required
Is well being install for a public use? "Y"
for yes or "N" for no.
Y = yes
N= no
20
Purpose
Text (70)
Not
required
Describe the purpose of the boring event.
No
3.6 Lithology EDD 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
Region 5 EDD Comprehensive Specification Manual
Version 4.2 36
United States
Environmental Protection Agency
-------
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:
EPAR5LTH v3.txt (or .csv)
Table 3-6 Lithology (EPAR5LTH_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Valued
In Appendix
1
sysloccode
Text(20)
Required
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-4) submitted in the
current or previous EDD.
No
2
startdepth
Number
w/decimal
precision
up to 15
Required
The start depth, in feet below ground
surface, of the lithologic unit.
No
3
materialtype
Text(40)
If
available
The type of material that composes the
lithologic unit. See Table A-19 in the
Appendix for appropriate values.
Table A-19
4
geounitcodel
Text(20)
If
available
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.
No
5
geo_unit_code_2
Text(20)
If
available
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.
No
6
remarkl
Text(255)
Not
required
Comments (if any) on the lithologic unit.
No
7
remark_2
Text(255)
Not
required
Additional comments on the lithologic
unit.
No
8
Moisture
Text(l)
Not
required
Was any moisture detected within the
lithologic unit? "Y" for yes or "N" for no.
Y = yes
N=No
9
Permeable
Text(20)
Not
required
Description of the permeability of the
lithologic unit such as "impervious,"
"semi," "pervious," or "very."
No
10
consolidatedyn
Text(l)
Not
required
Was lithologic unit consolidated? "Y" for
yes or "N" for no.
Y=yes
N=no
11
Color
Text(20)
Not
required
Color of the lithologic unit.
No
12
Observation
Text(255)
Not
required
General field observations of the
lithologic unit.
No
13
Consistency
Text(20)
Not
required
Description of the consistency of the soil,
such as "very soft," "soft," "firm," "hard"
or "very hard."
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 37
United States
Environmental Protection Agency
-------
Table 3-6 Lithology (EPAR5LTH_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Valued
In Appendix
14
Sorting
Text(20)
Not
required
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.
No
15
Grainsize
Text(20)
Not
required
Description of grain size.
No
16
Odor
Text(20)
Not
required
Description of odor from the soil.
No
3.7 Well EDD File
The well (EPAR5WEL_v3) EDD file contains general information relating to well installation. Each well
file must be named according to the following convention:
EPAR5WEL_v3.txt (or .csv)
Table 3-7 Well (EPAR5WEL_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Value
In Appendix
1
sysloccode
Text(20)
Required
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-4)
submitted in the current or previous EDD.
No
2
Alternate Well
id
Text(30)
Not required
Well identification number
No
3
welldescriptio
n
Text(30)
Not required
Used for additional well description if
necessary.
No
4
well owner
Text(30)
Not required
Name of entity that owns the well.
No
5
well_purpose
Text (20)
Not required
Purpose of well.
No
6
well status
Text (20)
Not required
Current status of well.
No
7
top_casing_
elev
Number
w/decim
al
precision
up to 15
Not required
Elevation of the top of well casing.
Elevation must be in feet.
No
8
datumvalue
Number
w/decim
al
precision
up to 15
Required
Elevation of datum used to reference
measurement of water level depths. (EPA
normally uses top of well casing for datum.)
No
9
datum unit
Text(15)
Required
Unit of measure for the well datum..
Table A-18
10
datumdesc
Text (70)
Required
Description of the datum, such as "top of
well casing."
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 38
United States
Environmental Protection Agency
-------
Table 3-7 Well (EPAR5WEL_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Value
In Appendix
11
steporlinear
Text (6)
Not required
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.
No
12
Datumstartda
te
DateTim
e
Required
Date that datum was first used to take
measurements.
MM/DD/YYYY
format.
13
datum_collect_
methodcode
Text (2)
If available
Method used to determine the datum
elevation. Use codes from Table A-6 in the
Appendix
Table A-6
14
depthofwell
Number
w/decim
al
precision
up to 15
Not required
Depth below ground surface of the well
bottom.
No
15
depth unit
Text (15)
If available
Unit of measurement for depth.
Table A-18
16
depth_measure_
method
Text (20)
Not required
Method of measuring depth of well.
No
17
stickup height
Text (8)
Not required
Height of casing above ground surface.
No
18
stickup unit
Text (15)
If available
Unit of measure for the stickup height
Table A-18
19
sump length
Text (20)
Not required
Length of sump.
No
20
sump unit
Text (15)
If available
Unit of measure for the sump length.
Table A-18
21
Installationdat
e
Date
Not required
Date of well installation
MM/DD/YYYY
format.
22
construct_start_
date
DateTim
e
Not required
Date well construction began
MM/DD/YYYY
format.
23
constructcomp
lete date
DateTim
e
Not required
Date well construction was completed
MM/DD/YYYY
format.
24
construct_
contractor
Text (20)
If available
Name of contractor that installed well.
No
25
pumptype
Text (20)
Not required
Type of pump used at well such as
centrifugal, propeller, jet, helical, rotary,
etc.
No
26
pump capacity
Text (6)
Not required
Capacity of pump.
No
27
pumpunit
Text (15)
If available
Unit of measure for the pump capacity and
yield.
Table A-18
28
pump yield
Text (6)
Not required
The yield of the pump.
No
29
pump_yield_
method
Text (20)
Not required
Method used for pump yield.
No
30
weephole
Text (1)
Not required
Is there a weep hole? "Y" for yes or "N" for
no.
Y=yes
N=No
31
headconfigurat
ion
Text (50)
Not required
Description of the well-head.
No
32
access_port_yn
Text (1)
Not required
Is there an access port? "Y" for yes or "N"
for no.
Y=yes
N=No
33
casing J ointty
pe
Text (50)
Not required
Type of casing joint, such as "threaded,"
"flush," or "solvent-welded."
No
34
Perforatorused
Text (50)
Not required
Description of well perforation, such as
"slotted," "drilled," or "wound."
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 39
United States
Environmental Protection Agency
-------
Table 3-7 Well (EPAR5WEL_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Value
In Appendix
35
intakedepth
Number
w/decim
al
precision
up to 15
Not required
Depth in feet below ground surface of the
well intake.
Feet
36
Disinfectedyn
Text (1)
Not required
Was well disinfected? "Y" for yes or "N"
for no.
Y=yes
N=No
37
historical_
referenceelev
Number
w/decim
al
precision
up to 15
Not required
Leave null.
No
38
geologicunitc
ode
Text (20)
If available
Geologic unit in which the well intake is
installed.
No
39
Remark
Text
(255)
Not required
Available for general remarks.
No
3.8 Well Construction EDD 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:
EPAR5WSG_v3.txt (or .csv)
Table 3-8 Well construction (EPAR5WSG_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Value
In Appendix
1
sysloccode
Text(20)
Required
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-4)
submitted in the current or previous EDD.
No
2
segmenttype
Text(20)
Required
Type of segment within well (e.g.,
protective casing, well casing, screen,
etc.).
Table A-20
3
material_type_
code
Text(20)
Required
Material description of well segment. Use
values.
Table A-20
4
startdepth
Number
w/decimal
precision
up to 15
Required
Depth, in feet below ground surface, of
the top of the described segment.
No
5
enddepth
Number
w/decimal
precision
up to 15
Required
Depth, in feet below ground surface, of
the bottom of the described segment.
No
6
depth unit
Text(15)
Required
The unit of depth measurements.
Table A-18
Region 5 EDD Comprehensive Specification Manual
Version 4.2 40
United States
Environmental Protection Agency
-------
Table 3-8 Well construction (EPAR5WSG_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Value
In Appendix
7
innerdiameter
Number
w/decimal
precision
up to 15
Not
required
The inside diameter of the described
segment.
No
8
outerdiameter
Number
w/decimal
precision
up to 15
Not
required
The outside diameter of the described
segment.
No
9
diameterunit
Text(15)
If
available.
The unit of diameter measurements
Table A-18
10
Thickness
Number
w/decimal
precision
up to 15
Not
required
Thickness of the described well segment.
No
11
thicknessunit
Text(15)
If
available
The unit of measurement for thickness.
Table A-18
12
slottype
Text(20)
Not
required
Type of slots in screen segment such as
bridge, shutter, and continuous.
No
13
slotsize
Number
w/decimal
precision
up to 15
Not
required
Width of slots.
No
14
slotsizeunit
Text(15)
If
available
The unit of measurement for slot size..
Table A-18
15
perflength
Number
w/decimal
precision
up to 15
Not
required
Length of perforated portion of screen in
feet.
No
16
screentype
Text(15)
Not
required
Type of screen.
No
17
materialquant
ity
Text(20)
Not
required
Quantity of material used in pounds.
Applicable to annular seal/fill material.
No
18
materialdensi
ty
Text(20)
Not
required
Density of the annular seal material in
lbs/ft3.
No
19
Remark
Text(255)
Not
required
Remarks regarding the segment.
No
3.9 Geology Samples EDD File
The Geology Samples (GSMP) EDD file contains geotechnical sample information. (Samples results
related to chemical analyses should be reported using the Lab EDD.) Each Geology sample EDD file
must be named according to the following convention:
EPAR5GSMP_v3.txt (or .csv)
Table 3-9 Geology samples (EPAR5GSMP_v3) file data structure
Pos#
Column
Data
Required
Description
Valid Values
Name
Type
In Appendix
Region 5 EDD Comprehensive Specification Manual
Version 4.2 41
United States
Environmental Protection Agency
-------
Table 3-9 Geology samples (EPAR5GSMP_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
1
sysloccode
Text(20)
Required
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-4) submitted in the current
or previous EDD.
No
2
geo_sample_
code
Text(40)
Required
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.
No
3
samplename
Text(50)
Not
required
Use to provide a name or description of
sample. Does not have to be a unique
throughout database.
No
4
sampletop
Number
w/decimal
precision
up to 15
Required
Depth, in feet below ground surface, to
top of sample.
No
5
sample_
bottom
Number
w/decimal
precision
up to 15
Required
Depth, in feet below ground surface, to
bottom of sample.
No
6
Sampledate
DateTime
Not
required
Date sample was collected.
MM/DD/YYYY
HH:MM:SS
format
7
sample_
method
Text(30)
If
available
Method used to obtain sample, e.g., split
spoon or Shelby tube.
No
8
materialtype
Text(40)
If
available
Material type of geologic sample. .
Table A-8
9
sampledesc
Text(255)
Not
required
General description of the sample or
sampling activities.
No
10
geologic_
unit code
Text(20)
If
available
Code used to identify the geologic unit of
the sample.
No
11
liquidlimit
Number
w/decimal
precision
up to 7
Not
required
Liquid limit (LL) of the sample.
No
12
plasticlimit
Number
w/decimal
precision
up to 7
Not
required
Plastic Limit (PL) of the sample.
No
13
shrinkage_
limit
Number
w/decimal
precision
up to 7
Not
required
Shrinkage limit of the sample.
No
14
flowindex
Number
w/decimal
precision
up to 7
Not
required
Flow index of the sample.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 42
United States
Environmental Protection Agency
-------
Table 3-9 Geology samples (EPAR5GSMP_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
15
plasticity_
index
Number
w/decimal
precision
up to 7
Not
required
Plasticity index of the sample.
No
16
Activity
Number
w/decimal
precision
up to 7
Not
required
Activity of the sample.
No
17
E
Number
w/decimal
precision
up to 7
Not
required
Void ratio of the sample.
No
18
emax
Number
w/decimal
precision
up to 7
Not
required
Maximum void ratio of the sample.
No
19
emin
Number
w/decimal
precision
up to 7
Not
required
Minimum void ratio of the sample.
No
20
N
Number
w/decimal
precision
up to 7
Not
required
Porosity of the sample.
No
21
specific_
gravity
Number
w/decimal
precision
up to 7
Not
required
Specific gravity of the sample.
No
22
W
Number
w/decimal
precision
up to 7
Not
required
Water content of the sample.
No
23
optw
Number
w/decimal
precision
up to 7
Not
required
Optimum water content.
No
24
S
Number
w/decimal
precision
up to 7
Not
required
Degree of saturation of the sample.
No
25
K
Number
w/decimal
precision
up to 7
Not
required
Hydraulic conductivity of the sample.
No
26
Kunit
Text(15)
If
available.
Unit of measure for K.
Table A-18
27
unitwt
Number
w/decimal
precision
up to 7
Not
required
Unit weight of the sample.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 43
United States
Environmental Protection Agency
-------
Table 3-9 Geology samples (EPAR5GSMP_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
28
satunitwt
Number
w/decimal
precision
up to 7
Not
required
Saturated unit weight of the sample.
No
29
dryunitwt
Number
w/decimal
precision
up to 7
Not
required
Dry unit weight of the sample.
No
30
dry_unit_wt_
max
Number
w/decimal
precision
up to 7
Not
required
Maximum dry unit weight of the sample.
No
31
dry_unit_wt_
min
Number
w/decimal
precision
up to 7
Not
required
Minimum dry unit weight of the sample.
No
32
densityunit
Text(15)
If
available
Unit of measure for the densities of the
sample.
Table A-18
33
reldensity
Number
w/decimal
precision
up to 7
Not
required
Relative density of the sample.
No
34
rel_
compaction
Number
w/decimal
precision
up to 7
Not
required
Relative compaction of the sample.
No
35
Consistency
Text (20)
Not
required
Description of the consistency of the soil
sample such as very soft, soft, firm, hard
or very hard.
No
36
organic_
carbon
Number
w/decimal
precision
up to 7
Not
required
Organic carbon content of sample.
No
37
organic_
carbonunit
Text (15)
If
available
Unit of measurement of organic content.
Use values from Table A-18 of the
Appendix.
No
3.10 Water Levels
The Water Level (EPAR5GWTR_v3) 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 lab
Region 5 EDD Comprehensive Specification Manual
Version 4.2 44
United States
Environmental Protection Agency
-------
Sample (EPAR5SMP_v3) 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.16. Each water level file must be named according to the following convention:
EPAR5GWTR_v3.txt (or .csv)
Table 3-10 Water Level (EPAR5GWTR_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
1
sysloccode
Text(20)
Required
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 EDD file (Table 3-
4) submitted in the current
or previous EDD.
No
2
Measurement
date
DateTime
Required
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).
MM/DD/YYYY
HH:MM:SS
format
3
historical_
referenceelev
Number
w/decimal
precision
up to 15
Required
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).
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 45
United States
Environmental Protection Agency
-------
Table 3-10 Water Level (EPAR5GWTR_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
4
waterlevelde
pth
Number
w/decimal
precision
up to 7
Required
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"
No
5
waterlevelel
ev
Number
w/decimal
precision
up to 7
Not required
Elevation of water level.
Elevation must be in feet.
Feet
6
corrected dept
h
Number
w/decimal
precision
up to 7
Not required
Depth of water level after
any necessary corrections,
e.g., if free product was
encountered.
No
7
correctedelev
Number
w/decimal
precision
up to 7
Not required
Corrected water level
elevation that corresponds
to the corrected depth.
Elevation must be in feet.
feet
8
measureddept
h_
ofwell
Number
w/decimal
precision
up to 7
Not required
The depth below ground
surface to the bottom of the
well.
No
9
depthunit
Text (15)
If available
Unit used for depth
measurements. See Table A-
18 in the Appendix for
appropriate values.
Table A-18
10
Technician
Text (30)
Not required
Name of technician
measuring water level
No
11
dry_indicator_
yn
Text (1)
Not required
This field is used to indicate
whether or not a well is dry
-- "Y" for yes or "N" for no.
Y= yes
N=No
12
measurement
method
Text (20)
Not required
Method used to make water
level measurements.
No
13
batchnumber
Text (10)
Not required
Batch number of group of
measurements.
No
14
diporelevati
on
Text (10)
Not required
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.
Elevation
Dip
15
Remark
Text (255)
Not required
Any necessary remarks
related to groundwater or
surface water information
provided in this EDD file.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 46
United States
Environmental Protection Agency
-------
Table 3-10 Water Level (EPAR5GWTR_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
16
Lnaplcasrn
Text (15)
If applicable
Analyte code of the light
non-aqueous phase liquid
(lnapl) present in the well.
Use appropriate valid value
from Table A-15 in the
EDD Specification Manual
Valid Value Appendix.
Table A-15
17
Lnapldepth
Text
Number
with
precision
of up to 7
Not required
Depth to the top surface of
the lnapl in feet below the
reference elevation.
No
18
Dnaplcasrn
Text (15)
If applicable
Analyte code of the dense
non-aqueous phase liquid
(dnalp) present in the well..
Table A-15
19
Dnapledepth
Number
with
precision
of up to 7
Not required
Depth to the top surface of
the dnapl in feet below the
reference elevation
No
20
Taskcode
Text(40)
Required
Code used to associate
individual samples to a
specific sampling event. The
format for this field is XX-P#,
XX is the type of task
required and P# is the
phase.
No
3.11 Water Table EDD Files
The water table (EPAR5TBL_v3) 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:
EPAR5TBL_v3.txt (or .csv)
Table 3-11 Water table (EPAR5TBL_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
1
sysloccode
Text (20)
Required
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-4) submitted in the
current or previous EDD.
No
2
Type
Text (20)
Required
Aquifer designation, such as unconfinedl,
confinedl, or confined2.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 47
United States
Environmental Protection Agency
-------
Table 3-11 Water table (EPAR5TBL_v3) file data structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
3
Sequence
Text (20)
Required
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.
No
4
Depth
Number
w/decimal
precision
up to 15
Required
Depth of water table, in feet, below
reference point.
Feet
5
flowing_yn
Text (1)
Not
Required
Is the water table flowing? "Y" for yes or
"N" for no.
1/3 O
" £
ii ii
^ £
6
measurement
method
Text (50)
Not required
Method of measuring water table depth.
No
7
capped_pressu
re
Number
w/decimal
precision
up to 15
Not required
Hydrostatic pressure of confined aquifer.
No
8
capped_pressu
re_
unit
Text (15)
If available
Unit of measure for capped pressure. Use
values from Table A-18 in the Appendix.
Table A-18
9
reference_poin
t
Text (50)
Not required
Description of reference point from which
depth measurements were taken.
No
10
referenceelev
ation
Number
w/decimal
precision
up to 15
Required
Elevation of the reference point from
which depth measurement were taken.
Elevation must be in feet.
No
11
Temperature
Number
w/decimal
precision
up to 15
Not required
Temperature of water in the water table.
No
12
temperatureu
nit
Text (15)
If available
Unit of temperature. Use values from
Table A-18 in the Appendix.
Table A-18
3.12 Geology Down Hole Point Data EDD File
The Geology downhole 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.
Report the parameter being measured in the "param" field, such as resistivity, and report the measured
value at the depth of the measurement. Table 3.12a presents the DHP EDD file structure.
Each Geology downhole point data EDD file must be named according to the following convention:
EPAR5DHP_v3.txt (or .csv)
Region 5 EDD Comprehensive Specification Manual
Version 4.2 48
United States
Environmental Protection Agency
-------
Table 3-12 Geology Downhole Point (EPAR5DHP_v3) File Data Structure
Pos#
Column
Name
Data
Type
Required
Description
Valid Values
In Appendix
1
sysloccode
Text(20)
Required
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-4) submitted in
the current or previous EDD.
No
2
Depth
Number
w/decimal
precision
up to 15
Required
Depth of measurement below ground surface
in feet.
No
3
Param
Text(20)
Required
The parameter being measured, such as tip
stress, resistivity, or pore pressure.
No
4
paramvalue
Number
w/decimal
precision
up to 15
Required
The measured value of the parameter.
No
5
Paramunit
Text(15)
Required
Measured unit of the parameter
No
Table 3.12a Example of downhole point data file
Sysloccode
Depth
Param
ParamValue
MW01
10.8
Tip Stress
612
MW01
11.2
Tip Stress
624
MW01
10.8
Sleeve Stress
6.1
MW01
11.2
Sleeve stress
5.8
MW02
9.5
Resistivity
510
MW02
10.1
Resistivity
521
MW02
11.0
Resistivity
889
3.13 Extraction - Injection Well (EPAR5EIW_v3) EDD 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. The purpose
of the EIW EDD file is to provide EPA Region 5 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 an
Extraction-Injection Well file is provided in Figure 2-4, section 2.16. Each Extraction-Injection Well
EDD file must be named according to the following convention:
EPAR5EIW_v3.txt (or .csv)
Region 5 EDD Comprehensive Specification Manual
Version 4.2 49
United States
Environmental Protection Agency
-------
Table 3-13 Extraction-Injection Well (EPAR5EIW_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
1
sysloccode
Text(20)
Required
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-4) submitted in the current
or previous EDD.
No
2
startmeasuredate
DateTime
Required
Date that the pumping rate
measurements began.
MM/DD/YYYY
HH:MM:SS format
3
endmeasuredate
DateTime
Required
Date that the pumping rate
measurements concluded in
MM/DD/YYYY HH:MM:SS format.
MM/DD/YYYY
HH:MM:SS format
4
avg_pump_rate
Number
w/decimal
precision
up to 15
Required
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)
No
5
pumprateunit
Text(15)
Required
Unit of measure for the pumping rate.
Use values from Table A-18 in the
Appendix.
Table A-18
6
pctoperatingtime
Text(3)
Not required
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,
"%").
No
7
operating_
mode
Text(14)
Required
Mode in which well was operating
during the reported interval.
EXTRACTION,
INJECTION,
RECIRCULATION,
PULSE, DEVEL,
UNUSE.
8
designrate
Text(14)
Required
Pumping rate as specified in the
approved remedial design report for
fully capturing site groundwater
contamination.
No
9
designrateunit
Text(14)
Required
Unit of measure for the design pumping
rate. Use values from Table A-18 in the
Appendix.
Table A-18
10
ratemeasurementt
ype
Text(14)
Not required
Type of measurements used for
averaging.
TOTALIZER
(totalizing flow
meter), MANIFOLD
(estimated from total
manifold flow),
ESTIMATE
(estimate from prior
values), AVERAGE
(average of
instantaneous
measurements
11
suction
Text(14)
Not required
Vacuum in well (e.g., wellpoint
vacuum) or well casing (e.g., vacuum
well), reported in equivalent feet of
water.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 50
United States
Environmental Protection Agency
-------
Table 3-13 Extraction-Injection Well (EPAR5EIW_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
12
remark
Text(255)
Not required
Remarks regarding the pumping rate
measurements.
No
3.14 Soil Gas Data EDD File
The soil gas (EPAR5SoilGas_v3) data file contains soil gas survey data.
Each Soil Gas data EDD file must be named according to the following convention:
EPAR5SoilGas_v3.txt (or .csv)
Table 3-14 Soil Gas (EPAR5SoilGas_v3) Survey file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
1
sys loc code
Text(20)
Required
Sample collection location
N/A
2
survey date
Datetime
Required
Sample survay date
N/A
3
Parametercode
Text(20)
Required
Parameter measured by soil gas
survey
N/A
4
Readingdepth
Text(8)
Not required
Depth of soil gas survey
measurement
N/A
5
Reading unit
Text(15)
If available
Parameter measured by soil gas
survey
N/A
6
Reading
Text(8)
Not required
Soil gas survey measurement
N/A
7
Depthunit
Text(15)
If Available
Unit of measure of soil gas survey
measurement
N/A
8
Sampling method
Text(10)
Not required
Sampling method
N/A
9
Instrument type
Text(15)
Not required
Instrument type
N/A
10
East
Text(14)
Not required
Easting coordinate of soil gas
survey measurement
N/A
11
North
Text(14)
Not required
Northing coordinate of soil gas
survey measurement
N/A
12
Secondaryeast
Text(14)
Not required
Secondary easting coordinate of
soil gas survey measurement
N/A
13
Secondary north
Text(14)
Not required
Secondary easting coordinate of
soil gas survey measurement
N/A
14
Lithology code
Text(10)
Not required
Lithology code
N/A
15
Area desc
Text(70)
Not required
Discription of area
N/A
16
Equipment code
Text(60)
Not required
Equipment_code
N/A
17
Boreholedrillmet
hod
Text(10)
Not required
Drilling method
N/A
18
Technician
Text(50)
Not required
Technician
N/A
19
Remark
Text(255)
Not required
remark
N/A
Region 5 EDD Comprehensive Specification Manual
Version 4.2 51
United States
Environmental Protection Agency
-------
4. FORMATS FOR LAB 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 Lab 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 Lab Sample file is provided in Figure 2-4, section
2.16.
Each Lab Sample file must be named according to the following convention:
EPAR5SMP v3.txt (or .csv)
Table 4-1 Lab sample (EPAR5SMP_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
1
Data provider
Text (20)
Required
Date provider company code
A-23
2
syssamplecode
Text(40)
Required
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.
No
3
samplename
Text(50)
Not 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.
No
4
samplematrixcode
Text(3)
Required
Code that identifies the matrix being
sampled, such as soil, groundwater, or
sediment. For acceptable valid values, see
Table A-l in the Appendix.
Table A-l
Region 5 EDD Comprehensive Specification Manual
Version 4.2 52
United States
Environmental Protection Agency
-------
Table 4-1 Lab sample (EPAR5SMP_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
5
sampletypecode
Text(3)
Required
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.
Table A-12
6
samplesource
Text(10)
Required
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.
Field
Lab
7
parentsamplecode
Text(40)
Required for
field
duplicate
samples
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."
No
8
sample_delivery_
group
Text(10)
Not required
EPA and most EPA Reigon 5 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
No
9
sampledate
DateTime
Required
Date sample was collected in
MM/DD/YYYY HH:MM:SS format.
MM/DD/YYYY
HH:MM:SS
format.
10
sysloccode
Text(20)
Required*
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-4)
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
No
11
startdepth
Number
w/decimal
precision
up to 15
Not required
Beginning depth (top) of sample in feet
below ground surface for Soil or
Groundwater sample. Only use for
groundwater samples if discrete samples are
taken at different depth elevations from a
single well, i.e. multiple well packer
samples.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 53
United States
Environmental Protection Agency
-------
Table 4-1 Lab sample (EPAR5SMP_v3) file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
12
enddepth
Number
w/decimal
precision
up to 15
Not required
Ending depth (bottom) of sample in feet
below ground surface for Soil or
Groundwater sample. Only use for
groundwater samples if discrete samples are
taken at different depth elevations from a
single well, i.e. multiple well packer
samples.
No
13
depthunit
Text(15)
If available
Unit of measurement for the sample
beginning and end depths. For valid values,
see Table A-18 in the Appendix.
Table A-18
14
chainofcustody
Text(15)
Not required
Chain of custody identifier. A single sample
may be assigned to only one chain of
custody.
No
15
senttolabdate
DateTime
Not required
Date sample was sent to lab in
MM/DD/YYYY format.
No
16
samplereceiptdate
DateTime
Not required
Date that sample was received at laboratory
in MM/DD/YYYY format.
No
17
sampler
Text(30)
Not required
Name or initials of sampler.
No
18
samplingcompanyc
ode
Text(10)
Required
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.)
No
19
sampling reason
Text(30)
Not required
Reason for Sampling
No
20
sampling technique
Text(40)
If available
Sampling technique.
No
21
taskcode
Text(40)
Required
Code used to associate individual samples
to a specific sampling event. The format for
this field is XX-P#, XX is the type of task
required and P# is the phase.
No
22
collection quarter
Text(5)
Not required
Report as null.
No
23
composite_yn
Text(l)
Required
Is sample a composite sample? Enter "Y"
for yes or "N" for no.
Y= Yes
N=No
24
compositedesc
Text(255)
Not required
Description of composite sample. If sample
is not a composite, leave this field null.
No
25
sampleclass
Text(10)
Not required
Report as null.
No
26
custom field 1
Text (20)
Not required
Report as null.
No
27
custom_field_2
Text(50)
Not required
Report as null.
No
28
custom field 3
Text(50)
Not required
Report as null.
No
29
comment
Text(255)
Not required
Any comments regarding the sample.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 54
United States
Environmental Protection Agency
-------
4.2 Lab Test Results EDD Files
The Lab Test Results EDD files contain data relating data concerning analytical tests and results
performed on samples.
Each Lab Test Results EDD file must be named according to the following convention:
EPAR5TRS v3.txt (or .csv)
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
1
syssamplecode
Text(40)
Required
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
EPAR5SMP_v3 file submitted in the
current or previous EDD.
No
2
lab_anl_method_
name
Text(20)
Required
Laboratory analytical method name or
description. For acceptable valid values,
see Table A-16 in the Appendix. Default
to "Unknown" if data is unavailable.
Table A-16
3
analysisdate
DateTim
e
Required
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
No
4
totalordissolved
Text(l)
Required
Must be either "D" for dissolved or
filtered [metal] concentrations, and "T"
for every other case.
A-24
5
columnnumber
Text(2)
Not required
Report as null.
No
6
test type
Text(lO)
Required
Type of test
A-25
7
labmatrixcode
Text(3)
If available
Code that identifies the matrix, such as
soil, groundwater, and sediment, being
sampled... 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.
Table A-l
8
analysislocation
Text(2)
Required
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.
FI = Field
Instrument
FL = Mobile
Field lab
LB = Fixed
based lab
Region 5 EDD Comprehensive Specification Manual
Version 4.2 55
United States
Environmental Protection Agency
-------
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
9
Basis
Text(10)
Required
Must be "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.
Wet= wet-weight
Dry= dry weight
N/A = not
applicable
10
container id
Text(30)
Not required
Report as null.
No
11
dilution factor
Number
Not required
Effective test dilution factor.
No
w/decim
al
precision
up to 7
12
prepmethod
Text(20)
If available
Laboratory sample preparation method
name or description. Must use valid value
from Table A-14 in the Appendix.
Table A-14
13
prepdate
DateTim
e
Not required
Beginning date of sample preparation
MM/DD/YYYY
HH:MM:SS
format
14
leachatemethod
Text(15)
Not required
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).
No
15
leachatedate
DateTim
e
Not required
Beginning date of leachate preparation
MM/DD/YYYY
HH:MM:SS
format
16
labnamecode
Text(20)
If available
Unique identifier of the laboratory as
defined by the EPA. Controlled
vocabulary..
[Note: If the lab you are using does not
appear in Table A-17, you may propose a
valid value for the lab for addition to the
EPA Region 5 list. Please provide
information about the lab in the cover
letter accompanying your EDD
submittal.]
Table A-17
17
qclevel
Text(10)
Not required
Not limit to "Screen" or "Quant", visit
Appendix B in the
https://semspub.epa. aov/work/HO/17
6101 .pdf for more values
No
18
labsampleid
Text(20)
Not required
Laboratory LIMS sample identifier. If
necessary, a field sample may have more
than one LIMS lab sample id (maximum
one per each test event).
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 56
United States
Environmental Protection Agency
-------
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
19
percentmoisture
Text(5)
Not required
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%."
No
20
subsample_
amount
Text(14)
Not required
Amount of sample used for test.
No
21
subsample_
amountunit
Text(15)
If available
Unit of measurement for subsample
amount. Must use valid value from Table
A-18 in the Appendix.
Table A-18
22
analyst name
Text(30)
Not required
Report as null.
No
23
instrument id
Text(50)
Not required
Report as null.
No
24
comment
Text(255
)
Not required
Comments about the test as necessary.
No
25
preservative
Text(20)
If available
Sample preservative used.
No
26
finalvolume
Numeric
Not required
The final volume of the sample after
sample preparation. Include all dilution
factors.
No
27
finalvolumeunit
Text(15)
If available
The unit of measure that corresponds to
the final amount.
No
28
cas rn
Text(15)
Required
Analyte code..
Table A-15
29
chemical name
Text(75)
Required
Chemical name..
Table A-15
30
resultvalue
Numeric
Not required
Analytical result reported at an
appropriate number of significant digits.
No
31
resulterrordelta
Text(20)
Not required
Error range applicable to the result value;
typically used only for radiochemistry
results.
No
32
resulttypecode
Text(3)
Required
Must be either "TRG" for a target or
regular result, "TIC" for a tentatively
identified compound. Use "TRG" for
measurements taken from the field (e.g.,
pH, dissolved oxygen)
TRG = Target or
regular
TIC = Tentative
identified
33
reportableresult
Text(10)
Required
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
(only one result should be flagged as
reportable).
Yes
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 57
United States
Environmental Protection Agency
-------
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
34
detectflag
Text(2)
Required
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.
Y = detected
N = non-detects
35
lab qualifiers
Text(10)
Not required
Qualifier flags assigned by the laboratory.
No
36
validatorqualifiers
Text(10)
Not required
Qualifier flags assigned by the person
who validates the laboratory data. The
interpret qualifier is required if
lapqualifer or validator qualifier are
populated
No
37
Interpretedqualifier
Text(20)
If available/
Required
Interpreted qualifier flag assigned by the
data provider. The interpret qualifier is
required if lap qualifer or validator
qualifier are populated
Table A-10
38
Validated yn
Text (1)
Required
Indicates if the result has been validated
39
organicyn
Text(l)
Required
Must be either" Y" for organic
constituents or "N" for inorganic
constituents. Use "Y" for measurements
taken from the field (e.g., pH, dissolved
oxygen)
Y= organic
N= inorganic
40
method_detection_
limit
Text(20)
Not required
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.
No
41
reporting_detection_
limit
Numeric
Not required
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.
No
42
quantitationlimit
Text(20)
Not required
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.
No
43
resultunit
Text(15)
If available
Units of measurement for the result. Must
use valid values from Table A-18 in the
Appendix.
Table A-18
Region 5 EDD Comprehensive Specification Manual
Version 4.2 58
United States
Environmental Protection Agency
-------
Table 4-2 Lab Test Results (EPAR5TRS_v3) EDD file data structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
44
detectionlimitunit
Text(15)
If available
Units of measurement for the detection
limit(s). Must use valid value from
Table A-18 in the Appendix.
Table A-18
45
tic retention time
Text(8)
Not required
Report as null.
No
46
resultcomment
Text(255
)
Not required
Result specific comments.
No
4.3 Lab Test/Result with QC Data EDD File
The Lab 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 5 EDD Comprehensive Specification Manual
Version 4.2 59
United States
Environmental Protection Agency
-------
EPAR5TRSQC_v3.txt (or .csv)
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
1
syssamplecode
Text(
40)
Required
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
EPAR5SMP_v3 file submitted in the
current or previous EDD.
2
labanl _method_
name
Text(
20)
Required
Laboratory analytical method name or
description. For acceptable valid
values. Default to "Unknown" if data
is unavailable.
Table A-16
3
analysisdate
DateT
ime
Required
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
4
T otalordissolved
Text(
1)
Required
Enumeration list contains the values
A-24
5
columnnumber
Text(
2)
Not required
Column number, if null, "NA" will be
placed in this field
No
6
testtype
Text(
10)
Required
Type of test.
A-25
7
labmatrixcode
Text(
3)
If available
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.
Table A-l
8
analysislocation
Text(
2)
Required
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.
FI = Field
Instrument
FL = Mobile
Field lab
LB = Fixed
based lab
9
Basis
Text(
10)
Required
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.
Wet= wet-
weight
Dry= dry
weight
N/A = not
applicable
10
containerid
Text(
30)
Not required
Report as null.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 60
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
11
dilutionfactor
Nume
ric
Not required
Effective test dilution factor.
No
12
prepmethod
Text(
20)
If available
Laboratory sample preparation method
name or description. Must use valid
value from Table A-14 in the
Appendix.
Table A-14
13
prepdate
DateT
ime
Not required
Beginning date of sample preparation.
MM/DD/YY
YY
HH:MM:SS
format
14
leachatemethod
Text(
15)
Not required
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).
No
15
leachatedate
DateT
ime
Not required
Beginning date of leachate preparation
MM/DD/YY
YY
HH:MM:SS
format
16
labnamecode
Text(
20)
If available
Unique identifier of the laboratory as
defined by the EPA. Controlled
vocabulary; see the lab valid value
table in appendix.
Table A-17
17
qclevel
Text(
10)
Not required
Not limit to "Screen" or "Quant",
visit Appendix B in the
httDs://semsDub.eDa.eov/work/H
O/176101.Ddf for more values
No
18
labsampleid
Text(
20)
Not required
Laboratory LIMS sample identifier. If
necessary, a field sample may have
more than one LIMS lab sample id
(maximum one per each test event).
No
19
percent moisture
Text(
5)
Not required
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%."
No
20
subsampleamount
Text(
14)
Not required
Amount of sample used for test.
No
21
subsample_amount_
unit
Text(
15)
If available
Unit of measurement for subsample
amount. Must use valid value from
Table A-18 in the Appendix.
Table A-18
22
analystname
Text(
30)
Not required
Report as null.
No
23
instrumentid
Text(
50)
Not required
Report as null.
No
24
Comment
Text(
255)
Not required
Comments about the test, if necessary.
No
25
Preservative
Text(
20)
If available
Sample preservative used.
Table A-27
Region 5 EDD Comprehensive Specification Manual
Version 4.2 61
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
26
finalvolume
Nume
ric
Not required
The final volume of the sample after
sample preparation. Include all dilution
factors.
No
27
finalvolumcunit
Text(
15)
If available
The unit of measure that corresponds to
the final amount.
Table A-18
28
casrn
Text(
15)
Required
Analyte code..
Table A-15
29
chemicalname
Text(
75)
Required
Chemical name.
Table A-15
30
Resultvalue
Nume
ric
Not required
Analytical result reported at an
appropriate number of significant
digits. May be blank for non-detect
results.
No
31
Resulterrordelta
Text(
20)
If available
Error range applicable to the result
value; typically used only for
radiochemistry results.
No
32
Resulttypecode
Text(
10)
Required
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).
'CAL' for calculated pore water
concentrations.
Table A-11
33
reportableresult
Text(
10)
Required
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.
Yes
No
Y
N
34
detectflag
Text(
2)
Required
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.
Y= detected
N = non-
detects
35
Labqualifiers
Text(
10)
Not required
Qualifier flags assigned by the
laboratory.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 62
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
36
validatorqualifiers
Text(
10)
Not required
Qualifier flags assigned by the person
who validates the laboratory data.
No
37
Interpretedqualifier
s
Text(
10)
If available
Interpreted qualifier flag assigned by
the validator. When the validated_yn =
N (no, meaning the data is not validated
by validator), the interpret qualifier is
required if labqualifier or validator
qualifier are populated. If the
validated_yn = Y (yes, meaning the
data has been validated and the
validator agreed witht eh lab qualifier),
then they should populate the
validator qualifier and the
interpreted qualifier. If the
validated_yn = Y (yes, but the validator
does not agree with the lab qualifier),
then the validator will leave the
qualifier NULL and the final qualifier
is also NULL. When populating th e
interpreted qualifier, please use the
qualifier in the Valid Value in A-10
with the description that can closely
match with the lab qualifier.
A-10
38
Validated_yn
Text
(1)
Required
Must be either" Y" for validate or "N"
for not validate.
Indicated if
the result has
been
validated
39
Organic_yn
Text(
1)
Required
Must be either Y' for organic
constituents or 'N' for inorganic
constituents.
No
40
methoddetectionli
mit
Text(
20)
If available
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.
No
41
reporting_detection_
limit
Nume
ric
Not required
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.
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 63
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
42
quantitationlimit
Text(
20)
Not required
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.
No
43
Resultunit
Text(
15)
If available
Units of measurement for the result.
Must use valid values from Table A-18
in the Appendix.
Table A-18
44
detection_limit_
unit
Text(
15)
If available
Units of measurement for the detection
limit(s). Must use valid value from
Table A-18 in the Appendix.
Table A-18
45
ticretentiontime
Text(
8)
Not required
Report the value and time when the
result type is TIC.
No
46
Resultcomment
Text
(255)
Not required
Result specific comments
No
47
qcoriginalconc
Nume
ric
Not required
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).
No
48
qcspikeadded
Nume
ric
Not required
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).
No
49
qcspikemeasured
Nume
ric
Not required
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).
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 64
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
50
qcspikerecovery
Nume
ric
Not required
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").
No
51
qc_dup_original_
cone
Nume
ric
Not required
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).
No
52
qc_dup_spike_
added
Nume
ric
Not required
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.
No
53
qc_dup_spike_
measured
Nume
ric
Not required
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.
No
54
qc_dup_spike_
recovery
Nume
ric
Not required
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").
No
55
qcrpd
Text(
8)
Not required
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").
No
Region 5 EDD Comprehensive Specification Manual
Version 4.2 65
United States
Environmental Protection Agency
-------
Table 4-3 Chemistry test/results with QC (EPAR5TRSQC_v3) data file structure
Pos#
Column Name
Data
Type
Required
Description
Valid Values
In Appendix
56
qcspikelcl
Text(
8)
Not required
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").
No
57
qcspikeucl
Text(
8)
Not required
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").
No
58
qcrpdcl
Text(
8)
Not required
Relative percent difference control
limit. Required for any duplicated
sample. Report as percentage
multiplied by 100 (e.g., report "25%" as
"25").
No
59
qcspikestatus
Text(
10)
Not required
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.
No
60
qc_dup_spike_
status
Text(
10)
Not required
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.
No
61
qcrpdstatus
Text(
10)
Not required
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.
No
4.4 Lab Batch Data (EPAR5BAT v3) EDD File
The Lab Batch (EPAR5BAT_v3) 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 test type fields match those found in the TestResultQC EDD files. Each
Chemistry batch file must be named according to the following convention:
EPAR5BAT_v3.txt (or .csv)
Table 4-4 Lab batch file (EPAR5BAT_v3) data structure
Region 5 EDD Comprehensive Specification Manual
Version 4.2 66
United States
Environmental Protection Agency
-------
Pos#
Column Name
Data type
Required
Description
Valid Values
In Appendix
1
syssamplecode
Text(40)
Required
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
EPAR5 SMP_v3 file (Table 4-1)
submitted in the current or previous EDD.
No
2
lab_anl_method_
name
Text(20)
Required
Laboratory analytical method name or
description. For acceptable valid values,
see Table A-16 in the Appendix. Default
to "Unknown" if data is unavailable.
Table A-16
3
analysisdate
Datetime
Required
Date of sample analysis. May refer to
either beginning or end of the analysis.
MM/DD/YYYY
HH:MM:SS
format.
4
totalordissolved
Text(l)
Required
Enumeration list contains the values
A-24
5
columnnumber
Text(2)
Not
required
Report as null.
No
6
testtype
Text(lO)
Required
Type of test.
A-25
7
testbatchtype
Text(lO)
Required
Lab batch type.
This is a required field for all batches.
A-26
8
test batch id
Text(20)
Required
Unique identifier for all lab batches.
No
5. TECHNICAL SUPPORT
EPA Region 5 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 5 EDD Comprehensive Specification Manual
Version 4.2 67
United States
Environmental Protection Agency
------- |