Electronic Data Deliverable (EDD)
Basic
Manual for Historic Electronic Data
EPA Region 2
Prepared By:
Region 2 Superfund Division
Environmental Protection Agency
May 2019
EDD version 4

-------
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.

-------
TABLE OF CONTENTS
1.0 INTRODUCTION	1
2.0 GENERAL EDD REPORTING REQUIREMENTS	2
2.1	File Formats	2
2.2	EDD Files	3
2.3	File Naming Convention	5
2.4	Data Integrity Rules	6
2.5	Reporting Null Values	7
2.6	Valid Values	8
2.7	Reporting Non-Detects	9
2.8	Reporting Re-Tests	10
2.9	Reporting Tentatively Identified Compounds	10
2.10	Using the Electronic Data Processor to Check EDD Formatting	11
2.11	Submitting Your EDD to EPA	11
3.0 EDD FILE FORMATS	12
3.2Site EDD File	14
3.3	Location EDD File	16
3.4	Chemistry Sample Result EDD File	19
3.5	Water Level EDD File	27
3.6	Geology EDD File - Optional	29
3.7	Extraction ¦ Injection Well EDD File	30

-------
INTRODUCTION
The Basic Manual for Electronic Data describes the requirements for electronically submitting
"historical" operation and maintenance (O&M) data to EPA Region 2. O&M data is considered
to be "historical" if it was collected between the time remedy construction was completed up to
and including the most recent data collection event. The data provider should anticipate all
future data being collected for a site to be submitted on a regular basis (at least annually or semi-
annually) in accordance with this manual. The data provider is also encouraged to become
familiar with and submit EDDs in accordance with the standard EPA Region 2 Comprehensive
Specification Manual for Electronic Data. EPA Region 2 anticipates requiring all data providers
to submit EDDs in accordance with the standard EPA Region 2 Comprehensive Specification
Manual for Electronic Data.
The intent of developing special requirements for historical information is to decrease the burden
associated with reporting in-depth details about data that may have been collected a number of
years ago. 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.
This information is also available on the Region2 Superfund EDD Website located at:
https://www.epa.gov/superfiind/region-2-superfund-electronic-data-submission
Excited News: EPA Region 2 EQuIS database has been upgraded to version 7, please check out the "EPA
Region 2 EQuIS 6 EDD format version 4 Changes release notes.pdf' to get the summary of all new
changes in the EDD format. Detail of changes can be found in this document and they will be highlighted in
Blue.
Basic Manual for Historic Electronic Data
Version6
l
US EPA Region 2
May 2019

-------
2.0 GENERAL EDD REPORTING REQUIREMENTS
2.1 File Formats
All EDD data from EPA Region 2 data providers must be reported as text 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-1 provides
instructions for creating tab-delimited text files from some widely-used software packages.
Table 2-1 Instructions for Producing Tab-Delimited Text Files
Package
Type
Instructions
Access
Database
Create tables using file structures in Section 3.
After data are entered, close table.
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.
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
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
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?]
Enter data into a table in Word. Any text entered must be
contained within double quotes.
Select "Table," "Select Table," from the top menu.
When the table is highlighted, select "Table," "Convert
to Text," "Separate Text with Tabs."
Select "File," "Save As," from the top menu. Change
"Save as Type" to "MS DOS Text (*.txt).
Lotus 1-2-3
Spreadsheet
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.
Basic Manual for Historic Electronic Data
Version6
2
US EPA Region 2
May 2019

-------
A Microsoft Excel Workbook file, EPAR2BasicEDD.xls, provides electronic templates for EDD
files. To create an EDD, simply enter your data into the worksheets provided and then follow the
instructions in Table 2-1 to create a tab-delimited text file.
A Microsoft Access database file, EPAR2BasicEDD.mdb, also provides electronic templates for
EDD files. To create an EDD, simply enter your data into the database files provided and then
follow the instructions in Table 2-1 to create a tab-delimited text file.
2.2 EDD Files
The tables in this guidance identify the various types of data being requested. Each EDD file
should be saved as an individual text file and should be named in accordance with the naming
convention rules. Table 2-2 provides general information on the files that make up this EDD.
Detailed instructions for creating all the EDD files are provided in Section 3. Instructions for
submitting your EDDs to EPA Region 2 are presented in Section 2.11
Table 2.2 General Information on EDD Files
File Type
File Name
Created
By
Contents
What makes a
row of data
unique?
Dependence of
other files on
these data
Base Map or
any cover
letter or PDF
file of the
Base Map,
any image
files
SiteName.dxf,
drawing (.dwg)
or ArcGIS
shapefiles.
Document or
cover letter in
PDF, or doc
format.
Data
provider
Basemap or cover
letters about the
EDD.
Not applicable
Not applicable.
Data
Provider
SiteNameDate.
EPAID.
DataProviderv
4.txt (or csv)
Data
Provider
Information about
the data provider
DataProviderco
de
Not applicable
Site
(Section 3.2)
SiteNameDate.
EPAID.
Site_v4.
Txt (or csv)
Data
provider
One-time definition
of site including EPA
Region 2 data
providers' contact
information.
Sitecode
The location file
cannot be loaded
without properly
referenced sites
(sitecode).
Location
(Section 3.3)
SiteNameDate.E
PAIDCode.
BasicLocationv
4.txt (or .csv).
Data
provider's
surveyor
One entry for each
location on a site.
Contains elevation,
coordinate and
general locational
data. Data should
only be reported once
for a location.
Sysloccode
Sample Results,
water levels, field
measurements,
geology and
extraction well
data can only be
reported for
locations that are
defined in this
file.
Basic Manual for Historic Electronic Data
Version6
3
US EPA Region 2
May 2019

