Basic
Manual for Historic Electronic Data
EPA Region 2
Prepared By:
Region 2 Superfund Division
Environmental Protection Agency
June 2009
Version 1.3
-------
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 EDO REPORTING REQUIREMENTS 2
2.1 File Formats 2
2.2 EDO Files 3
2.3 File Naming Convention 5
2.4 Data Integrity Rules 6
2.5 Reporting Null Values 7
2.6 Valid Values 7
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.2SiteEDDFile 14
3.2 Location EDD File 16
3.3 Chemistry Sample Result EDD File 19
3.4 Water Level EDD File 25
3.5 Geology EDD File-Optional 27
3.6 Extraction - Injection Well EDD File 29
-------
1.0 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 Region! Superfund EDD Website located at:
http://www.epa.gov/region02/superfund/medd.htm
Basic Manual for Historic Electronic Data i USEPA Region 2
Versionl.3 March 2009
-------
2.0 GENERAL EDO 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
Access
Excel
Quattro® v8
Word
Lotus 1-2-3
Type
Database
Spreadsheet
Spreadsheet
Word
Processor
Spreadsheet
Instructions
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.
Select "File," "Save As," from the top menu. Change
"Save as Type" to a "Text (Tab Delimited)" file. Press
the "Save" button.
Select "File," "Save As," from the top menu. Change the
"File Type" to "ASCII Text (Tab Delimited)." Press the
"Save Button."
[Note: A word processor is not the best tool for the job!
A large paper size will have to be selected to prevent
wrapping for most files. ] [wrapping?]
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).
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
Versionl.3
USEPA Region 2
March 2009
-------
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
Base Map
Data
Provider
Site
(Section 3.1)
Location
(Section 3.2)
File Name
SiteName.DXF
SiteNameDate.
EPAID.
EPAR2DPR_vl.t
xt (or csv)
SiteNameDate.
EPAID.
EPAR2SITE_vl.
txt (or csv)
SiteNameDate. E
PAIDCode.
BasicLOC.txt (or
.csv).
Created
By
Data
provider
Data
Provider
Data
provider
Data
provider's
surveyor
Contents
Basemapof site.
Information about the
data provider
One-time definition
of site including EPA
Region 2 data
providers' contact
information.
One entry for each
location on a site.
Contains elevation,
coordinate and
general locational
data. Data should
only be reported once
for a location.
What makes a
row of data
unique?
Not applicable
Not applicable
site_code
sys_loc_code
Dependence of
other files on
these data
Not applicable.
Not applicable
The location file
cannot be loaded
without properly
referenced sites
(site_code).
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
Versionl.3
USEPA Region 2
March 2009
-------
Table 2.2 General Information on EDD Files
File Type
Chemistry
Sample
Result
(Section 3.3)
Water Level
(Section 3.4)
Geology
(Optional)
(Section 3.5)
Extraction-
Injection
Well
(Section 3.6)
File Name
SiteNameDate.
EPAID.
BasicChem_vl.
txt (or csv)
SiteNameDate. E
PAIDCode.
BasicWTR.txt
(or .csv).
SiteNameDate. E
PAIDCode.
BasicGEO.txt (or
.csv).
SiteNameDate.
EPAIDCode.
EPAR2EIW_vl.
Txt (or csv)
Created
By
Data
provider's
field
sampling
team(s)
and
testing
lab(s)
Data
provider's
field
sampling
team(s)
Data
provider's
geologist
Data
provider's
field
sampling
team(s)
Contents
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.
Groundwater level
data for monitoring
wells
Geology data for a
borehole.
Data that relates to
any extraction wells
that are operating as
part of the remedial
action.
What makes a
row of data
unique?
sys_sample_code
lab_anl_method_
name
analysis_date
total_or_dissolved
test_type
cas_rn
sys_loc_code
measurement_date
measurement_time
sys_loc_code
start_depth
sys_loc_code
start_measurement
_date
start_measurement
_time
Dependence of
other files on
these data
None
None.
None.
None.
Basic Manual for Historic Electronic Data
Versionl.3
USEPA Region 2
March 2009
-------
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 may be obtained from the EQuIS Database Administrator.
To use the Sign and Submit feature, after data files have been loaded and all of the errors have been
resolved,
1. Select Sign and Submit from the Application Menu. This will open the Sign and Submit window.
xj
User Narre; username
Passwo'd; I**********
Program Code;
Registry ID;
P* Save Password
Submit
Figure 13: Sign and Submit Window
2. Enter your User Name and Password as well as the Program Code that applies to the data package
being submitted. The Registry ID will be automatically populated based on the selected Program Code.
For this exercise use your name as the User Name and Password, and 'NYO123456' for the Program
Code. This information will be used to create a user certificate file that EQuIS Enterprise uses to ensure a
valid user is submitting data for the appropriate Program. NOTE: The Program Code and Registry ID
are extremely important for Enterprise Data Submittals; however, the data entered into these sections of
the Sign and Submit screen may be modified by the user as needed.
3. Click the Submit 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
Program Code, a period, the Registry ID, a period and the Format File name used to create the EDDs.
(Example file name: '20080424. NY0123456.RegID123.EPARegion2EDD.zip'). The contents of the
Zipped file includes text files named for the sections of the format used to create them.
5. Select Save. Once the zipped EDD Package has been saved the following screen will appear.
Basic Manual for Historic Electronic Data
Versionl.3
USEPA Region 2
March 2009
-------
EDO Signed and Submitted
Figure 14: Sign and Submit Verification Window
6. Select OK
After the zipped file has been created the EDD Package is ready to be submitted to your regulator for
loading into EQuIS Professional EDP or EQuIS Enterprise EDP.
Each EDD file, except the base map file, should be named according to the following
convention:
SiteNameDate.EPAIDCode.E7Mtf2EDDFileTypevl.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 twelve-character alphanumeric CERCLIS ID number designated by EPA for the site. The
code consists of the two-letter abbreviation of the State in which the site is located, followed by
the letter "D," followed by a unique nine-digit number. CERCLIS ID numbers for sites can be
found in Table A-22 of the Comprehensive Manual for Electronic Data. The third part of the
EDD file name refers to the type of EDD file being submitted, e.g., EPAR2Site_vl,
BasicLOC_vl, 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 "vl" 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 February 19, 2000 would be reported in a
file named ABC20000219.XYZ123456789.BasicCHEM_vl.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
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
sample_matrix_code field of the Sample Result file and must be reported using one of the values
Basic Manual for Historic Electronic Data f. USEPA Region 2
Versionl.3 March 2009
-------
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
"data_one""data_two"
"data_three"
"data_one", "datajwo", "datajhree"
"data_one" "data_three"
" data_one "„" datajhree "
"data_one" "data_three"
"data one", "data three"
Comment
O.K. All fields populated, one tab or comma
between fields.
O.K. Optional field not populated, 2 tabs or 2
commas between first and third field.
Not O.K. Optional field omitted, only 1 tab or
comma between first and third field.
2.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
Basic Manual for Historic Electronic Data
Versionl.3
USEPA Region 2
March 2009
-------
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 o USEPA Region 2
Versionl.3 March 2009
-------
Table 2-4. Cross-reference between the valid value tables in appendix and the EDD files
Valid Value Table
Name
Matrix
Location Type
Qualifier
Result Type
Sample Type
Analyte
Lab Analysis Method
Name
Unit
Geology Soil
Materials
EPA Facility IDs
Company Codes
Fraction (Total or
dissolved)
Test Type
Test Batch Type
Table
Number
A-l
A-9
A-10
A-ll
A-12
A-15
A-16
A-18
A-19
A-22
A-23
A-24
A-25
A-26
Field Name
sample matrix code, lab matrix code
loc_type
lab qualifiers, validator qualifiers
result type code
sample type code
cas_rn, chemical_name, dnapl_cas_rn,
lnapl_cas_rn
lab_anl_method_name
various unit fields throughout all files
material type
facility id, site name, city
Data_provider_code, data_provider
Total or dissolved
Test type
Test batch type
EDD File
Chemistry
Sample Result
Location
Chemistry
Sample Result
Chemistry
Sample Result
Chemistry
Sample Result
Chemistry
Sample Result
Water Level
Chemistry
Sample Result
All Files
Geology
Site
Location, Sample,
Test Result, Data
Provider
Test Result, Test
Result QC, Batch
Test Result, Test
Result QC, Batch
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 reporting_detection_limit
and detection_limit_unit 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
Value
Detect
Flag
Reporting
Detection
Detection
Limit Unit
Result comment
Laboratory
qualifiers
Basic Manual for Historic Electronic Data
Versionl.3
USEPA Region 2
March 2009
-------
108-88-3
108-88-3
.15
Y
N
Limit
.005
.005
ug/ml
ug/ml
not detected
U
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
reportable_result field.. The initial test, and any retest result not considered reportable will have
reportable_result set to "No". Table 2.6 provides examples of reporting re-tests.
Table 2-6. Example of reporting re-tests
Test
Type
Initial
Initial
Initial
Dilution
1
Chem
Name
Benzene
Toluene
Xylenes
Benzene
Casrn
71-43-2
108-88-3
1330-20-
7
71-43-2
Result
Value
1000
5
5
780
Detect
Flag
Y
N
N
Y
Lab
Qualifiers
E
U
U
Reportable
Result
No
Yes
Yes
Yes
Result Comment
too concentrated
to quantitate
not detected
not detected
quantitated
2.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
cas_rn 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
Unknown
Unknown Hydrocarbon
Unknown PAHs
Unknown Aromatics
Number for TIC
1-10
1-10
1-10
1-10
Reported Name in cas rn
Unknown 1 -Unknown 10
UnkHydrocarbl - UnkHydrocarbl 0
UnkPAHl -UnkPAHIO
UnkAromaticl - UnkAromaticlO
Basic Manual for Historic Electronic Data
Versionl.3
10
USEPA Region 2
March 2009
-------
Unknown VOA
Unknown SV
1-10
1-10
UnkVOAl -UnkVOAlO
UnkSVl -UnkSVIO
2.10 Using the Electronic Data Processor to Check EDD Formatting
All EDD files must be run 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 http://www.epa.gov/region02/superfund/medd.htm 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.gov 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
everyway except the errors are corrected.
Basic Manual for Historic Electronic Data i i USEPA Region 2
Versionl.3 March 2009
-------
3.0 EDO 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.EPAR2DPRvl.txt (or .csv)
Basic Manual for Electronic Data i o USEPA Region 2
Version 1.3 March 2009
-------
Table 3.1 Data Provider File Structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
Column
Name
Data Provider
code
Data Provider
Contact Name
Contact
Address 1
Contact
Address 2
Contact City
Contact State
Contact zip
code
Contact
Country
Contact
phone
number
Contact email
address
Data Type
Text(20)
Text(70)
Text(50)
Text(40)
Text(40)
Text(30)
Text(lO)
Text(30)
Text(50)
Text(20)
Text(lOO)
Required
Required
Required
Required
Required
If available
Required
Required
Required
If available
Required
If available
Description
Data provider company code
This is the name of the company who is responsible for providing the
site data.
This is the name of the contact person who is responsible for providing
the site data.
Contact Address
Contact Address
Contact City
Contact state
Contact zip
Contact country
Contact phone number
Contact email address
Valid Values
In Appendix
A-23
A-23
No
No
No
No
No
No
No
No
No
Basic Manual for Electronic Data
Version 1.3
13
USEPA Region 2
March 2009
-------
3.2Site 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.EPAR2Sitevl.txt (or .csv).
Basic Manual for Electronic Data i A USEPA Region 2
Version 1.3 March 2009
-------
Table 3-2. SITE data file structure
Pos#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Column Name
site code
Program_Code
site name
site_task_code
site descl
site desc2
contact_name
addressl
address2
City
State
Zipcode
phone number
alt_phone_number
fax_number
email address
Data Type
Text(3)
Text(20)
Text(60)
Text(20)
Text(255)
Text(255)
Text(50)
Text(40)
Text(40)
Text(30)
Text(2)
Text(lO)
Text(30)
Text(30)
Text(30)
Text(lOO)
Required
Required
If available
Required
If available
If available
If available
Required
Required
If available
Required
Required
Required
Required
If available
If available
Required
Description
Code indicating the site operable unit for which the data is
collected, or area of concern (AOC). Typically the code is
"01" unless there is a second or third operable unit at facility.
Codes of "02" and "03" should be used for second and third
operable units, respectively. Contact the EPA RPM if unsure
of proper code.
This is equivalent to the EPA CERCLIS ID number, or
SRPID or other state program code
Name of site
Code used to identify the task under which the site or area is
investigated. This field is for informational purposes only.
Field samples are formally associated with task codes.
General description of the site.
Additional description of site, if necessary.
Name of person to contact if EPA Region 2 has any
questions about the EDD.
Site address, part one.
Site address, part two. Default to null if information is not
needed
Site city.
Site state.
Site zip code.
Site contact phone number.
Alternate phone number for site contact. Default to null
where the data are not available.
Fax number of site contact. Default to null where the data is
not available.
Site contact e-mail address.
Valid Values
In Appendix
No
Table A-22
Table A-22
No
No
No
No
No
No
No
No
No
No
No
No
No
Basic Manual for Electronic Data
Version 1.3
15
USEPA Region 2
March 2009
-------
3.2 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.BasicLOCvl.txt (or .csv).
Basic Manual for Electronic Data i £ USEPA Region 2
Version 1.3 March 2009
-------
SiteNameDate.EPAIDCode. BasicLOC vl.txt (or .csv)
Table 3.3 Location Data File Structure
Pos#
1
2
3
4
5
6
7
8
Column Name
Data Provider
sys_loc_code
sys_well_id
primary _site_code
Longitude
Latitude
surf_elev
Elev_unit
Data Type
Text(20)
Text (20)
Text (20)
Text (3)
Number
w/precision
of up to 15
Number
w/precision
of up to 15
Number
w/precision
of up to 15
Text (2)
Required
Required
Required
Required
Required
Required
Required
Required
Required
Description
Data provider company code.
Location ID, such as MW-01, A24, SW12, or SB-2S,
for all samples collected, including groundwater
samples, hydropunch samples, surface
water/sediment samples, and soil samples. For
facility center point, sys loc code = "FAC CENTER
POINT"
Well identification number
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.
Longitude of sampling location in decimal degrees. Must be
negative for western hemisphere (-ddd.xxxxxx).
Latitude of sampling location in decimal degrees (dd.xxxxxx).
Elevation in feet above sea level of the ground surface at the
sampling location.
Unit of measurement for elevation
Valid Values
In Appendix
A-23
No
No
No
No
No
No
Units must be in
ftorm
Basic Manual for Electronic Data
Version 1.3
17
USEPA Region 2
March 2009
-------
Table 3.3 Location Data File Structure
Pos#
9
10
11
12
13
14
15
16
17
18
Column Name
coord_sys_desc
loc_name
loc_desc
locjype
loc_purpose
within_facility_yn
depth_to_top_of_screen
depth_to_bottom_of_screen
top_casing_elev
depth_to_bottom_of_well
Data Type
Text (50)
Text(40)
Text(255)
Text (10)
Text (20)
Text (1)
Number
w/precision
of up to 15
Number
w/precision
of up to 15
Number
w/precision
of up to 15
Number
w/precision
of up to 15
Required
Required
If available
If available
If available
If available
Required
Required if
location is
a well
Required if
location is
a well
Required if
location is
a well
Required if
location is
a well
Description
Sampling location coordinate system description. Must be in
decimal degrees, Latitude and Longitude.
Sampling location name. (May be identical to entry in column
1.)
Description of sampling location.
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.
Brief description of purpose for collecting sample.
Indicate whether this sampling location is within the facility
(site) boundary.
Depth to the top of the well screen in feet below ground surface.
Default to null if sample is not from a well.
Depth to bottom of well screen in feet below ground surface.
Default to null if sample is not from a well.
Elevation of top of well casing in feet. Default to null if sample
is not from a well.
Depth to bottom of well in feet below ground surface. Default to
null if sample is not a well.
Valid Values
In Appendix
No
No
No
No
No
Y= Yes N= No
No
No
Table A-5
Basic Manual for Electronic Data
Version 1.3
18
USEPA Region 2
March 2009
-------
Table 3.3 Location Data File Structure
Pos#
19
20
21
22
23
24
Column Name
total_depth
remarks
Horz_collect_method_code
Horz_accuracy_value
Horz_accuracy_unit
Horz_datum_code
Data Type
Number
w/precision
of up to 15
Text (255)
Text(3)
Text (20)
Text(8)
Text (3)
Required
Required if
locations is
a well
If needed
Required
Required
Required
Required
Description
Total depth of boring below ground surface in feet. Default to
null if sample is not a well.
Any comments or information regarding the information in this
EDO file.
Method used to determine the latitude/longitude measurements.
Horizontal collection Method.
Accuracy range (+/-) of the latitude and longitude. Only the
least accurate measurement should be reported, regardless if it is
for latitude or longitude.
Unit of the horizontal accuracy values.
Reference datum of the latitude and longitude
Valid Values
In Appendix
Table A-6
Table A-3
No
Table A-4
Table A-5
3.3 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.EPAR2SMPvl.txt (or .csv)
Note: Field parameters
Basic Manual for Electronic Data
Version 1.3
19
USEPA Region 2
March 2009
-------
Table 3-4. Chemistry sample file data structure
Pos#
1
2
3
4
5
6
7
8
Column Name
Data_provider
sys_sample_code
sys_loc_code
sample_name
sample_matrix_code
sample_type_code
sample_source
parent_sample_code
Data Type
Text (20)
Text(40)
Text (20)
Text (30)
Text (3)
Text (3)
Text (5)
Text (40)
Required
Required
Required
Required*
If available
Required
Required
Required
Required
for field
duplicate
samples
Description
Data provider company code
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). Fortrip blanks that do not have
unique sample IDs, enter "TB" plus the date, e.g., TB + April 5, 2000 =>
TB04052000.
Sample collection location. Enter the same sys_loc_code, such as MW-
01, A24, SW12, or SB-2S, as it appeared in the Location EDO 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).
Additional sample identification information, if necessary. Should be the
same value as in the sys_sample_code field if no further naming
information applies.
Code that identifies the matrix, such as soil, groundwater, and sediment,
being sampled. For acceptable valid values, see Table A-l in the EDD
Specification Manual Valid Value Appendix. Definitions should be
provided for all codes where valid values are not used.
Code which distinguishes between different types of samples, for
example field samples versus laboratory method blank samples
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
"Field."
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 "sample_type_code" column is FD,
FR, FS, or LR.
Valid Values
In Appendix
A-23
No
No
No
Table A-l
Table A-12
No
No
Basic Manual for Electronic Data
Version 1.3
20
USEPA Region 2
March 2009
-------
Table 3-4. Chemistry sample file data structure
Pos#
9
10
11
12
13
14
Column Name
sample_date
start_depth
end_depth
depth_unit
composite_yn
lab_anl_method_na
me
Data Type
Date (10)
Number
w/precision
of up to 15
Number
w/precision
of up to 15
Text (15)
Text (1)
Text (35)
Required
Required
Required if
applicable
Required if
applicable
Required if
applicable
If available
Required
Description
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).
Beginning depth (top) of sample in feet below ground surface. Required
for soil boring or grab samples with a depth component. Use only for
groundwater samples if discrete samples are collected from different
depths from a single well (i.e., the samples have the same
"sys_well_id"). An example of this situation would be multiple well
packer samples. Default to null if not applicable.
Ending depth (bottom) of sample in feet below ground surface. Required
for soil boring or grab samples with a depth component. Use only for
groundwater samples if discrete samples are collected from different
depths from a single well (i.e., the samples have the same
"sys_well_id"). An example of this situation would be multiple well
packer samples. Default to null if not applicable..
Unit of measurement for the sample beginning and ending depths
Default to null if not applicable.
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.
Laboratory analytic method name or description.
Default to 'unknown' if the information is not available.
Valid Values
In Appendix
MM/DD/YYYY
format
No
Ni
Table A- 18
Y=yes
N=no
Table A-16
Basic Manual for Electronic Data
Version 1.3
21
USEPA Region 2
March 2009
-------
Table 3-4. Chemistry sample file data structure
Pos#
15
16
17
18
19
20
Column Name
analysis_date
total_or_dissolved
test_type
lab_matrix_code
analysis_location
basis
Data Type
Date(lO)
Text (1)
Text (10)
Text (3)
Text (2)
Text (3)
Required
Required
Required
Required
If available
Required
If available
Description
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.
Enter "D" for results from a sample that was filtered and a "T" for
samples that were not filtered or were analyzed for total metals. Use
"T" if unknown or data are from field measurements.
Type of test. Valid values include "initial," "reextractl," "reextract2,"
"reextractS," "reanalysis," "dilutionl," "diluton2," and"diluton3." ."
Use "initial" if unknown or data is from measurements taken in the field
(e.g., pH, dissolved oxygen).
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).
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.
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.
Valid Values
In Appendix
MM/DD/YYYY
format
A-24
A-25
Table A-l
FI = field
instrument or probe
FL = mobile field
lab analysis
LB = lab analysis
Wet
Dry
NA
Basic Manual for Electronic Data
Version 1.3
22
USEPA Region 2
March 2009
-------
Table 3-4. Chemistry sample file data structure
Pos#
21
22
23
24
25
26
27
28
29
Column Name
dilution_factor
qc_level
lab_sample_id
cas_rn
chemical_name
result_value
result_type_code
reportable_result
detect_flag
Data Type
Number w/
precision of
up to 7
Text (6)
Text (20)
Text (15)
Text(75)
Text (20)
Text (3)
Text (3)
Text (1)
Required
If available
Required
If available
Required
Required
Required
*for all
detect
results
Required
Required
Required
Description
Effective test dilution factor. Default to null if data are not available or
is not applicable.
May be either "screen" for screening data or "quant" for quantitative
data. Default value is "quant."
Laboratory LIMS sample identifier. If necessary, a field sample may
have more than one LIMS lab_sample_id (maximum one per each test
event). Default to null if data are not available.
Analyte code.
Chemical name
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 "TIC"
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.
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.
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.]
Valid Values
In Appendix
No
screen
quant
No
Table A- 15
Table A- 15
No
No
Yes
No
Y=detected
N=non detected
">""<" = flash
point
Basic Manual for Electronic Data
Version 1.3
23
USEPA Region 2
March 2009
-------
Table 3-4. Chemistry sample file data structure
Pos#
30
31
32
33
34
35
36
37
Column Name
lab_qualifiers
validator_qualifiers
Interpreted_qualifier
organic_yn
reporting_detection_
limit
result_unit
detection_limit_unit
method_detection_
limit
Data Type
Text (10)
Text (10)
Text(lO)
Text (1)
Text (20)
Text (15)
Text (15)
Text(20)
Required
If available
If available
If
available/
Required
Required
Required if
non-detect
Required if
the result is
a detect
Required if
non-detect
If available
Description
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.
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. A request for adding
the value to the EPA Region 2 list of valid values should be included in
the cover letter also.
Interpreted qualifier flag assigned by the data provider. The interpret
qualifier is required if lap_qualifer or validator _qualifier are populated
Must be either "Y" for organic constituents or "N" for inorganic
constituents. Use "Y" for data from field measurements.
Concentration level above which results can be quantified with
confidence. Required if result is a non-detect (i.e., detect_flag = 'Y').
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.
Unit of measurement for the result
Unit of measurement for the detection limit. This field is required if a
value other than null appears in the reporting_detection_limit field.
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.
Valid Values
In Appendix
Table A-10
Table A-10
Table A-10
Y=organic
N=inorganic
No
Table A- 18
Table A- 18
No
Basic Manual for Electronic Data
Version 1.3
24
USEPA Region 2
March 2009
-------
Table 3-4. Chemistry sample file data structure
Pos#
38
39
40
Column Name
quantitation_limit
task_code
result comments
Data Type
Text(20)
Text(20)
Text (255)
Required
If available
If available
If needed
Description
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.
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-PL
Record any comments here.
Valid Values
In Appendix
No
No
No
3.4 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.BasicWTRvl.txt (or .csv)
Table 3.5. Water Level file data structure
Basic Manual for Electronic Data
Version 1.3
25
USEPA Region 2
March 2009
-------
Pos#
1
2
3
4
5
6
7
8
9
10
11
Column Name
sys_loc_code
measurement_date
Historical reference e
lev
water_level_depth
water_level_elev
measured depth of w
ell
depth_ unit
remark
dry_indicator_yn
Lnapl_cas_rn
Lnapl_depth
Data Type
Text (20)
DateTime
Number with
precision of up
to 15
Number with
precision of up
to 7
Number with
precision of up
to 7
Number with
precision of up
to 7
Text (15)
Text (255)
Text (1)
Text (15)
Text Number
with precision
of up to 7
Required
Required
Required
Required
Required if
available
Required if
available
If available
Required if
available
If needed
If available
If applicable
If applicable
Description
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.
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).
Historical reference value. Used for the elevation of past
reference points. Elevation must be in feet.
Water level depth in feet below the reference elevation.
Default to null if data are not available.
Water level elevation in feet below the reference elevation.
Default to null if data are not available.
Depth below ground surface to bottom of well. Default to null
if data are not available.
Unit used for depth and elevation measurements..
Remark or comment on measurement. Default to null where
the data are not available.
Enter "Y" if the well was dry and "N" if it was not dry.
Default to null if data are not available.
Analyte code of the light non-aqueous phase liquid (Inapl)
present in the well. Use appropriate valid value from Table A-
15 in the EDD Specification Manual Valid Value Appendix.
Depth to the top surface of the Inapl in feet below the
reference elevation.
Valid Values
In Appendix
No
MM/DD/YYYY
format
No
No
No
No
Table A- 18
No
Y=dry
N=not dry
Table A- 15
No
Basic Manual for Electronic Data
Version 1.3
26
USEPA Region 2
March 2009
-------
Table 3.5. Water Level file data structure
Pos#
12
13
14
Column Name
Dnapl_cas_rn
Dnaple_depth
Task_code
Data Type
Text (15)
Number with
precision of up
to 7
Text(20)
Required
If applicable
If applicable
If available
Description
Analyte code of the dense non-aqueous phase liquid (dnalp)
present in the well..
Depth to the top surface of the dnapl in feet below the
reference elevation
Code used to associate individual samples to a specific
sampling event. The format for this field is XX-P# where XX
is the type of task required (PR = Pre Remedial, RI =
Remedial Investigation, FS = Feasibility Study, PD = Pre-
Design, RD = Remedial Design, RA = Remedial
Construction, PC = Post Construction, RM = Removal
Action, BD = Before Dredge, AD = After Dredge, BR =
Brown Fields, SP = Special Project); P# is the phase; For
example, if sampling was performed for a Phase 1 Post
Construction site, the task code would be PC-PL
Valid Values
In Appendix
Table A- 15
No
No
3.5 Geology EDD File - Optional
The Geology 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.BasicGEO vl.txt (or .csv).
Basic Manual for Electronic Data
Version 1.3
27
USEPA Region 2
March 2009
-------
Table 3-6. Geology file data structure
Pos#
1
2
3
4
5
6
Column Name
sys_loc_code
start_depth
material_type
geo_unit_code_l
geo_unit_code_2
remarks
Data Type
Text (20)
Number
w/precision
up to 15
Text(40)
Text (20)
Text (20)
Text (255)
Required
Required
Required
If applicable
Required
If available
If needed
Description
Sample location ID, such as MW-01. Must be the same
sys_loc_code as reported in the Location EDD file.
Start depth of the geologic unit in feet below ground
surface.
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.
The data provider's 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.
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.
General remarks concerning the lithologic or geologic
unit(s).
Valid Values
In Appendix
Basic Manual for Electronic Data
Version 1.3
28
USEPA Region 2
March 2009
-------
3.6 Extraction - Injection Well 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 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 EPAR2EIW-vl format. Each Extraction-Injection Well EDD file must be named according to the
following convention:
SiteNameDate.EPAIDCode.EPAR2EIW_vl.txt (or .csv)
Pos#
1
2
3
4
5
Column Name
sys_loc_code
start_measure_date
end_measure_date
avg_pump_rate
pump_rate_unit
Data Type
Text(20)
DateTime
DateTime
Number
Text(15)
Required
Required
Required
Required
Required
Required
Description
Well installation location. Must be a valid code for the
facility and must match one of the reported values in the
sys_loc_code field of the location EDD file (Table 3-2)
submitted in the current or previous EDD.
Date that the pumping rate measurements began..
Date that the pumping rate measurements concluded.
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)
Unit of measure for the pumping rate.
Valid Values
In Appendix
No
MM/DD/YYYY
HH:MM:SS format
MM/DD/YYYY
HH:MM:SS
format.
No
Table A-18
Basic Manual for Electronic Data
Version 1.3
29
USEPA Region 2
March 2009
-------
Pos#
6
7
8
9
10
11
12
Column Name
pct_operating_time
operating_mode
design_rate
design_rate_unit
rate_measurement_type
suction
remark
Data Type
Text(3)
Text(13)
Text(14)
Text(14)
Text(14)
Text(14)
Text(255)
Required
If Available
Required
Required
Required
If available
If available
If available
Description
Percentage of the measurement time interval during
which the well was operating. Use a value from 0 to 100
(do not include the percent symbol ,"%").
Mode in which well was operating during the reported
interval. Select from the followoing valid values:
EXTRACTION, INJECTION, RECIRCULATION,
PULSE, DEVEL, UNUSE.
Pumping rate as specified in the approved remedial
design report for fully capturing site groundwater
contamination.
Unit of measure for the design pumping rate.
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).
Vacuum in well (e.g., wellpoint vacuum) or well casing
(e.g., vacuum well), reported in equivalent feet of water.
Remarks regarding the pumping rate measurements.
Valid Values
In Appendix
No
No
No
Table A-18
Totalizer
Manifold
Estimate
Average
No
No
Basic Manual for Electronic Data
Version 1.3
30
USEPA Region 2
March 2009
-------
Attachment 1
EXAMPLES OF EDD FILES
Basic Manual for Electronic Data -j i USEPA Region 2
Version 1.3 March 2009
-------
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
site code
01
facility id
FAC 123456723
site name
Example Site
site task code
site descl
site desc2
contact name
John Smith
address 1
23 Main Street
Additional
Fields
email address
abc@abd.com
Figure 2. Example of Location File Ready for Conversion to Text File
Location (LOG) File:
sys loc code
MW01
SB-01
MW03
MW04
sys well id
MW01
NONE
MW03
MW04
Primary
site code
01
01
01
01
Longitude
414456.78
414709.23
414601.23
414601.23
Latitude
4424543.21
4424304.12
4424700.33
4424700.33
surf elev
120.2
126.3
130.1
130.1
coord sys desc
UTMZonel7
UTMZonel7
UTMZonel7
UTMZonel7
Loc name
Lagoon
Landfill
landfill
Loc desc
Shallow
well
Deep well
Loc type
MW
Soilbore
MW
MW
Loc purpo
se
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 1.3
32
USEPA Region 2
March 2009
-------
Figure 3. Example of Chemistry Result File Ready for Conversion to Text File
sys_sample_
code
MW01040198
MW02040198
MW02040198
Sys_loc
_code
MW-01
MW-03
MW-03
sample_
name
sample_
matrix_
code
WG
WG
WG
sample_
type_
code
N
N
N
sample_
source
Field
Field
Field
parent_samp
le_code
sample_
date
04/01/1998
04/01/1998
04/01/1998
Start_
depth
10
End_
depth
12
Depth
unit
Ft
Composite
y/n
N
N
lab_anl_
method_
name
SW8240
SW8240
SW8240
Analysis
date
04/02/1998
04/02/1998
04/02/1998
Total or
disolved
D
D
D
Figure 3. Example of Chemistry Result File Ready for Conversion to Text File (continued)
test_
type
Initial
Initial
Reanalysis
Lab
Matrix
code
WG
WG
WG
analysis
location
LB
LB
LB
Additional
Fields
Additional
Fields
Cas rn
71-43-2
108-88-3
1330-20-7
Chemical
name
BENZENE
TOLUENE
XYLENES
Result
value
23.20
Result
type
code
TRG
TRG
TRG
reportable
result
Yes
Yes
Yes
Detect
flag
Y
N
N
Addition
td
Fields
reporting
detection
limit
5
100
10
Additional
Fields
Figure 4. Example of Water Level File Ready for Conversion to Text File
sys_loc_code
MW01
MW02
sys_well_id
MW01
MW02
measurement
_date
05/10/1999
05/10/1999
measurement
_time
13:10
13:45
ref_elev
120.2
123.1
water_level_depth
31.1
34.1
water_level_elev
89.1
89.0
Additional
Fields
remark
Figure 5. Example of Extraction - Injection Well File Ready for Conversion to Text File
sys_loc
_code
EX-01
EX-02
sys_well
_code
EX-01
EX-02
Start
measurement
date
05/12/2000
11/12/2000
Start
measurement _time
11:23
12:00
end measure
_date
06/12/2000
12/12/2000
end measure
_time
11:30
13:10
avgjjump rate
2.5
1.75
pump rate unit
mgd
mgd
Figure 6. Example of Geology File Ready for Conversion to Text File
Additional
Fields
remark
Basic Manual for Electronic Data
Version 1.3
33
USEPA Region 2
March 2009
-------
sys loc code
MW-03
MW-03
MW-03
SB-01
start depth
0
10
23
0
material type
CL
SW
SP
ML
geo unit 1
Glacial
Outwash
Outwash
Alluvial
geo unit 2
AquiferO
Aquifierl
Aquifer2
AquiferO
Remark
Basic Manual for Electronic Data
Version 1.3
34
USEPA Region 2
March 2009
------- |