Key
Required
Lookup
Lookup And Required
Format Name: NYSDEC
Format Version: 2.02.36
Field Name Data Type Key Required Default Parent Lookup
data_provider_code Text(20) PK Y
data_provider Text(70) Y
data_contact_name Text(50) Y
data_contact_address1 Text(40) Y
data_contact_address2 Text(40)
data_contact_city Text(30) Y
data_contact_state Text(2) Y rt_state.state_code
data_contact_zipcode Text(30) Y
data_contact_country Text(50)
data_contact_phone Text(20) Y
data_contact_email Text(100)
Comment
Data Provider company code. This code is assigned by DEC. Received by email. Eaxmple: GH
Data provider company name. Example: G&H Environmental
Name of contact person. Format: First Name Last Name. Example: John Smith
Contact mailing address. (street or box number). Example: 123 Main Street
Contact mailing address. (if second line is required)
Contact city. Example: Albany
Contact state abbreviation. Example: NY
Contact zip code. Example: 12207
Contact country. Example: USA
Contact phone number. Example: 518-434-4546
Contact email address. Example: jsmith@email.com
Checks
Field Name Data Type Key Required Default Parent Lookup
subfacility_code Text(20) PK Y
subfacility_type Text(20) rt_subfacility_type.subfacility_type
subfacility_name Text(60) Y
subfacility_task_code Text(20)
subfacility_desc1 Text(255)
subfacility_desc2 Text(255)
contact_name Text(50)
address1 Text(40)
address2 Text(40)
city Text(30)
state Text(2) rt_state.state_code
zipcode Text(10)
phone_number Text(30)
alt_phone_number Text(30)
fax_number Text(30)
email_address Text(100)
Comment
Code indicating the subfacility operable unit (OU) for which the data is collected or area of
concern (AOC). Use „01‟ unless there is a second or third operable unit at facility. Code of '02'
and '03' should be used for second and third unit, respectively.
Subfacility type: BASIN, BLDG, OU or SWMU.
Name of project. Example: Off-site Investigation. Use "Remedial Program" unless NYSDEC PM
directs otherwise.
Code used to identify the task under which the subfacility or area is investigated. Field samples
are formally associated with task codes. Example: SC= Site Characterization; RD=Remedial
Design; RIFS=Remedial Investigation/Feasibility Study; RC=Remedial Construction; IRM=Interim
Remedial Measure; SM=Operations & Maintenance Phase
A brief description of the subfacility
Subfacility description, part two (if needed).
The name of the person responsible for the subfacility
Subfacility mailing address. (street or box number). Example: 123 Main Street
Subfacility mailing address. (if second line is required)
Subfacility city. Example: Albany
Subfacility state abbreviation. Example: NY
Subfacility zip code. Example: 12207
Contact phone number. Example: 518-434-4546
Alternative subfacility contact phone number.
Subfacility contact fax number. Example: 518-434-4546
Subfacility contact email address. Example: jsmith@email.com
Checks
Field Name Data Type Key Required Default Parent
data_provider Text(20) Y
sys_loc_code Text(20) PK Y
x_coord Numeric Y
y_coord Numeric Y
surf_elev Numeric Y
elev_unit Text(2) Y
coord_sys_desc Text(20) Y
observation_date DateTime
alt_x_coord Text(20)
alt_y_coord Text(20)
alt_coord_type_code Text(20)
identifier Text(20)
horz_collect_method_code Text(3) Y
horz_accuracy_value Text(20) Y
horz_accuracy_unit Text(15) Y
horz_datum_code Text(3) Y
elev_collect_method_code Text(3)
elev_accuracy_value Text(20)
elev_accuracy_unit Text(15)
elev_datum_code Text(3)
source_scale Text(2)
subcontractor_name_code Text(20)
verification_code Text(1)
reference_point Text(2)
loc_name Text(40)
loc_desc Text(255)
loc_type Text(20)
loc_purpose Text(20)
subfacility_code Text(20) Y Subfacility_v1.subfacility_code
within_facility_yn Text(1) Y
loc_county_code Text(20)
DEC_region Text(20)
loc_state_code Text(2)
loc_major_basin Text(8)
loc_minor_basin Text(20)
remark Text(255)
NYS_drainage_basin_code Text(2)
Lookup
rt_company.company_code
(Enumeration: elev_unit)
(Enumeration: coord_sys_desc)
(Enumeration: coord_type_code)
(Enumeration: identifier)
rt_coord_horz_method.horz_collect_method_code
(Enumeration: horz_accuracy_unit)
rt_coord_horz_datum.horz_datum_code
rt_coord_elev_method.elev_collect_method_code
(Enumeration: elev_accuracy_unit)
rt_coord_elev_datum.elev_datum_code
(Enumeration: source_scale)
rt_company.company_code
(Enumeration: reference_point)
rt_location_type.location_type_code
(Enumeration: yes_no_values)
rt_county.county_code
rt_state.state_code
rt_basin.basin_code
Comment
Must be the valid code for the data provider for this subfacility and match the data_provider field
of the DataProvider_v1 EDD file submitted in the current or previous EDDs.
Location identifier of sample collection, soil boring, or well installation. Use sample location ID.
Must be unique for each OU or AOC. Example: MW-01, A-1, SB6, etc. Additional informaiton is
provided in the EDD Manual.
Longitude of sampling location in decimal degrees. Must be negative for western hemisphere (-
ddd.xxxxxx). Must contain a minimum of 6 six significant figures. Example: -73.740476
Latitude of sampling location in decimal degrees (dd.xxxxxx). Must contain a minimum of 6 six
significant figures. Example: 43.020295
Elevation of the ground surface, or if location is for surface water samples, water surface
elevation. If unknown use "0".
Unit of measurement for elevations. Units must be in feet.
Sampling location coordinate system description. Must be Latitude and Longitude based on World
Geodetic System 1984 (WGS84) datum. Valid Value is: Lat/Long.
Date observation or site survey was made.
x-Coordinate in alternate system.
y-Coordinate in alternate system.
Must reference alternate coordinate system type code. SP designates State Plane.
Leave Null.
Method used to determine latitude/longitude. Example: S1 is for NYS Licensed Professional Land
Survey.
Accuracy range (+/-) of the latitude and longitude. Use "0.1" for professional survey, "100" for
site centroid, or "10" for all other methods.
Unit of the horizontal accuracy. Use "5" for feet.
This is the reference datum for the original survey coordinates. Example: If the latitude and
longitude were calculated from a NAD83 survey, the code would be "002". If the coordinates are
directly from a GPS survey, enter "003" for WGS84.
Method used to determine ground elevation of the sampling location. Example: S1 is for NYS
Licensed Professional Land Survey.
Accuracy range (+/-) of the ground elevation. Use "0.1" for professional survey, "1" for all other
methods.
Unit of the elevation accuracy. Use "5" for feet.
Reference datum for the elevation measurement. Must use valid value from elev_datum code
from the valid_values table. Example: If the elevation references mean sea level, the code is
"003".
Leave this field null.
Code used to distinguish subcontractor name.
Leave this field null.
Leave this field null.
Leave this field null.
Sampling location Description. Example: 50 feet northwest of dog pen.
Sampling location type. Use codes in loc_type valid values table. Example: For a monitoring well
the code is "MW".
Sampling location purpose. Example: Staining observed on soil.
Must be the valid code for this subfacility and match the subfacility_code field in the
Subfacility_v1 EDD file submitted in the current or previous EDD.
Indicates whether this sampling location is within facility boundaries, 'Y' for yes or 'N' for no.
Location county code is found within the Valid Values Table.
Location district code; controlled vocabulary using FIPS codes.
Location state code; controlled vocabulary using FIPS codes.
Location major basin; controlled vocabulary using HUC (Hydrologic Unit Codes). The first 8 digits
of the HUC code should be entered here. Example: The sample location is located within the
Black River Basin the HUC Code is "04150101"
Location minor basin; controlled vocabulary using HUC codes. Any digits after the 8th (first 8 are
reported in loc_major_basin) should be reported here.
Location specific comment.
NYS Drainage Basin Code. Basin Codes can be found at http://www.dec.ny.gov/lands/56800.html
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y Location_v1.sys_loc_code
drill_event Text(20) PK Y
start_depth Numeric
end_depth Numeric
drill_date DateTime
diameter Numeric
diameter_unit Text(15)
drill_method Text(50)
fluid Text(50)
viscosity Text(50)
hammer_wt Text(50)
hammer_fall Text(50)
lift_mechanism Text(50)
new_yn Text(1)
repair_yn Text(1)
deepen_yn Text(1)
abandon_yn Text(1)
replace_yn Text(1)
public_yn Text(1)
purpose Text(70)
Lookup
rt_unit.unit_code
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Use month and year the drilling event started. Use the start month for events that take longer
than a month.
The start depth, in feet below ground surface, of the drilling.
End depth, in feet below ground surface of the drilling.
Date drilling began.
Diameter of boring.
Use values from Unit valid value table. Unit of measure for diameter.
Method used to drill boring. Example: Rotary Mud.
Description of fluid used during drilling. Example: Bentonite
Viscosity of drilling fluid.
Weight of hammer, in pounds, used for sampling.
Distance of hammer fall during sampling in inches.
Type of mechanism used to lift hammer. Example: Hydraulic
Is this a new boring? 'Y' for yes or 'N' for no.
Is this drilling event to repair an existing boring? 'Y' for yes or 'N' for no.
Is this drilling event to deepen an existing boring? 'Y' for yes or 'N' for no.
Has the boring been abandoned? 'Y' for yes or 'N' for no.
Is this boring event to replace an existing boring? 'Y' for yes or “N” for no.
Is well being install for a public use? ? 'Y' for yes or 'N' for no.
Describe the purpose of the boring event. Example: Installation of new monitorings for RI.
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y Location_v1.sys_loc_code
start_depth Numeric PK Y
material_type Text(40)
geo_unit_code_1 Text(20)
geo_unit_code_2 Text(20)
remark1 Text(255)
remark2 Text(255)
moisture Text(1)
permeable Text(20)
consolidated_yn Text(1)
color Text(30)
observation Text(255)
consistency Text(20)
sorting Text(20)
grainsize Text(20)
odor Text(20)
Lookup
rt_material.material_name
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
(Enumeration: sorting)
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
The start depth, in feet below ground surface, of the lithologic unit.
The type of material that composes the lithologic unit. Material Type listed in Valid Values Table.
The data providers interpretation of the hydrogeologic unit present at this lithologic unit.
Example: Upper Aquifer, Lower Aquifer, Magothy Aquifer, Upper Confined Aquifer, Glacial Aquifer,
etc.
Alternate geologic unit grouping. This can be a sub-classification of geologic_unit_code_1 or a
layer used for groundwater flow/transport computer modelling that contains the lithologic unit.
Comment on the lithologic unit.
Comment on the geologic unit.
Was any moisture detected within the lithologic unit? 'Y' for yes or 'N' for no.
Description of the permeability of the lithologic unit. Example: impervious, semi, pervious, or
very.
Was lithologic unit consolidated? 'Y' for yes or 'N' for no.
Color of the lithologic unit. Example: light brown
General field observations of the lithologic unit. Example: running sand
Description of the consistency of the soil Example:very soft, soft, firm, hard or very hard.
Geologic description of the grain size distribution of the lithologic unit. Use 'poor' for soil with a
wide range of particle sizes or 'well' for soil with a narrow range of particle sizes.
Description of grain size.
Description of odor from the soil.
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y Location_v1.sys_loc_code
well_id Text(30)
well_description Text(30)
well_owner Text(30)
well_purpose Text(20)
well_status Text(20)
top_casing_elev Numeric
datum_value Numeric Y
datum_unit Text(15) Y
datum_desc Text(70) Y
step_or_linear Text(6)
datum_start_date DateTime Y
datum_collection_method_code Text(2)
depth_of_well Numeric
depth_unit Text(15)
depth_to_bedrock Numeric
depth_measure_method Text(20)
stickup_height Text(8)
stickup_unit Text(15)
sump_length Text(20)
sump_unit Text(15)
installation_date DateTime
construct_start_date DateTime
construct_complete_date DateTime
construct_contractor Text(20)
pump_type Text(20)
pump_capacity Text(6)
pump_unit Text(15)
pump_yield Text(6)
pump_yield_method Text(20)
weep_hole Text(1)
head_configuration Text(50)
access_port_yn Text(1)
casing_joint_type Text(50)
perforator_used Text(50)
intake_depth Numeric
disinfected_yn Text(1)
historical_reference_elev Numeric
geologic_unit_code Text(20)
remark Text(255)
Lookup
rt_unit.unit_code
(Enumeration: step_or_linear)
rt_coord_elev_method.elev_collect_method_code
rt_unit.unit_code
rt_unit.unit_code
rt_unit.unit_code
rt_company.company_code
rt_unit.unit_code
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Used to track well id (if different from sys_loc_code). Example: CDM-MW-1
Used for additional well description if necessary. Example: Located in right-of-way in front of
town hall.
Name of entity that owns the well. Example: ACME Associates.
Purpose of well. Example: Installed to track downgradient plume.
Current status of well. Example: Active, abandoned, destroyed, etc.
Elevation of the top of well casing. Elevation must be in feet.
Datum elevation used for meausureing water levels. Elevation must be in feet. Typically this is
the elevation of top of casing.
Unit of measure for the well datum. Must be feet.
Description of the datum. Example: Top of well casing.
Leave this field null.
Date that current datum was first recorded in MM/DD/YYYY format.
Method used to determine the water level datum elevation. Use codes in
rt_coord_elev_method.elev_collect_method_code valid values table.
Depth below ground surface of the well bottom. Must be in feet.
Unit of measure for the well datum. Must be feet.
Depth below ground surface of bedrock. Must be in feet.
Method of measuring depth of well. Example: Tape down.
Height of well casing above ground surface. Must be in feet.
Unit of measure for height of well casing above ground surface. Must be feet.
Length of sump constructed in well. Must be feet.
Unit of measure for the well sump length. Must be feet.
Date of well installation in MM/DD/YYYY format.
Date well construction began in MM/DD/YYYY format.
Date well construction was completed in MM/DD/YYYY format.
Code used to distinguish subcontractor name.
Type of pump used at well. Example: centrifugal, propeller, jet, helical, rotary, etc.
Pump Rate Capacity: Example: 10.
Unit of measure for the pump capacity and yield. Use code from rt_unit.unit_code valid value
table.
Actual pumping rate. Example: 10 gpm
Method used for pump yield. Example: Flow meter.
Is there a weep hole? 'Y' for yes or 'N' for no.
Description of the well head. Example: man-hole entry well vault.
Is there an access port? '“Y' for yes or 'N' for no.
Type of casing joint. Example: threaded, flush, or solvent welded.
Description of well perforation. Example: slotted, drilled, or wound.
Depth below ground surface of the well intake. Must be in feet.
Was well disinfected? 'Y' for yes or 'N' for no.
Historical reference value. Used for the elevation of past reference points. Elevation must be in
feet. Do not use to reference current elevation.
Geologic unit in which the well intake is installed. Use established USGS rock unit codes as
applicable.
Available for general remarks.
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y Well_v1.sys_loc_code
Location_v1.sys_loc_code
segment_type Text(20) PK Y
material_type_code Text(20) PK Y
start_depth Numeric PK Y
end_depth Numeric Y
depth_unit Text(15) Y
inner_diameter Numeric
outer_diameter Numeric
diameter_unit Text(15)
thickness Numeric
thickness_unit Text(15)
slot_type Text(20)
slot_size Numeric
slot_size_unit Text(15)
perf_length Numeric
screen_type Text(15)
material_quantity Text(20)
material_density Text(20)
remark Text(255)
Lookup
rt_well_segment_type.segment_type
rt_well_segment_type.material_type_code
rt_unit.unit_code
rt_unit.unit_code
rt_unit.unit_code
rt_unit.unit_code
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
This field is used to describe an individual section of the well, such as filter pack. A new record is
generated for each section of the well construction. Use Segment Types codes listed in
rt_well_segment_type.segment_type valid values table.
This field is used to describe the material used in an individual section of the well, such as Sand
Pack. A new record is generated for each section of the well construction. Use material type
codes listed in rt_well_segment_type.materials_type valid values table.
Depth below ground surface of the top of the section. Must be in feet.
Depth below ground surface of the bottom of the section. Must be in feet.
The unit of depth measurements. Units must be feet.
The inside diameter of section.
The outside diameter of the section.
The unit of measurement for diameter. Use codes in rt_unit.unit_code valid value table.
Leave this field null.
Leave this field null.
Enter type of well screen slots. Example: bridge, shutter, and continuous.
Width of slots.
The unit of measurement for slot size. Use codes in rt_unit.unit_code valid value table.
Length of perforated portion of screen. Must be in feet.
Type of screen. Example: Slotted, micro-perforated, etc.
Quantity of annular seal or fill material used. Must be in pounds.
Density of the annular seal material in lbs/ft3.
Remarks regarding the segment. Example: Encountered running sands, needed to use micro-
perforated screen.
Checks
Field Name Data Type Key Required Default Parent Lookup
sys_loc_code Text(20) Y
geo_sample_code Text(40) PK Y
sample_name Text(50)
sample_top Numeric Y
sample_bottom Numeric Y
sample_date DateTime
sample_method Text(30)
material_type Text(40) rt_material.material_name
sample_desc Text(255)
geologic_unit_code Text(20)
liquid_limit Numeric
plastic_limit Numeric
shrinkage_limit Numeric
flow_index Numeric
plasticity_index Numeric
activity Numeric
e Numeric
e_max Numeric
e_min Numeric
n Numeric
specific_gravity Numeric
w Numeric
opt_w Numeric
s Numeric
K Numeric
K_unit Text(15) rt_unit.unit_code
unit_wt Numeric
sat_unit_wt Numeric
dry_unit_wt Numeric
dry_unit_wt_max Numeric
dry_unit_wt_min Numeric
density_unit Text(15) rt_unit.unit_code
rel_density Numeric
rel_compaction Numeric
consistency Text(20)
organic_carbon Numeric
organic_carbon_unit Text(15) rt_unit.unit_code
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Unique sample identifier used only for geology section. Combine sys_loc_code with sample depth
to create identifier. Example: MW-01-2ft-4ft
Use to provide a name or description of sample. Does not have to be a unique throughout
database.
Depth to top of sample below ground surface. Must be in feet.
Depth to bottom of sample below ground surface. Must be in feet.
Date and time sample was collected in 'MM/DD/YYYY HH:MM:SS' format.
Method used to obtain sample. Example: Hand Auger
Soil or rock type geologic sample. Use codes in rt_material.material_name valid value table.
General description of the sample or sampling activities. Example: Delineation of Surface Soil
Contamination.
Geologic unit sample collected from. Use established USGS rock unit codes or NRCS soil codes as
applicable.
Liquid limit of sample.
Plastic limit of sample.
Shrinkage limit of sample.
Flow index of sample.
Plasticity index of sample.
Atterberg activity of sample.
Void ratio of sample.
Maximum void ratio of sample.
Minimum void ratio of sample.
Porosity of sample.
Specific gravity of sample.
Water content of sample in decimal percentage.
Optimum water content.
Degree of saturation of the sample in decimal percentage.
Hydraulic conductivity of sample.
Unit of measure for K. Use code from rt_unit.unit_code valid value table.
Unit weight of sample. All unit weights for one sample must be reported in a consistent unit of
measurement.
Saturated unit weight. All unit weights for one sample must be reported in a consistent unit of
measurement.
Dry unit weight. All unit weights for one sample must be reported in a consistent unit of
measurement.
Maximum dry unit weight. All unit weights for one sample must be reported in a consistent unit
of measurement.
Minimum dry unit weight. All unit weights for one sample must be reported in a consistent unit
of measurement.
Unit of measure for all reported densities of the sample. Use code from rt_unit.unit_code valid
value table.
Relative density of sample in decimal percentage.
Relative compaction of sample in decimal percentage.
Description of the consistency of the soil sample. Example: very soft, soft, firm, hard, very hard,
etc.
Organic carbon content of sample.
Unit of measurement of organic content. Use code from rt_unit.unit_code valid value table.
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y Location_v1.sys_loc_code
type Text(20) PK Y
sequence Text(20) PK Y
depth Numeric Y
flowing_yn Text(1)
measurement_method Text(50)
capped_pressure Numeric
capped_pressure_unit Text(15)
reference_point Text(50)
reference_elevation Numeric Y
temperature Numeric
temperature_unit Text(15)
Lookup
(Enumeration: sequence)
(Enumeration: yes_no_values)
rt_unit.unit_code
rt_unit.unit_code
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Aquifer designation. Example: unconfined1, confined1, confined2, upper, lower, etc.
Designation of water level conditions at time of measurement. Input "Stabilized" for stablized
water conditions or "Unstablized" for unstablized conditions.
Depth of water table below reference point. Must be in feet.
Is the water table flowing? 'Y' for yes or 'N' for no.
Method of measuring water table depth. Example: Water level probe.
Hydrostatic pressure of confined aquifer.
Unit of measure for confined aquifer. Use code from rt_unit.unit_code valid value table.
Description of reference point from which depth were taken. Example: Top of casing.
Elevation of the reference point from which depth measurements were taken. Elevation must be
in feet.
Temperature of water in the water table.
Unit of temperature. Use code from rt_unit.unit_code valid value table.
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y Location_v1.sys_loc_code
depth Numeric PK Y
param Text(20) PK Y
param_value Numeric Y
param_unit Text(15) Y
Lookup
rt_downhole_point_param_type.param
rt_unit.unit_code
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Depth of measurement below ground surface. Must be in feet.
The parameter being measured. Example: tip stress, resistivity, pore pressure, etc. Use code
from rt_downhole_point_param_type.param valid value table.
The measured value of the parameter.
The unit of the measured value. Use code from rt_unit.unit_code valid value table.
Checks
Field Name Data Type Key Required Default Parent Lookup
sys_loc_code Text(20) PK Y
survey_date DateTime PK Y
param_code Text(20) PK Y rt_soil_gas_param_type.param_code
reading_depth Text(8)
reading_unit Text(15) rt_unit.unit_code
reading Text(8)
depth_unit Text(15) rt_unit.unit_code
sampling_method Text(10)
instrument_type Text(15)
east Text(14)
north Text(14)
secondary_east Text(14)
secondary_north Text(14)
lithology_code Text(10)
area_desc Text(70)
equipment_code Text(60)
borehole_drill_method Text(10)
technician Text(50)
remark Text(255)
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Sample survey date in mm/dd/yyyy hh:mm.
Parameter measured by soil gas survey. Use code from rt_soil_gas_param_type.param_code valid
values table.
Depth of soil gas survey measurement below ground surface. Must be in feet.
Unit of measure of soil gas survey measurement. Use code from rt_unit.unit_code valid value
table.
Leave this field null.
Leave this field null.
Sampling method. Example: Summa Canister
Leave this field null.
Leave this field null.
Leave this field null.
Leave this field null.
Leave this field null.
Lithology code. Example: fine sand.
Description of area. Example: Grassy Area behind building.
Leave this field null.
Drilling method. Example: Direct Push
Technician. Example: J. Smith
Remark: Neighbor mowing lawn.
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y Well_v1.sys_loc_code
Location_v1.sys_loc_code
measurement_date DateTime PK Y
historical_reference_elev Numeric Y
water_level_depth Numeric Y
water_level_elev Numeric
corrected_depth Numeric
corrected_elev Numeric
measured_depth_of_well Numeric
depth_unit Text(15)
technician Text(30)
dry_indicator_yn Text(1)
measurement_method Text(20)
batch_number Text(10)
dip_or_elevation Text(10)
remark Text(255)
Lnapl_cas_rn Text(15)
Lnapl_depth Numeric
Dnapl_cas_rn Text(15)
Dnapl_depth Numeric
task_code Text(20)
Lookup
rt_unit.unit_code
(Enumeration: yes_no_values)
(Enumeration: dip_or_elevation)
rt_analyte.cas_rn
rt_analyte.cas_rn
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Date and time of water level measurement in 'MM/DD/YYYY HH:MM' format.
Elevation of the reference point from which depth measurements were taken. For groundwater
elevations, this must match valid reference_elevation code for this location located in the
WaterTable_v1 table. Must be in feet.
Depth of water below reference point. If a well is measured under artesian conditions use
negative number for calculated water level above reference point. For the surface of a water
body or dry water bodies, water level is zero “0”, Must be in feet.
Calculated elevation of water level. Elevation must be in feet.
Depth below reference point of water level after any necessary corrections, e.g., if corrections
were necessary to water_level_depth because free product was encountered. Must be in feet.
Corrected water level elevation. Elevation must be in feet.
The actual measured depth below ground surface to the bottom of the well. Must be in feet.
Must use "Feet" code from rt_unit.unit_code valid value table.
Name of technician measuring water level. Example: J. Smith.
Is the well dry? 'Y' for yes or 'N' for no.
Method used to make water level measurements. Example: water level probe.
Leave this field null
Input 'elevation' if water level measurement is above the datum (i.e., artesian well) or input 'dip'
if water level is below datum.
Remark on measurement.
If LNAPL is found, input primary constituent CAS code. Use code from rt_analyte.cas_rn valid
value table.
Depth to top surface of LNAPL below reference point.
If DNAPL is found, input primary constituent CAS code. Use code from rt_analyte.cas_rn valid
value table.
Depth to top surface of DNAPL below reference point.
Code used to identify the task under which this sampling occured. Example: SC= Site
Characterization; RD=Remedial Design; RIFS=Remedial Investigation/Feasibility Study;
RC=Remedial Construction; IRM=Interim Remedial Measure; SM=Operations & Maintenance
Phase
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y Well_v1.sys_loc_code
Location_v1.sys_loc_code
start_measure_date DateTime PK Y
end_measure_date DateTime Y
ave_pump_rate Numeric Y
pump_rate_unit Text(15) Y
pct_operating_time Numeric
operating_mode Text(20) Y
design_rate Numeric Y
design_rate_unit Text(15) Y
rate_measurement_type Text(20)
suction Numeric
remark Text(255)
Lookup
rt_unit.unit_code
(Enumeration: operating_mode)
rt_unit.unit_code
(Enumeration: rate_measurement_type)
Comment
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Date and time that the pumping measures began in MM/DD/YYYY HH:MM:SS format.
Date and time that the pumping measures concluded in MM/DD/YYYY HH:MM:SS format.
Average pumping rate.
The unit of measure for the pumping rate. Use code from rt_unit.unit_code valid value table.
Percentage of the measurement time interval that the well was operating. 0 - 100 (no %).
Mode in which well was operating during the reported interval. Example: Extraction, injection,
recirculation, pulse, devel, or unuse.
Pumping rate specified in the remedial design to fully capture site's contamination.
Unit of measure for the design pumping rate. Use code from rt_unit.unit_code valid value table.
Type of measurement used for averaging. Example: Totalizer, Manifold, Estimate. For details
see EDD Manual.
leave this field null.
Remarks regarding the pumping rate measurements. Example: Well down for three weeks due
to repairs.
Checks
Field Name Data Type Key Required Default Parent
data_provider Text(20) Y
sys_loc_code Text(20) PK Y
sys_sample_code Text(255) PK Y
field_parameter Text(15) PK Y
start_depth Numeric
end_depth Numeric
depth_unit Text(2)
result_date Date PK Y
result_time Text(8) PK
result_value Text(14) Y
result_unit Text(15) Y
quantitation_limit Text(20)
task_code Text(20)
sample_matrix_code Text(20) Y
qualifier Text(20)
sampling_company_code Text(20)
sampling_reason Text(40)
sampling_method Text(40)
reportable_result Text(10) Y Yes
value_type Text(10) Y
remark Text(225)
Lookup
rt_company.company_code
rt_analyte.cas_rn
(Enumeration: depth_unit)
rt_unit.unit_code
rt_matrix.matrix_code
rt_qualifier.qualifier
rt_company.company_code
rt_sample_method.method_code
(Enumeration: reportable_result)
(Enumeration: value_type)
Comment
Must be a valid data_provider code. Use code from the rt_company.company_code valid value
table.
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Unique Sample identifier of the sample that was tested and analyzed. Must match the associated
sys_sample_code field of the Sample file submitted in the current or previous EDD.
Field parameter CAS number. Use code from rt_analyte.cas_rn valid value table. Example: The
code for oxidation-reduction potential is ORP.
Sample start depth below ground surface. Must be in feet.
Sample end depth below ground surface. Must be in feet.
Sample depth unit. Must choose "ft"
Result date/time (mm/dd/yr hh:mm:ss).
Time result was collected. Format hh:mm
Qualitative or Quantitative parameter result. Example: For the field parameter Color, "Red" could
be entered.
Result unit. Use code from rt_unit.unit_code valid value table.
Quantitation limit
Code used to identify the task under which this sampling occured. Example: SC= Site
Characterization; RD=Remedial Design; RIFS=Remedial Investigation/Feasibility Study;
RC=Remedial Construction; IRM=Interim Remedial Measure; SM=Operations & Maintenance
Phase
Sample matrix code. Use code from rt_matrix.matrix_code valid value table.
Field Parameter Qualifer. Use code from rt_qualifier.qualifier valid value table. NOTE: At this
time this field should limited to no more than two qualifers.
Code used to distinguish subcontractor name.
Sampling reason. Example: 3rdQ sampling event
Field sampling methodology. Use code from rt_sample_method.method_code valid value table.
Is this a reportable result? "yes"or "no".
How value was derived, actual, calculated, or estimated.
Remarks regarding field parameter collected. Example: Collected near oil stain.
Checks
Field Name Data Type Key Required Default Parent Lookup
building_code Text(20) PK Y
building_name Text(60) Y
subfacility_code Text(20) Y
contact_name Text(50)
address1 Text(40)
address2 Text(40)
city Text(30)
state Text(2) rt_state.state_code
zip_code Text(10)
county Text(50) rt_county.county_code
phone_number Text(30)
alt_phone_number Text(30)
fax_number Text(30)
email_address Text(100)
remark Text(2000)
Comment
Unique code that identifies the building within the facility (i.e. B001, B002, etc.) For additional
information, please refer to the EDD Manual.
Soil Vapor Intrusion Program Phase. Example: Off-site SVI investigation. Use "SVI Investigation"
unless otherwise directed by NYSDEC PM.
Operable Unit which the building is associated with for this subfacility and match the code in the
Subfacility_v1 EDD file submitted in the current or previous EDDs.
Building Contact Name: Example: J. Smith
Building Street Address Line 1 Example: 123 Main Street
Building Street Address Line 2
Building city. Example: Albany
Building state. Use code from rt_state.state_code valid value table. Example: NY
Building zipcode. Example: 12207
Building county. Use code from rt_county.county_code valid values table. Example: Albany
Building contact phone number. Example: 518-434-4546
Alternative site phone number.
Building contact fax number. Example: 518-434-4546
Building contact email address. Example: jsmith@email.com
Remarks regarding building
Checks
Field Name Data Type Key Required Default Parent
building_code Text(20) PK Y
building_name Text(255) Y
building_type Text(20)
building_size Text(20)
num_floors Numeric
construct_year Numeric
foundation_depth Numeric
foundation_depth_unit Text(15)
foundation_type Text(20)
foundation_wall_material Text(20)
foundation_floor_material Text(20)
foundation_wall_thickness Numeric
foundation_floor_thickness Numeric
foundation_thickness_unit Text(15)
attached_garage_yn Text(1)
radon_mitigation_yn Text(1)
heat_fuel_type Text(255)
heat_system_type Text(255)
central_air_yn Text(1)
sump_yn Text(1)
voc_mitigation_yn Text(1)
remark Text(2000)
custom_field_1 Text(255)
custom_field_2 Text(255)
custom_field_3 Text(255)
custom_field_4 Text(255)
custom_field_5 Text(255)
Lookup
rt_building_type.building_type
(Enumeration: building_size)
(Enumeration: ft_m_units)
rt_foundation_type.foundation_type
rt_material.material_name
rt_material.material_name
(Enumeration: ft_m_units)
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
(Enumeration: heat_fuel_type)
(Enumeration: heat_system_type)
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
Comment
Must be a valid building_code and match the building_code field in the VI_Bldg_Address EDD file
submitted in the current or previous EDDs.
Building name Example: Denison Medical Building
Type of building. Use code from rt_building_type.building_type valid value table. Example:
Residential, Industrial, etc.
Size of building. Input, "Small" , "Medium", or "Large"
Input number of floors in the building
Input year of construction
Input foundation depth below ground surface. Must be feet.
Unit of measurement for Foundation depth. Input "FT" for feet.
Foundation type. Example: Basement, crawlspace, ect.
Foundation wall material. Use code from rt_material.material_name valid value. Example: Poured
Concrete
Foundation floor material. Use code from rt_material.material_name valid value. Example: Poured
Concrete
Foundation wall thickness. Must be feet.
Foundation floor thickness. Must be feet.
Foundation thickness units. Must be feet.
Existence of an attached garage (Y/N)?
Existence of radon mitigation system (Y/N)?
Type of heating fuels. Example: Natural gas
Type of heating system. Example: Forced hot air
Existence of central air system (Y/N)?
Existence of sump pump (Y/N)?
Existence of VOC mitigation flag (Y/N)?
Building remarks
Leave this field Null
Leave this field Null
Leave this field Null
Leave this field Null
Leave this field Null
Checks
Field Name Data Type Key Required Default Parent Lookup
task_code Text(40) PK Y
param_code Text(20) PK Y rt_task_param_type.param_code
task_desc Text(255)
building_use_type Text(20) rt_building_use_type.building_use_type
measurement_date DateTime
param_value Text(255)
param_unit Text(15) rt_unit.unit_code
remark Text(2000)
Comment
This Table is reserved for future use.
This Table is reserved for future use.
This Table is reserved for future use.
This Table is reserved for future use.
This Table is reserved for future use.
This Table is reserved for future use.
This Table is reserved for future use.
This Table is reserved for future use.
Checks
Field Name Data Type Key Required Default Parent
data_provider Text(20) Y
sys_loc_code Text(20) Y
building_code Text(20) Y VI_Building.building_code
sys_sample_code Text(40) PK Y
sample_matrix_code Text(3) Y AS
task_code Text(40)
sampling_company_code Text(20) Y
sample_start_date DateTime Y
sent_to_lab_date DateTime
chain_of_custody Text(40)
sample_end_date DateTime
sample_duration Text(20)
sample_duration_unit Text(15)
floor_material Text(20)
slab_thickness Text(20)
subfloor_material Text(20)
subfloor_moisture Text(20)
seal_type Text(20)
seal_adequate_yn Text(1)
purge_yn Text(1)
purge_pid Numeric
purge_pid_unit Text(15)
vac_gauge_initial Numeric
vac_gauge_final Numeric
vac_gauge_unit Text(15)
vapor_loc_desc Text(255)
sampling_reason Text(30)
sampling_method Text(40)
sampler Text(50)
remark Text(2000)
Lookup
rt_matrix.matrix_code
rt_unit.unit_code
rt_material.material_name
rt_material.material_name
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
rt_sample_method.method_code
Comment
Must be a valid data_provider code. Use code from the rt_company.company_code valid value
table.
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs.
Must be a valid building_code and match the building_code field in the VI_Bldg_Address EDD file
submitted in the current or previous EDDs.
Unique sample identifier. Each SVI sample must have a unique value, including spikes and
duplicates. You have considerable flexibility in the methods used to derive and assign unique
sample identifiers, but uniqueness throughout the database is the only restriction enforced by
EQuIS®. If no Sample ID exists use sys_loc_code and suffix with date. For Example VI01 +
June 06, 2001= VI0106062001).
Code which distinguishes between different types of sample matrix. Use code from
rt_matrix.matrix_code valid value table. The default value for this field is "AS" for soil vapor.
This field is used to group samples into a sampling event. Until Further notice, leave this field
null.
Name or initials of sampling company.
Date and time sample collection was started. Input in MM/DD/YYYY HH:MM:SS format
Shipping date sample was sent to lab (in MM/DD/YYYY format).
Chain of custody identifier. Note: A single sample may be assigned to only one chain of custody.
Date and time sample collection was completed. Input in MM/DD/YYYY HH:MM:SS format
The sampling duration.
Sample duration units. Use code from rt_unit.unit_code valid value table.
Lowest level floor material at sample location. Use code from rt_material.material_name valid
value table.
Slab thickness at sample location (in inches)
Material found below the foundation floor. Use code from rt_material.material_name valid value
table.
Moisture content at subslab sample location. Example: Dry, Damp, Saturated, etc.
Type of seal used during sampling. Example: Beeswax, Clay, Teflon Tape, etc.
Did the sample probe seal pass the tracer test (Y/N)?
Was the sample equipment purged in accordance with work plan (Y/N)?
Input PID instrument reading
PID instrument reading units. Example: ppbv
Vacuum gauge reading immediately after start
Vacuum gauge reading immediately before end
Vacuum gauge instrument units. Example: inches of water
Soil vapor intrusion location description
Reason for sampling
Sampling method. Example: Summa Cannister
Person taking sample.
Remark
Checks
Field Name Data Type Key Required Default Parent
data_provider Text(20) Y
sys_sample_code Text(40) PK Y
sample_name Text(30)
sample_matrix_code Text(3) Y
sample_type_code Text(2147483647) Y
sample_source Text(10) Y FIELD
parent_sample_code Text(40) Sample_v1.sys_sample_code
sample_delivery_group Text(20)
sample_date DateTime Y
sys_loc_code Text(20) Location_v1.sys_loc_code
start_depth Numeric
end_depth Numeric
depth_unit Text(15)
chain_of_custody Text(15)
sent_to_lab_date DateTime
sample_receipt_date DateTime
sampler Text(30)
sampling_company_code Text(10) Y
sampling_reason Text(30)
sampling_technique Text(40)
task_code Text(20)
collection_quarter Text(5)
composite_yn Text(1) Y N
composite_desc Text(255)
sample_class Text(10)
custom_field_1 Text(20)
custom_field_2 Text(50)
custom_field_3 Text(50)
comment Text(255)
Lookup
rt_company.company_code
rt_matrix.matrix_code
rt_sample_type.sample_type_code
(Enumeration: sample_source)
rt_unit.unit_code
(Enumeration: yes_no_values)
Comment
Must be a valid data_provider code. Use code from the rt_company.company_code valid value
table.
Unique sample identifier. Each sample at a facility must have a unique value, including spikes and
duplicates. You have considerable flexibility in the methods used to derive and assign unique
sample identifiers, but uniqueness throughout the database is the only restriction enforced by
EQuIS®. If no Sample ID exists use sys_loc_code and suffix with date. For Example MW01 +
June 06, 2001= MW0106062001). For trip blanks that do not have unique sample IDs, enter TB
plus the date, e.g., TB + April 5, 2000 =TB04052000.
Additional sample identification information as necessary. Is not required to be unique (i.e.,
duplicates are OK). Can be the same value as in the sys_sample_code field.
Code which distinguishes between different types of sample matrix. Use code from
rt_matrix.matrix_code valid value table. Example: Soil samples are coded "SO", Groundwater
samples are coded "WG", etc.
Code which distinguishes between different types of samples. Use code from
rt_sample_type.sample_type_code valid values table. Example: Normal field samples are coded
“N”, laboratory method blank samples are coded “LB”, etc.
This field identifies where the sample originated. Samples collected in the Field are entered as
“Field”, samples originating in the Lab are entered “LAB”.
If the sample is a duplicate, MS/MSD, blind dup, lab dup, etc, input the parent sample
“sys_sample_code”. Example: A field duplicate "FD" (coded in sample_type_code) is collected
for sample MW0106062001, therefore MW0106062001 is input into this field. This field is left null
for all non-duplicate samples. Additional information may be found in the EDD Manual.
This is the laboratory sample delivery group.
Date and time sample was collected (in MM/DD/YYYY HH:MM:SS format).
Must be a valid sys_loc_ code for this subfacility and match the sys_loc_code field in the
Location_v1 EDD file submitted in the current or previous EDDs. This field is not required for QC
samples.
Depth to top of sample below ground surface. For surface water samples, use depth below water
surface elevation. This field maybe left null for most groundwater samples if the database
contains the start depth of the well screen in the well construction table, otherwise it must be
entered. An exception to this rule is discrete samples taken at various depth elevations from a
single well, start depth must be entered.
Depth to bottom of sample below ground surface. For surface water samples, use depth below
water surface elevation. This field maybe left null for most groundwater samples if the database
contains the start depth of the well screen in the well construction table, otherwise it must be
entered. An exception to this rule is discrete samples taken at various depth elevations from a
single well, end depth must be entered.
Unit of measurement for the sample begin and end depths. Use codes from rt_unit.unit_code
valid value table.
Chain of custody identifier. Note: A single sample may be assigned to only one chain of custody.
Shipping date sample was sent to lab (in MM/DD/YYYY format).
Date that sample was received at laboratory (in MM/DD/YYYY format).
Name or initials of sampler.
Name or initials of sampling company (not controlled vocabulary).
Leave this field null.
Sampling technique. Example: Field filtration, etc.
Code used to identify the task under which the field sample was retrieved. SC= Site
Characterization, RD=Remedial Design, RIFS=Remedial Investigation/Feasibility Study,
RC=Remedial Construction, IRM=Interim Remedial Measure, SM=Operations & Maintenance
Phase
Leave this field null.
Is sample a composite sample? 'Y' for yes or 'N' for no.
Description of composite sample (if composite_yn is 'Yes'). ). Example: Composite sample from
soil stock pile.
Leave this field null.
Leave this field null.
Leave this field null.
Leave this field null.
Comments on sampling
Checks
Field Name Data Type Key Required Default Parent
sys_sample_code Text(40) PK Y Sample_v1.sys_sample_code
lab_anl_method_name Text(35) PK Y
analysis_date DateTime PK Y
total_or_dissolved Text(10) PK Y T
column_number Text(2)
test_type Text(10) PK Y INITIAL
lab_matrix_code Text(3)
analysis_location Text(2) Y FI
basis Text(10) Y NA
container_id Text(30)
dilution_factor Numeric 1.0
prep_method Text(20)
prep_date DateTime
leachate_method Text(15)
leachate_date DateTime
lab_name_code Text(20)
qc_level Text(10) QUANT
lab_sample_id Text(20)
percent_moisture Text(5)
subsample_amount Text(14)
subsample_amount_unit Text(15)
analyst_name Text(30)
instrument_id Text(50)
comment Text(255)
preservative Text(20)
final_volume Numeric
final_volume_unit Text(15)
cas_rn Text(15) PK Y
chemical_name Text(75) Y
result_value Numeric
result_error_delta Text(20)
result_type_code Text(10) Y TRG
reportable_result Text(10) Y Yes
detect_flag Text(2) Y Y
lab_qualifiers Text(10)
validator_qualifiers Text(10)
interpreted_qualifiers Text(10)
validated_yn Text(1) Y N
organic_yn Text(1) Y
method_detection_limit Text(20)
reporting_detection_limit Numeric
quantitation_limit Text(20)
result_unit Text(15)
detection_limit_unit Text(15)
tic_retention_time Text(8)
minimum_detectable_conc Numeric
counting_error Numeric
uncertainty Text(10)
critical_value Numeric
validation_level Text(20)
result_comment Text(255)
qc_original_conc Numeric
qc_spike_added Numeric
qc_spike_measured Numeric
qc_spike_recovery Numeric
qc_dup_original_conc Numeric
qc_dup_spike_added Numeric
qc_dup_spike_measured Numeric
qc_dup_spike_recovery Numeric
qc_rpd Text(8)
qc_spike_lcl Text(8)
qc_spike_ucl Text(8)
qc_rpd_cl Text(8)
qc_spike_status Text(10)
qc_dup_spike_status Text(10)
qc_rpd_status Text(10)
Lookup
rt_analytic_method.analytic_method
(Enumeration: fraction)
rt_test_type.test_type
rt_matrix.matrix_code
(Enumeration: analysis_location)
(Enumeration: basis)
rt_prep_method.prep_method
rt_company.company_code
(Enumeration: qc_level)
rt_unit.unit_code
rt_preservative.preservative
rt_unit.unit_code
rt_analyte.cas_rn
rt_analyte.chemical_name
rt_result_type.result_type_code
(Enumeration: reportable_result)
(Enumeration: detect_flag)
rt_qualifier.qualifier
(Enumeration: yes_no_values)
(Enumeration: yes_no_values)
rt_unit.unit_code
rt_unit.unit_code
(Enumeration: uncertainty)
(Enumeration: spike_status)
(Enumeration: spike_status)
(Enumeration: spike_status)
Comment
Must be a valid sys_sample_code and match the sys_sample_code field in the Sample_v1 EDD file
submitted in the current or previous EDDs.
Laboratory analytical method name or description. Use code from
rt_analytic_method.analytic_method valid values table. Example: SW8260B, E130.1, etc.
Date and time of sample analysis in 'MM/DD/YYYY HH:MM:SS' format. May refer to either
beginning or end of the analysis as required.
Must be either 'D' for dissolved or filtered [metal] concentration, or 'T' for total or 'NA' for not
applicable, or L for leachate extraction from TCLP and SPLP analysis.
Leave this field Null
Type of test. Use code from rt_test_type.test_type valid values. Examples: 'Initial', 'Reextract1',
'Reextract2', 'Reextract3', 'Reanalysis', 'Dilution1', 'Diluton2', and 'Diluton3'.
This code is used to denote the matrix that was analyzed, not the sample matrix received. Use
code from rt_matrix.matrix_code valid value table.
Denotes location of analysis. Must be either 'FI' for field instrument or probe, 'FL' for mobile field
laboratory analysis, or 'LB' for fixed_based laboratory analysis.
Denotes reporting basis. 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.
Leave this field Null
Input effective test dilution factor. Example: 10
Laboratory sample preparation method name or description. Use code from
rt_prep_method.prep_method valid values table. Example: Acid digestion of waters would be
input as "SW3005A".
Beginning date and time of sample preparation in 'MM/DD/YYYY HH:MM:SS' format.
Laboratory leachate generation method name or description. The method name should be
sufficient to reflect operation of the laboratory. Example: pH dependent, percolation, tank,
granular.
Beginning date and time of leachate preparation in 'MM/DD/YYYY HH:MM:SS' format.
Code used to distinguish laboratory name.
Input analysis type. For screening analysis input "SCREEN" ; for quantitaive analysis input
"QUANT".
Laboratory LIMS sample identifier assigned to sample.
Input Percent moisture of the sample portion used in this test. Report in numeric format to two
decimal places. Example: 70.5% will wil be reported as 70.50.
Weight or volume of sample used for test.
Unit of measurement for sample amount. Use code from rt_unit.unit_code valid value table.
Leave this field Null
Leave this field Null
Comments about the test as necessary.
Input the preservatie used in sample analsysis. Use code rt_preservative.preservative valid value
table. Example: hydrochloric acid, 12N, 5 ML/L is input as HCL.
Final volume of the sample after sample preparation. Include all dilution factors.
The unit of measure that corresponds to the final sample volume. Use code from
rt_unit.unit_code valid value table.
Input CAS number code for chemical name. Use code from rt_analyte.cas_rn valid value table.
Input actual name of chemical. Use name from rt_analyte.cas_rn valid value table.
Analytical result reported at an appropriate number of significant digits. May only be null for non-
detects
Error range applicable to the result value; typically used only for radiochemistry results.
Input result type code corresponding to result type. Use code from
rt_result_type.result_type_code valid value table. Example; Input 'TRG' for a target or regular
result.
This field is used to state if the sample is reportable. Use 'Yes' for results which are considered to
be reportable, or 'No' for results that are not reportable. This field is used to distinguish the
value to be reported for a diluted or reanalysis run. It is also used to indicate if a sample has
been rejected during validation. Example: A sample was diluted and reanalyzed due to a
calibration exceedance. The diluted result for the chemical that exceeded its calibration range
would have a "Y" input, where the non-diluted result would have an "N" input.
Input 'Y' for detected analytes or 'N' for non_detects. Use "Y'"for estimated (above detection limit
but below the quantitation limit) or "" for tests such as flash point. Note that '' for tests such as flash point. Note
that '<' must not be used to indicate non_detects (use 'N' for non_detects instead).
Qualifier flags assigned by the laboratory.
Qualifier flags assigned by the validation firm.
Final qualifier flags assigned by the validator. Use codes from rt_qualifier.qualifier valid value
table. Example: The validator adds a "J" flag to a sample result that is laboratory qualified as
"D". "DJ" would be the value entered.
Indicates if the result has been validated. Input "Y" for validated and "N" for not validated.
Must be either "Y" for organic constituents or "N" for inorganic constituents.
The value entered in this field should be the sample-specific detection limit concentration level
above which results can be quantified with confidence. It must reflect conditions such as dilution
factors and moisture content. Required if detect_flag is “N” (non-detect)
Units of measurement for the result. Controlled vocabulary, see Units valid value table.
Units of measurement for the detection limit(s). This field is required if a
reporting_detection_limit is reported.
Method detection limit. Value reported in detection_limit_unit field.
Quantitation limit. Unit reported in detection_limit_unit field.
Code used to identify the task under which the field sample was retrieved.
Result specific comments.
Checks
Field Name Data Type Key Required Default Parent
sys_loc_code Text(20) PK Y BasicLoc_v1.sys_loc_code
start_depth Numeric PK Y
material_type Text(40)
geo_unit_code_1 Text(20) Y
geo_unit_code_2 Text(20)
remark Text(255)
Lookup
rt_material.material_name
rt_geologic_unit.geologic_unit_code
rt_geologic_unit.geologic_unit_code
Comment
Location identifier of sample collection, soil boring, or well installation. Use sample location ID.
Must be unique for each OU or AOC. Examples: MW-01, A-1, SB6, etc. See Section 3.2
'Definition of a Facility, Subfacility, and Location' for additional information. Must be a valid
sys_loc_code for the subfacility and match the sys_loc_code field in the Location_v1 EDD file
submitted in the current or previous EDDs
Depth to top of lithologic unit below ground surface.Must be in Feet.
The type of material that composes a lithologic unit. Must be used in all cases except when a
depth specific comment is being made.
The data providers interpretation of the hydrogeologic unit present at this lithologic unit.Example:
Upper aquifer, lower aquifer, Magothy aquifer, upper confined aquifer, glacial aquifer, etc.
Alternate geologic unit grouping. This can be a sub-classification of geologic_unit_code_1 or a
layer used for groundwater flow/transport computer modeling that contains the lithologic unit.
Comment on the lithologic unit.
Checks
Field Name Data Type Key Required Default Parent Lookup
file_name Text(255) PK Y
file_type Text(20) Y rt_file_type.file_type
file_date DateTime
title Text(255)
author Text(255)
remark Text(255)
place_type Text(50)
place_code Text(50)
place_subcode Text(50)
content
Comment
Name of the file.
Type of the file. Example: Data file, image, GIS, CAD, etc.
Date of the file. MM/DD/YYYY
Title of the file.
Author of the file.
Remark for the file.
Type of place this file is associated with. Example: DEC site name
Code/identifier of the place this file is associated with. Example: DEC site code.
Subcode/identifier of the place this file is associated with.
Content of the file.
Checks