-------
Table 2.2 General Information on EDD Files
File Type
File Name
Created
By
Contents
What makes a
row of data
unique?
Dependence of
other files on
these data
Chemistry
Sample
Result
(Section 3.4)
SiteNameDate.
EPAID.
BasicChemistry
v4.
Txt (or csv)
Data
provider's
field
sampling
team(s)
and
testing
lab(s)
One row for each
analyte reported for a
given sample and
test. Additional rows
can be added to
report total and
dissolved results and
to report results for
re-extracts.
Syssamplecode
lab_anl_method_
name
analysisdate
totalordissolved
testtype
casrn
None
Water Level
(Section 3.5)
SiteNameDate.E
PAIDCode.
BasicWaterLev
el_v4.txt (or
.csv).
Data
provider's
field
sampling
team(s)
Groundwater level
data for monitoring
wells
sysloccode
measurementdate
measurementtime
None.
Geology
(Optional)
(Section 3.6)
SiteNameDate.E
PAIDCode.
BasicGeololgyv
4.txt (or .csv).
Data
provider's
geologist
Geology data for a
borehole.
Sysloccode
startdepth
None.
Extraction-
Injection
Well
(Section 3.7)
SiteNameDate.
EPAIDCode.
Extractionlnjecti
onWells_v4.
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.
Sysloccode
startmeasurement
date
startmeasurement
time
None.
Basic Manual for Historic Electronic Data
Version6
4
US EPA Region 2
May 2019

-------
2.3 File Naming Convention
-Sign and Submit
After using the tools outlined above to resolve all of the issues in a set of Data Files the data is ready to be
submitted for loading into the EquIS 5 database. The Sign and Submit tool was designed to facilitate
submittal of data to EquIS Enterprise EDP. Sign and Submit option packages the data files with the correct
naming convention which allows easy submittal of data packages. Use of the Sign and Submit feature
requires a user name and password that can be created by EQuIS EDP user or obtained from the EPA
Region 2 MEDD Database Administrator.
To use the Sign and Submit feature, after data files have been loaded and all of the errors have been
resolved,
1. Select Sign and Submit from the Application Menu. This will open the Sign and Submit window.
Sign and Submit	X
User Name:	i
Password'	j
EPA ID,:	¦•¦]
Registry ID;	|
[~1 Save Password	Save
Figure 13: Sign and Submit Window
Enter your User Name and Password as well as the EPA ID that applies to the data package being
submitted. The Registry ID will be automatically populated based on the selected EPA ID. If the EPA ID
does not exist, users can enter the EPA ID and Registry ID manually. Rigister ID and EPA ID can be
obtained from EPA Region 2 MEDD database administrator. For this exercise use your name as the User
Name and Password, and 'NYO123456' for the EPA ID. This information will be used to create a user
certificate file that EQuIS Enterprise uses to ensure a valid user is submitting data for the appropriate
Program. NOTE: The EPA ID and Registry ID are extremely important for Enterprise Data Submittals;
however, the data entered into these sections of the Sign and Submit screen may be modified by the user as
needed.
3.	Click the Save button.
4.	Users will be prompted to provide a filename and location where you would like to save the file. The
Sign and Submit feature will save an archived ("zipped") file named with the current date, a period, the
EPA ID, a period, a period and the Format File name used to create the EDDs. (Example file name:
'20080424. NY0123456.EPAR2.zip'). The contents of the Zipped file include text files named for the
Basic Manual for Historic Electronic Data
Version6
5
US EPA Region 2
May 2019

-------
sections of the format used to create them.
5. Select Save. Once the zipped EDD Package has been saved the following screen will appear.
Figure 14: Sign and Submit Verification Window
6. Select OK
After the zipped file has been created the EDD Package is ready to be submitted to your regulator for
loading into EQuIS Professional EDP or EQuIS Enterprise EDP.
Each EDD file, except the base map file, should be named according to the following
convention:
SiteNameDate.EPA I DCode.£'/,/l/?2E DDFileType_v2.txt (or .csv)
Italicized text in the above example is the actual text that appear in the file names. The non-
italicized text indicates what information should be provided at that position in the EDD file
name. Specifically, the short version of the site name would be used in place of siteName,
followed by (with no intervening spaces) the date the EDD is submitted. The date should be in
the following format: YYYYMMDD. The next part of the file name, EPAIDCode,* refers to the
EPA ID number designated by EPA for the site. The next part of the EDD file name refers to the
type of EDD file being submitted, e.g., SITE_v4, BasicLocation_v4, etc. Please note that the
number after the "_v" is for internal EPA use only and serves to indicate the version of the
EPA Comprehensive Manual for Electronic Data on which the EDD format is based. For the
foreseeable future, all EDD files submitted to EPA Region 2 should have "v4" as the suffix.
[Note: Using capitals versus lowercase letters in the file names makes no difference. The choice
is yours.]
As an example, sample and result data for the ABC site (EPA identification number of
XYZ123456789) that is being submitted to EPA on March 19, 2018 would be reported in a file
named 20180319.XYZ123456789.BasicChemistry_v4.txt (or .csv).
2.4 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
Basic Manual for Historic Electronic Data
Version6
6
US EPA Region 2
May 2019

-------
provided in the description columns of the tables in Section 3 or in the tables in the Valid Value
Appendix of this manual. For example, sample matrix information is inputted in the
samplematrixcode field of the Sample Result file and must be reported using one of the values
provided in Table A-l in the Valid Value Appendix.
Row Uniqueness. Row uniqueness must be verified using the guidance provided in Table 2-2.
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, the sys loc code is the primary key in the Location EDD file
and therefore no two rows in the can have the same sys loc code.
Row Integrity . The relationship between rows within the files of the EDD must be assured by
enforcing the "referential integrity" rules discussed in Table 2-2 under the column labeled
"Dependence of other files on these data." For example, the values in the sys loc code field in
the Sample Result file must match with a value previously reported in the sys loc code field of
the Location file.
2.5 Reporting Null Values
When a field is not listed as required in Section 3 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-3 shows a number of examples.
	Table 2-3. 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.
"dataone" "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.
Basic Manual for Historic Electronic Data
Version6
7
US EPA Region 2
May 2019

-------
2.6 Valid Values
Valid values, also known as reference values or code lists, govern the contents of some fields in
the EDD files. In other words, some fields may only be populated with data that matches a value
listed in the EPA Region 2 list of valid values in Valid Value Appendix of this Manual. A list
of all the data fields that must contain valid values is presented in Table 2-4. This list is also
cross-referenced to the EDD file(s) the field appears in. If data providers need to enter a value
not already in the Region 2 list in Valid Value Appendix, they can request the proposed addition
to the valid value list in the EDD submittal 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 laboratory 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.
Basic Manual for Historic Electronic Data
Version6
8
US EPA Region 2
May 2019

-------
Table 2-4. 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
Sample Result
Location Type
A-9
locjype
Location
Qualifier
A-10
labqualifiers, validator qualifiers
Chemistry
Sample Result
Result Type
A-l 1
resulttypecode
Chemistry
Sample Result
Sample Type
A-12
sampletypecode
Chemistry
Sample Result
Analyte
A-l 5
cas rn, chemicalname, dnaplcasrn,
lnaplcasrn
Chemistry
Sample Result
Water Level
Lab Analysis Method
Name
A-16
labanlmethodname
Chemistry
Sample Result
Unit
A-l 8
various unit fields throughout all files
All Files
Geology Soil
Materials
A-19
materialtype
Geology
EPA Facility IDs
A-22
facility id, site_name, city
Site
Company Codes
A-23
Data_provider_code, data_provider
Location, Sample,
Test Result, Data
Provider
Fraction (Total or
dissolved)
A-24
T otalordi s sol ved
Test Result, Test
Result QC, Batch
Test Type
A-25
Test_type
Test Result, Test
Result QC, Batch
Test Batch Type
A-26
Testbatchtype
Batch
2.7 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 and must have values entered in the reportingdetectionlimit
and detectionlimitunit fields (i.e., these fields cannot be left null if record is a non-detect).
Table 2.5 presents an examples how to report a detect (1st row) and non-detect (2nd row) data.
Table 2-5. Example of reporting non-detects
Cas rn
Result
Detect
Reporting
Detection
Result comment
Laboratory

Basic Manual for Historic Electronic Data
Version6

9

US EPA Region 2
May 2019

-------

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.8 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
reportableresult field. The initial test, and any retest result not considered reportable will have
reportableresult set to "No". Table 2.6 provides examples of reporting re-tests.
Table 2-6. Example of reporting re-tests
Test
Type
Chem
Name
Cas rn
Result
Value
Detect
Flag
Lab
Qualifiers
Reportable
Result
ResultComment
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.9 Reporting Tentatively Identified Compounds
Tentatively Identified Compounds (TICs) should be reported when available. The naming of
TICs should be applied in a cascade fashion. The TIC should be identified to analyte name if
possible. If this is not possible, then the class of the TIC should be entered.. If neither an analyte
name or a class can be identified, the TIC should be identified as Unknown. The EPA Region 2
EDD only allows for reporting up to 10 TICs. Only the 10 most concentrated or most relevant
TICs should be reported. Table 2-7 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
casrn field, Pos #23, of the Chemistry Sample Result file (Section 3.4). In addition, the
result type code, Pos # 26 in the Chemistry Sample Result file should have "TIC" for all TIC
records.
Table 2-7. 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
Basic Manual for Historic Electronic Data
Version6
10
US EPA Region 2
May 2019

-------
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.10	Using the Electronic Data Processor to Check EDD Formatting
All EDD files must be ran through the Electronic Data Processor (EDP) prior to submittal to
EPA Region 2. The EDP is used by Data Providers to check EDD files prior to submittal to EPA
Region 2. The EDP is a no-cost application that performs a series of formatting checks on the
files and then identifies any records that have errors along with a description of those errors.
This allows the Data Provider to correct the errors before sending the files to EPA Region 2.
EDD files that pass through the EDP error-free should also result in error-free import at EPA
Region 2.
EDP is currently available as a no-cost download from the EPA Region 2 E-Data website located
at https://www.epa.gov/superfund/region-2-superfund-electronic-data-submission
Instructions on how to install and use the EDP are also provided on the website.
2.11	Submitting Your EDD to EPA
It is preferred to submit by e-mail, e-mail submittals may be provided with cc: Remedial Project
Manager (RPM). Each EDD must be accompanied by a cover letter that specifies the name of the
site, the contact for any EDD technical questions regarding file names, any exceptions to the EDD
format, any requests for additional valid values, etc. Larger files should be zipped and renamed e.g.
*.piz.
All electronic submittals should be sent to: Reqion2 EQUISedd@epa.qov and cc:ed RPM
If you cannot submit files electronically, contact the EDD coordinator.
In the case where Region 2 encounters errors with the submitted EDD files, the entire EDD
submittal will be returned to the data provider along with an error report explaining the errors.
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 as those in the original
submittal (i.e., use the same site name and submittal date in the file name as was used in the
original submittal). Thus, the EDD resubmittal will be identical to the original submittal in every
way except the errors are corrected.
Basic Manual for Historic Electronic Data
Version6
li
US EPA Region 2
May 2019

-------
3.0 EDD FILE FORMATS
This section contains detailed information regarding the files that make up the Region 2 EDD. As stated in section 2.1, each file must
be saved as individual text files and can be created using any software with the capability to create text files. If a column is limited to
a specific number of characters, the limit will be given in parenthesis within the "Data Type" column (e.g., Text (3) signifies the value
cannot exceed 3 characters in length). 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.
The Site and Location files need to be submitted as part of the first EDD submittal. These 2 files only need to be submitted once
unless information in the files change or additional information, such a new sampling location, needs to be added.
Examples of populated EDD files are provided in Attachment 1.
3.1. Data Provider
The Data Provider EDD file provides general information about the data provider who is the contact for the data on the site.
SiteNameDate.EPAIDCode.DataProvider_v4.txt (or .csv)
Basic Manual for Electronic Data
Version 6
12
USEPA Region 2
May 2019

-------
Table 3.1 Data Provider File Structure
Pos#
Column
Name
Data Type
Required
Description
Valid Values
In Appendix
1
DataProvider
code
Text (20)
Required
Data provider company code
A-23
2
DataProvider
Text (70)
Required
This is the name of the company who is responsible for providing the
site data.
A-23
3
Data contact
Name
Text (50)
Required
This is the name of the contact person who is responsible for providing
the site data.
No
4
Data_Contact_
Addressl
Text (40)
Required
Contact Address
No
5
DataContact
_Address2
Text (40)
If available
Contact Address
No
6
DataContact
City
Text (30)
Required
Contact City
No
7
DataContact
State
Text (10)
Required
Contact state
No
8
DataContact
zip code
Text (30)
Required
Contact zip
No
9
DataContact
Country
Text (50)
If available
Contact country
No
10
DataContact
phone
Text (20)
Required
Contact phone number
No
11
Data Contact
Text (100)
Required
Contact email address
No
email









Basic Manual for Electronic Data
Version 6
13
USEPA Region 2
May 2019

-------
3.2 Site EDD File
The Site EDD file is typically a one-time-only submittal and must be submitted as part of the first EDD submittal. This file contains
general information about the site, along with information such as the name, address, and phone number of the main contact
responsible for data submittal. If the Site EDD file has already been submitted for the site, and none of the information in the file has
changed, you do not have to resubmit the file. The only time this file is resubmitted is when information about the contact person or
other information in the file changes.
For historical data, the Site EDD file, and all the requirements related to it, are exactly the same as are described for the Site EDD file
in the EPA Region 2 Comprehensive EDD Specification Manual for non-historical data.
Site EDD files should be named according to the following convention:
SiteNameDate.EPAIDCode.Site_v4.txt (or .csv).
Basic Manual for Electronic Data
Version 6
14
USEPA Region 2
May 2019

-------
Table 3-2. SITE data file structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
1
site code
Text (3)
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
ProgramCode
Text (20)
If available
This is equivalent to the EPA CERCLIS ID number, or
SRPID or other state program code
Table A-22
3
site name
Text (60)
Required
Name of site
Table A-22
4
sitetaskcode
Text (20)
If available
Code used to identify the task under which the site or area is
investigated. This field is for informational purposes only.
Field samples are formally associated with task codes.
No
5
site descl
Text (255)
If available
General description of the site.
No
6
site desc2
Text (255)
If available
Additional description of site, if necessary.
No
7
contact name
Text (50)
Required
Name of person to contact if EPA Region 2 has any
questions about the EDD.
No
8
addressl
Text (40)
Required
Site address, part one.
No
9
address2
Text (40)
If available
Site address, part two. Default to null if information is not
needed
No
10
City
Text (30)
Required
Site city.
No
11
State
Text (2)
Required
Site state.
No
12
Zipcode
Text (10)
Required
Site zip code.
No
13
phone number
Text (30)
Required
Site contact phone number.
No
14
alt_phone_number
Text (30)
If available
Alternate phone number for site contact. Default to null
where the data are not available.
No
15
faxnumber
Text (30)
If available
Fax number of site contact. Default to null where the data is
not available.
No
16
emailaddress
Text (100)
Required
Site contact e-mail address.
No
Basic Manual for Electronic Data
Version 6
15
USEPA Region 2
May 2019

-------
3.3 Location EDD File
The Location file is another EDD file that is typically submitted only once and must be part of the first EDD submittal. The location
file only needs to be resubmitted if a new sampling location is used, such as a new monitoring well, or to update previously submitted
information. When resubmitting the location file, only include data for the new locations and/or for the locations whose information is
being updated. The Location EDD file contains general information about sampling locations and sample ID numbers. This table does
not need to be resubmitted if information has previously been submitted to EPA Region 2 in the EDD format
Location files should be named according to the following convention:
SiteNameDate.EPAIDCode.BasicLocations_v4.txt (or .csv).
Table 3.3 Location Data File Structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
1
Data Provider
Text (20)
Required
Data provider company code.
A-23
2
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
3
wellid
Text (30)

Well identification number
No
Basic Manual for Electronic Data
Version 6
16
USEPA Region 2
May 2019

-------
Table 3.3 Location Data File Structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
4
sitecode
Text (3)
Required
Code indicating the site operable unit for which the data is being
submitted. Must match the entry in column 1 (site code) of the
SITE EDD file. Typically the code is 01. unless there is a
second or third operable unit. Codes 02 or 03, for example,
should be used for the second and third operable unit,
respectively. Contact the EPA RPM if you are unsure of the
proper code to use.
No
5
Latitude
Number
w/precision
of up to 15
Required
Latitude of sampling location in decimal degrees (dd.xxxxxx).
Please provide 6 decimal digits. This field accepts "zero" (0)s if
the loc type = "Drum", "WSTAP", "SEISMIC", "WI",
"REMEDIATION" and "LANDFILL"
No
6
Longitude
Number
w/precision
of up to 15
Required
Latitude of sampling location in decimal degrees (dd.xxxxxx).
Please provide 6 decimal digits. This field accepts "zero" (0)s if
the loc type = "Drum", "WSTAP", "SEISMIC", "WI",
"REMEDIATION" and "LANDFILL"
No
7
surfelev
Number
w/precision
of up to 15
Required
Elevation in feet above sea level of the ground surface at the
sampling location.
No
8
Elevunit
Text (15)
Required
Unit of measurement for elevation
Units must be in
ftorm
9
coordsysdesc
Text (20)
Required
Sampling location coordinate system description. Must be in
decimal degrees, Latitude and Longitude. Values: 'LAT LONG'
No
10
locname
Text (40)
If available
Sampling location name. (May be identical to entry in column
1.)
No
11
locdesc
Text (255)
If available
Description of sampling location.
No
12
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
Basic Manual for Electronic Data
Version 6
17
USEPA Region 2
May 2019

-------
Table 3.3 Location Data File Structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
13
locpurpose
Text (20)
If available
Brief description of purpose for collecting sample.
No
14
within_facility_yn
Text (1)
Required
Indicate whether this sampling location is within the facility
(site) boundary.
Y= Yes N= No
15
depthtotopofscreen
Number
w/precision
of up to 15
Required if
location is
a well
Depth to the top of the well screen in feet below ground surface.
Default to null if sample is not from a well.

16
depthtobottomofscreen
Number
w/precision
of up to 15
Required if
location is
a well
Depth to bottom of well screen in feet below ground surface.
Default to null if sample is not from a well.
No
17
topcasingelev
Number
w/precision
of up to 15
Required if
location is
a well
Elevation of top of well casing in feet. Default to null if sample
is not from a well.
No
18
depthtobottomofwell
Number
w/precision
of up to 15
Required if
location is
a well
Depth to bottom of well in feet below ground surface. Default to
null if sample is not a well.
Table A-5
19
totaldepth
Number
w/precision
of up to 15
Required if
locations is
a well
Total depth of boring below ground surface in feet. Default to
null if sample is not a well.
Table A-6
20
remark
Text (255)
If needed
Any comments or information regarding the information in this
EDD file.

21
Horzcollectmethodcode
Text(3)
Required
Method used to determine the latitude/longitude measurements.
Horizontal collection Method.
Table A-3
Basic Manual for Electronic Data
Version 6
18
USEPA Region 2
May 2019

-------
Table 3.3 Location Data File Structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
22
Horzaccuracyvalue
Text(20)
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
23
Horzaccuracyunit
Text(15)
Required
Unit of the horizontal accuracy values.
Table A-4
24
Horzdatumcode
Text(3)
Required
Reference datum of the latitude and longitude
Table A-5
25
Streammile
Numeric

This indicates where the river or stream (stream code) the
station exists.
No
26
Streamcode
Text (30)

This indicates the river or stream in which the station exists.
Stream mile indicates where in the river/stream the stations
exists.
No
3.4 Chemistry Sample Result EDD File
The Chemistry Sample Result EDD file contains sample, test and result data. Data from both laboratory analysis and in situ
measurements taken in the field - such as pH, conductivity, and dissolved oxygen - are to be reported in this file. For surface water
samples, record the sample depths, start depth (field 9) and end depth (field 10), 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 3.5).
Each Chemistry Sample Result EDD file should be named according to the following convention:
SiteNameDate.EPAIDCode.EPAR2_BasicChemistry_v4.txt (or .csv)
Note: Field parameters
Table 3-4. Chemistry sample file data structure- BasicChemistry_v4
Basic Manual for Electronic Data
Version 6
19
USEPA Region 2
May 2019

-------
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
1
Data_provider
Text (20)
Required
Data provider company code
A-23
2
syssamplecode
Text (40)
Required
Unique sample identifier. Each sample must have a unique value to
identify the sample, including spikes and duplicates. If no sample ID is
available, enter the sys loc code plus the sample date. (e.g., MW01 +
March 11, 1991=> MW01031191). For trip blanks that do not have
unique sample IDs, enter «TB. plus the date, e.g., TB + April 5, 2017
=> TB04052017.
No
3
sysloccode
Text (20)
Required*
Sample collection location. Enter the same sys loc code, such as MW-
01, A24, SW12, or SB-2S, as it appeared in the Location EDD file.
*Field should be null if sample is not associated with a location, such
as a field QC sample (e.g., field blank or trip blank).
No
4
samplename
Text (30)
If available
Additional sample identification information if necessary. Should be
the same value as in the sys sample code field if no further naming
information applies.
No
5
sample matrix code
Text (4)
Required
Code which distinguishes between different types of sample matrix.
Table A-l


If sample matrix code ='SO'or'WG'and sample type code
'FD' then start depth, end depth, and depth unit are required.
= 'N' or







If sample type code = TB, EB, orFB then samplematrixcode
cannot be WG or SO.

6
sampletypecode
Text (4)
Required
Code which distinguishes between different types of samples. If
Table A-12

samplematrixcode = 'SO' or 'WG' and sample type code =
'FD' then start depth end depth, and depth unit are required.
'N' or











If sampletypecode = TB, EB, orFB then samplematrixcode
cannot be WG or SO.





Sys loc code is required where sample type code=N.





Parent sample code is required if
rt_sample_type.needs_parent_sample='Y'.

Basic Manual for Electronic Data
Version 6
20
USEPA Region 2
May 2019

-------
Table 3-4. Chemistry sample file data structure- BasicChemistry_v4
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
7
samplesource
Text (10)
Required
This field indicates if the sample originated in the field or in the lab.
For the BasicCHEM EDD file, in almost all cases the correct entry will
be aFicld.*
FIELD OR
LAB
8
parentsamplecode
Text (40)
Required for
field
duplicate
samples
This field applies to duplicate samples only and should contain the
entry in the "sys sample code" field for the sample from which the
duplicate sample was derived, i.e., the ¦parent, sample. If the sample is
not a duplicate sample, the field should be left null. A value other than
¦null, is required whenever the entry in the ¦samplctypecode*
column is FD, FR, FS, or LR.
No
9
sampledate
DateTime
Required
Date sample was collected in MM/DD/YYYY format. 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 36).
MM/DD/YYYY
format
10
startdepth
Number
w/precision
of up to 15
Required
when
"Samplemat
rix code" =
'SO' or 'WG'
and
"sampletype
code" = 'N'
or 'FD'
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
Basic Manual for Electronic Data
Version 6
21
USEPA Region 2
May 2019

-------
Table 3-4. Chemistry sample file data structure- BasicChemistry_v4
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
11
enddepth
Number
w/precision
of up to 15
Required
when
"Samplemat
rix code" =
'SO' or 'WG'
and
"Sampletype
code" = 'N'
or'FD'
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
12
depthunit
Text (15)
Required if
applicable
Unit of measurement for the sample beginning and ending depths
Default to null if not applicable.
Table A-18
13
composite_yn
Text (1)
If available
Code used to indicate whether a sample is a composite sample. Enter
¦Y. for yes and «N. for no. Default to null if the data are not available.
Y=yes
N=no
14
labanlmethodna
me
Text (35)
Required
Laboratory analytic method name or description.
Default to ^unknown* if the information is not available.
Table A-16
15
analysisdate
Date(10)
Required
Date of sample analysis. Should refer to either beginning or end time
of the analysis as required by EPA. Please report the analysis date as
the collection date plus 30 days where the analysis date is unknown, or
with another approximate date if a more accurate estimated date of
analysis is known. For measurements taken in the field (e.g., pH,
dissolved oxygen), use the same date as sample date (see Pos# 8).
Whenever an approximate date is used, document the way the date was
determined in the comment field (column 36 of this EDD file) and in
the cover letter that accompanies the EDD. Analysis date cannot
precede the sample date.
MM/DD/YYYY
format
16
Fraction
Text (4)
Required
Enumeration list contains the values
A-24
Basic Manual for Electronic Data
Version 6
22
USEPA Region 2
May 2019

-------
Table 3-4. Chemistry sample file data structure- BasicChemistry_v4
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
17
testtype
Text (10)
Required
Type of test. Valid values include "initial," "reextractl.* ¦ree\tract2..
¦reextract3," "reanalysis," ¦dilutionl.. «diluton2,. and ¦dilutonS,.
Use "initial" if unknown or data is from measurements taken in the
field (e.g., Ph, dissolved oxygen).
A-25
18
labmatrixcode
Text (3)
If available
Code that identifies the matrix, such as soil, groundwater, and
sediment, being sampled.. This field is included because the matrix of
the sample as analyzed in the lab may differ from the matrix in which it
arrived at the lab (e.g., TCLP leachate samples).
Table A-l
19
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 laboratory.
FI = field instrument
or probe
FL = mobile field
lab analysis
LB = lab analysis
20
basis
Text (3)
If available
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 be reported on the basis of dry
weight. Default to null if data are not available.
Wet
Dry
NA
21
dilutionfactor
Number w/
precision of
up to 7
If available
Effective test dilution factor. Default to null if data are not available or
is not applicable.
No
22
qclevel
Text (6)
Required
May be either "screen" for screening data or "quant" for quantitative
data. Default value is ¦quanta
screen
quant
23
labsampleid
Text (20)
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). Default to null if data are not available.
No
Use "UNKNOWN"
for historical data.
24
casrn
Text (15)
Required
Analyte code.
Table A-15
25
chemicalname
Text (75)
Required
Chemical name
Table A-15
Basic Manual for Electronic Data
Version 6
23
USEPA Region 2
May 2019

-------
Table 3-4. Chemistry sample file data structure- BasicChemistry_v4
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
26
resultvalue
Text (20)
Required *for
all detect
results
Analytic result reported using an appropriate number of significant
digits. Insert ¦null* for non-detect results.
* Required if detect flag = Y and result type code = «TRG« or bTIC.
No
27
resultunit
Text (15)
Required
when
resultvalue
is populated.
Unit of measurement for the result
Table A-18
28
resulttypecode
Text (3)
Required
Should be either "TRG" for a target or regular result, "TIC" for a
tentatively identified compound, "SUR" for a surrogate, "IS" for an
internal standard, or "SC" for spiked compound. Provide definitions if
other codes are used. Use "TRG" for data from field measurements.
No
29
reportableresult
Text (3)
Required
Must be either "Yes" for results that are considered reportable, or "No"
for other results. This field can be used to distinguish between multiple
results when 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. In both examples, the proper value for this field
should be provided by the laboratory, i.e., only one result should be
flagged as reportable. New condition: Samples with more than one
result with the same CAS RN cannot have Reportable result = Yes
Yes
No
Y
N
30
detectflag
Text (1)
Required
Enter "Y" for detected analytes and for estimated results above
detection limit but below the quantitation limit. Enter "N" for non-
detects. For tests such as flash point, use ">" and "<" [Note do not use
"<" to indicate non-detects.]
Y=detected
N=non detected
">""<" = flash point
31
labqualifiers
Text (10)
If available
Qualifier flags assigned by the laboratory. Definitions must be
provided in comment field (field 36) and in EDD cover letter for all
qualifiers which do not appear in the list of valid values.
Table A-10
Basic Manual for Electronic Data
Version 6
24
USEPA Region 2
May 2019

-------
Table 3-4. Chemistry sample file data structure- BasicChemistry_v4
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
32
validatorqualifiers
Text (10)
If available
Qualifier flags assigned by the person who validates the data received
from the lab. Definitions must be provided in comment field and cover
letter for all qualifiers if valid values are not used. EPAR region 2 is
not going to add any more qualifiers. Please contact Region 2 if a new
qualifier is needed
Table A-10
33
Interpretedqualifier
Text (10)
If available/
Required
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.
EPAR region 2 is not going to add any more qualifiers.
Table A-10
34
validated_yn
Text (1)
Required
Must be either "Y" for validate or "N" for not validate.
Indicate if the data
has been validated
35
reporting_detection_
limit
Numeric
Required if
non-detect
Concentration level above which results can be quantified with
confidence. Required if result is a non-detect (i.e., detect flag = 'N').
The value must reflect conditions such as dilution factor and moisture
content and must be sample-specific. Required for all results for which
such a limit is available. If the detection limit is unknown, enter null as
the detection limit and record ¦detection limit unknown, in the
comment field (field 36). [The value entered in this field should be the
sample-specific detection limit Do not enter the contract required
quantitation limit (CRQL) in this field. This value cannot be negative
unless one of the radiological fields (minimum detectable conc,
counting error, uncertainty, critical value) are populated.
No
Basic Manual for Electronic Data	2^	USEPA Region 2
Version 6	May 2019

-------
Table 3-4. Chemistry sample file data structure- BasicChemistry_v4
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
36
detectionlimitunit
Text (15)
Required
when
methoddetec
tionlimit,
reportingdet
ectionlimit,
or
quantitation^
imit is
populated.
Unit of measurement for the detection limit. This field is required if a
value other than null appears in the reporting detection limit field.
Table A-18





37
method_detection_
limit
Numeric
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
38
quantitationlimit
Numeric
If available
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
39
taskcode
Text (40)
If available
Code used to associate individual samples to a specific sampling event.
The format for this field is XX-P#, where XX is the type of task
required (PR = Pre Remedial, RI = Remedial Investigation, FS =
Feasibility Study, PD = Pre-Design, RD = Remedial Design, RA =
Remedial Construction, PC = Post Construction, RM = Removal
Action, BD = Before Dredge, AD = After Dredge, BR = Brown Fields,
SP = Special Project); P# is the phase the sampling event started. For
example, if sampling was performed for a Phase 1 Post Construction
site, the task code would be PC-PI.
No
40
resultcomments
Text (255)
If needed
Record any comments here.
No
41
LabSDG
Text (20)
If needed
Lab sample delivery group (SDG) identifier. A single sample may be
assigned to multiple SDG based on different analysis.
No

Basic Manual for Electronic Data
Version 6


26
USEPA Region 2
May 2019

-------
Table 3-4. Chemistry sample file data structure- BasicChemistry_v4
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
42
Validationlevel
Text (20)
If needed
EPA defined validation level
No
43
Labnamecode
Text (20)

Unique identifier of the laboratory as defined by the EPA. Controlled
vocabulary; see the lab valid value table in appendix.
Table A-17
3.5 Water Level EDD File
The Water Level EDD file includes information on water level measurements collected at the site over the years. 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. All fields in the Water Level file should be populated for groundwater elevation data (if data is available). For surface water
data, use only the first six fields (fields 1 through 6) and the "remark" field (field 10).
Each Water Level file containing historical data should be named according to the following convention:
SiteNameDate.EPAIDCode.BasicWater_Level_v4.txt (or .csv)
Table 3.5. Water Level file data structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
1
sysloccode
Text (20)
Required
Sample location ID, such as MW-01, from which water level
measurement was collected. Must be the same sys loc code
as reported in the Location EDD file.
No
Basic Manual for Electronic Data
Version 6
27
USEPA Region 2
May 2019

-------
Table 3.5. Water Level file data structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
2
measurementdate
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
format
3
Historicalreferencee
lev
Numeric
Required
Historical reference value. Used for the elevation of past
reference points. Elevation must be in feet.
No
4
waterleveldepth
Numeric
if available
Water level depth in feet below the reference elevation.
Default to null if data are not available.
No
5
waterlevelelev
Numeric
if available
Water level elevation in feet below the reference elevation.
Default to null if data are not available.
No
6
measured depth of w
ell
Numeric
If available
Depth below ground surface to bottom of well. Default to null
if data are not available.
No
7
depth_ unit
Text (15)
if available
Unit used for depth and elevation measurements.
Table A-18
8
remark
Text (255)
If needed
Remark or comment on measurement. Default to null where
the data are not available.
No
9
dry_indicator_yn
Text (1)
If available
Enter «Y. if the well was dry and «N. if it was not dry.
Default to null if data are not available.
Y= dry
N=not dry
10
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 (a drop
down with cas
number and
chemical name)
11
Lnapldepth
Text Number
with precision
of up to 7
If applicable
Depth to the top surface of the lnapl in feet below the
reference elevation.
No
Basic Manual for Electronic Data
Version 6
28
USEPA Region 2
May 2019

-------
Table 3.5. Water Level file data structure
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
12
Dnaplcasrn
Text (15)
If applicable
Analyte code of the dense non-aqueous phase liquid (dnalp)
present in the well..
Table A-15 (a drop
down with Cas
number and
chemical name)
13
Dnapledepth
Numeric
If applicable
Depth to the top surface of the dnapl in feet below the
reference elevation
No
14
Taskcode
Text (40)
If available
Code used to associate individual samples to a specific
sampling event. The format for this field is XX-P# where XX
is the type of task required (PR = Pre Remedial, RI =
Remedial Investigation, FS = Feasibility Study, PD = Pre-
Design, RD = Remedial Design, RA = Remedial
Construction, PC = Post Construction, RM = Removal
Action, BD = Before Dredge, AD = After Dredge, BR =
Brown Fields, SP = Special Project); P# is the phase; For
example, if sampling was performed for a Phase 1 Post
Construction site, the task code would be PC-PI.
No
3.6 Geology EDD File - Optional
The Field file contains general information on geology data collected at and in the vicinity of the site.
Note: This file is an optional file that Region 2 requests be submitted if the data is readily available. However, this file may become a
required submittal at the discretion of the responsible Remedial Project Manager (RPM) in order to perform certain analyses.
The historical Geology EDD file should be named according to the following naming convention:
SiteNameDate.EPAIDCode.BasicGeology_v4.txt (or .csv).
Basic Manual for Electronic Data
Version 6
29
USEPA Region 2
May 2019

-------
Table 3-6. Geology file data structure





Valid Values
Pos#
Column Name
Data Type
Required
Description
In Appendix
1
sysloccode
Text (20)
Required
Sample location ID, such as MW-01. Must be the same
sys loc code as reported in the Location EDD file.

2
startdepth
Numeric
Required
Start depth of the geologic unit in feet below ground
surface.

3
materialtype
Text (40)
If applicable
The type of material that composes the lithologic unit.
Acceptable valid values are listed in Table A-19 of the
EDD Specification Manual. Must be filled in all cases
except if a depth-specific comment is being made.

4
geounitcodel
Text (20)
Required
The data providers interpretation of the hydrogeologic
unit. This field may be used to indicate the geologic unit in
terms of general hydrostratigraphy (e.g., aquiferl,
aquiclude, aquifer2) or in terms of a grouping of lithologic
layers (e.g., fill, clay, gravel). Examples of possible
geologic groupings are provided in Figure A-2 of the EDD
Specification Manual.

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 and/or transport computer modeling that
contains the lithologic unit. Examples of possible geologic
groupings are provided in Figure A-2 of the EDD
Specification Manual.

6
remarks
Text (255)
If needed
General remarks concerning the lithologic or geologic
unit(s).

3.7 Extraction ¦ Injection Well EDD File
The Extraction-Injection Well (ExtractionlnjectionWells) 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 Extraction Injection Wells EDD
Basic Manual for Electronic Data
Version 6
30
USEPA Region 2
May 2019

-------
file is to provide EPA Region 2 with designed pumping rates as well as the actual pumping rates for each well during a particular
reporting period. This information will be useful for determining if the remedial system is successfully capturing the contaminant
plume. This file is identical to the file described in the EPA Region 2 Electronic Data Deliverable (EDD) Specification Manual.
When checking this file with the Electronic Data Processor (EDP), use the ExtractionInjectionWells_v4 format. Each Extraction-
Injection Well EDD file must be named according to the following convention:
SiteNameDate.EPAIDCode.ExtractionInjectionWells_v4.txt (or .csv)
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-2)
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.
MM/DD/YYYY
HH:MM:SS
format.
4
avg_pump_rate
Number
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
endmeasurementdate)
No
5
pumprateunit
Text (15)
Required
Unit of measure for the pumping rate.
Table A-18
6
pctoperatingtime
Numeric
If Available
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
operatingmode
Text (20)
Required
Mode in which well was operating during the reported
interval. Select from the followoing valid values:
EXTRACTION, INJECTION, RECIRCULATION,
PULSE, DEVEL, UNUSE.
EXTRACTION,
INJECTION,
RECIRCULATIO
N, PULSE,
DEVEL, UNUSE.
Basic Manual for Electronic Data
Version 6
31
USEPA Region 2
May 2019

-------
Pos#
Column Name
Data Type
Required
Description
Valid Values
In Appendix
8
designrate
Numberic
Required
Pumping rate as specified in the approved remedial
design report for fully capturing site groundwater
contamination.
No
9
designrateunit
Text (15)
Required
Unit of measure for the design pumping rate.
Table A-18
10
ratemeasurementtype
Text (20)
If available
Type of measurements used for averaging. Select from
the following valid values: TOTALIZER (totalizing
flow meter), MANIFOLD (estimated from total
manifold flow), ESTIMATE (estimate from prior
values), AVERAGE (average of instantaneous
measurements).
Totalizer
Manifold
Estimate
Average
11
suction
Numeric
If available
Vacuum in well (e.g., wellpoint vacuum) or well casing
(e.g., vacuum well), reported in equivalent feet of water.
No
12
remark
Text (255)
If available
Remarks regarding the pumping rate measurements.
No
Basic Manual for Electronic Data
Version 6
32
USEPA Region 2
May 2019

-------
Attachment 1
EXAMPLES OF EDD FILES
Basic Manual for Electronic Data
Version 6
33
USEPA Region 2
May 2019

-------
EXAMPLES OF EDD FILES READY FOR CONVERSION TO TEXT FILES
Examples of EDD files with the first few rows of the EDD populated with a typical data set are presented in Figures 1 through 7. 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) (see section 2.1), check the files using the EDP (see section 2.11), and then send the error free files to Region
2. In order to fit the examples on one page, not all of the fields (i.e., columns) were included for certain files (e.g., Site, Location,
Chemistry Result). 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.5 regarding reporting blanks, or "null" values).
Figure 1. Example of Site File Ready for Conversion to Text File
sitecode
facilityid
sitename
sitetaskcode
sitedescl
site_desc2
contactname
address 1
01
FAC123456723
Example Site



John Smith
23 Main Street
Additional
Fields
email address
abc(S?abd.com
Figure 2. Example of Location File Ready for Conversion to Text File
Location (Location) File:
sysloccode
wellid
sitecode
Latitude
Longitude
surfelev
coordsysdesc
Locname
Locdesc
Loctype
Locpurpo
se
MW01
MW01
01
44.24543
-73.414456
120.2
LAT LONG
Lagoon

MW

SB-01
NONE
01
44.24304
-73.470923
126.3
LAT LONG


Soilbore

MW03
MW03
01
44.24700
-73.460123
130.1
LAT LONG
Landfill
Shallow
well
MW

MW04
MW04
01
44.24700
-73.460123
130.1
LAT LONG
landfill
Deep well
MW

Additional
Fields
comment
Notes: SB-01 has no well therefore "NONE" is entered in sys_well_id.
MW03 and MW03 are multiple wells within same boring.
Basic Manual for Electronic Data
Version 6
34
USEPA Region 2
May 2019

-------
Figure 3. Example of Chemistry Result File Ready for Conversion to Text File
sys_sample_
code
Sysloc
code
sample_
name
sample_
matrix_
code
sample_
type_
code
sample_
source
parentsamp
lecode
sample_
date
Start_
depth
End_
depth
Depth
unit
Composite
y/n
lab_anl_
method_
name
Analysis date
Total or
disolved
MWO1040198
MW-01

WG
N
Field

04/01/2017
00:00:00
10
12
Ft

SW8240
04/02/2017
D
MW02040198
MW-03

WG
N
Field

04/01/2017
00:00:00



N
SW8240
04/02/2017
D
MW02040198
MW-03

WG
N
Field

04/01/2017
00:00:00



N
SW8240
04/02/2017
D
Figure 3. Example of Chemistry Result File Ready for Conversion to Text File (continued)
test
Lab
analysis
Additional
qc
lab
Additional
Cas rn
Chemical
Result
Result
reportable
Detect
Addition
reporting
type
Matrix
location
Fields
level
sample
Fields

name
value
type
result
flag
al
detection
code



id_




code

Fields
limit
Initial
WG
LB

quant


71-43-2
BENZENE
23.20
TRG
Yes
Y

5
Initial
WG
LB
quant
LAB02
108-88-3
TOLUENE

TRG
Yes
N

100
Reanalysis
WG
LB
quant

1330-20-7
XYLENES

TRG
Yes
N

10
Additional
Fields
Figure 4. Example of Water Level File Ready for Conversion to Tex
sysloccode
syswellid
measurement
date
refelev
waterleveldepth
w aterlevelelev
MW01
MW01
05/10/2017
13:10:00
120.2
31.1
89.1
MW02
MW02
05/10/2017
13:45:00
123.1
34.1
89.0
Additional
Fields
File
remark
Figure 5. Example of Extraction - Injection Well File Ready for Conversion to Text File
Basic Manual for Electronic Data	^ 5	USEPA Region 2
Version 6	May 2019

-------
sysloc
code
sys_well
code
Start_
measurement
date
endmeasure
date
avg pump rate
pumprateunit
EX-01
EX-01
05/12/2017 11:23:00
06/12/2017
11:30:00
2.5
mgd
EX-02
EX-02
11/12/2017 12:00:00
12/12/2017
13:10:00
1.75
mgd
Additional
Fields
remark
Figure 6. Example of Geology File Ready for Conversion to Text File
sysloccode
startdepth
materialtype
geounitl
geo_unit_2
Remark
MW-03
0
CL
Glacial
AquiferO

MW-03
10
SW
Outwash
Aquifierl

MW-03
23
SP
Outwash
Aquifer2

SB-01
0
ML
Alluvial
AquiferO

Basic Manual for Electronic Data
Version 6
36
USEPA Region 2
May 2019

-------