DCC DGM Standards - V2 0 408586

REFERENCE DOCUMENT
DCC DIGITAL GEOPHYSICAL MAPPING STANDARDS

FOR MUNITIONS RESPONSE PROJECTS
V 2.0
Prepared by: DEFENCE CONSTRUCTION CANADA

Date of Release: January 19, 2011
DCC Digital Geophysical Mapping Standards Page 1 of 23
Date: Jan 19, 2011

for Munitions Response Projects
Version: V 2.0
CONTENTS
1.0 Introduction.........................................................................................................................................................................1
2.0 Summary of Key Standards and Data Specifications .........................................................................................................1
3.0 Equipment Functionality and QC Tests ..............................................................................................................................3
4.0 Soft Prove Out ....................................................................................................................................................................7
5.0 QC Seeding Program .......................................................................................................................................................10
6.0 DCC/DND Blind Seed Program ........................................................................................................................................13
7.0 Geophysical Data Specifications ......................................................................................................................................15
8.0 Hard Prove Out and Clearance Standards ......................................................................................................................18
9.0 Geophysical Data Deliverables ........................................................................................................................................19
10.0 Data Transfer ...................................................................................................................................................................22
1.0 INTRODUCTION
1.1. This document provides the digital geophysical mapping (DGM) contract standards for all
Munitions Response (MR) projects conducted for Defence Construction Canada (DCC) on behalf
of its partner, Department of National Defence (DND).
1.2. Geophysical data or results submitted to DCC that fails to meet the requirements described
herein may be rejected and requested to be re-acquired or submitted as per the requirements
outlined in this document.
1.3. For site-specific information on the geophysical survey requirements please refer to the
statement of work (SOW). Where there are discrepancies between this document and the SOW,
the SOW shall have priority.
2.0 SUMMARY OF KEY STANDARDS AND DATA SPECIFICATIONS
2.1. The following table summaries some of the key standards and data specifications outlined in this
document. For a full description of the specification please refer to the relevant section indicated
in the table.
Date: Jan 19, 2011

Version: V 2.0
Requirement/ Ref.
Applicability Performance Standard Frequency Consequence of Failure
Test Section
95% of data shows noise less Start and Days data fails unless other
All DGM than the established maximum end of evidence is submitted that
Static Test 3.2
Surveys threshold determined at start production demonstrates equipment
of the project. day functionality.
Response amplitude must not Start and Days data fails unless a QC 3.3
vary by more than 10% from end of seed item is successfully
Instrument All DGM
the benchmark response production mapped that day and the
response Test Surveys
determined at start of the day recorded anomaly signature is
project. repeatable.
95% of all recorded positions Start and Days data fails unless QC seed 3.4.1
Geodetic
All DGM must lie within project design end of item is successfully mapped that
Equipment
Surveys limits. production day with required positional
Functionality
day accuracy.
Maximum 5 cm offset from Start of Production is delayed until 3.4.2
established benchmark / production specification achieved
100% survey control point (NAD83). day
Geodetic Coverage
Accuracy surveys After
moving
base-
station
100% 98% <= 20 cm along line. By daily Recoverage of affected areas 7.1.3
Along-line Coverage Never to exceed 1 m. dataset
measurement Ground-based
Surveys
All DGM >90% at or below project By daily Recoverage of affected areas -
Speed
Surveys design maximum dataset
Position All DGM <3.5 m between updates and By dataset/ Affected areas fail. Reacquire 7.2.4
Update surveys using <4.0 sec between updates work grid affected areas.
(Along-Line) digital geodetic
Spacing equipment
100% Not to exceed project design By daily Infilling of data gaps required 7.1.3
Coverage maximums dataset
Surveys
Survey Line
(Transect) Assessment >90% of data with line spacing By dataset Infilling of data gaps required 7.1.1
Spacing Surveys at project design maximums.
(<100%
coverage)
100% QC seeds must be detected By daily Dataset / work grid fails. 5.1
QC seed item Coverage and selected as a dig list dataset or Explanation of the root cause of
detection Surveys target according to project by work the failure and corrective action
design grid is required
By QC Work grid / dataset fails 5.3.11
seed item provided the error was not
Horizontally 95% of the sourced by unavoidable site
QC seed item 100% interpreted locations of QC conditions (e.g. steep terrain)
positional Coverage seed items must be within a 70 Explanation of root cause of
accuracy surveys cm radius of the true location. failure and corrective action may
be required.
100% All emplaced DCC/DND blind By dataset/ Data submittal fails. Explanation 6.0
DCC/DND Coverage seeds must be recovered work grid of the root cause of the failure
Blind seed Surveys with during the intrusive and corrective action is required
Clearance investigation
Date: Jan 19, 2011

Version: V 2.0
Requirement/ Ref.
Applicability Performance Standard Frequency Consequence of Failure
Test Section
Operations
Geophysical Not too exceed maximum By daily Affected areas fail. Reacquire 7.3, 7.4
ALL DGM
Noise levels noise level threshold dataset affected areas.
survey work
on survey established at the SPO
Horizontally 95% of the dig list By dataset/ Work grid / dataset fails 8.2.2
100% locations data must be within a work grid provided the error was not
Dig List Coverage 70 cm radius of the true sourced by unavoidable site
Positional Surveys with location. conditions (e.g. steep terrain)
Accuracy Clearance Explanation of root cause of
Operations failure and corrective action may
be required.
100% Excavation sites are verified By target Lot submittal fails. 8.0
Anomaly Coverage clear by DGM re-mapping
removal Surveys with (verification survey)
verification Clearance
Operations
3.0 EQUIPMENT FUNCTIONALITY TESTS
3.1. GENERAL - The goal of the equipment functionality tests is to monitor the operational worthiness
of the geophysical hardware. All equipment must meet or exceed the specifications of the
required tests described herein before surveying can proceed. Tests required at the start of the
survey day must be closely examined and deemed acceptable before starting the collection of
survey data. If surveying does proceed with equipment that has not passed all required tests for
that day, the survey data will not be accepted and the contractor will be required to re-cover the
affected areas at their expense. The tests must be repeated following any change to equipment.
The required frequency of the tests is summarized in Table 1 below.
Table 1. Minimum Frequency of Equipment Functionality Tests
TEST Frequency of testing

Start of Beginning of End of Day Following
Project (Part Day Equipment
of SPO) Change
Static
X X X X
Instrument Response
X X X X
Geodetic Scatter Test
X X X X
Geodetic Accuracy
X X X
Cable Shake
X X X
Personnel
X X X
System Latency (Lag)
X X
Date: Jan 19, 2011

Version: V 2.0
3.2. STATIC TEST The purpose of the static test is to determine whether a particular geophysical
system is recording stable readings. Potential sources of inconsistent readings include:
instrument malfunction or non-optimal configuration, local ambient noise from electrical
transmission lines and instability of the Earths magnetic field (such as during a magnetic storm).
Recording data while the instrument is static (stationary) provides information on the local
ambient noise levels of the area and the base noise of the geophysical equipment. Since this test
is conducted while the sensor is stationary the recorded data will be free of insitu noise sources
(such as from local geology) and also free of noise due to movement and vibration of the
equipment.
3.2.1. A static test point shall be established near the survey site which is free of metal and is
sufficiently far from power lines, roads, vehicle parking areas, etc. to avoid these sources of
noise. It is recommended that the same point be used throughout the duration of the
project. On large sites, multiple test points may be necessary. The test point should be
clearly marked and documented so that the instrument will be located in the same location
and for each test. It is critical that all personnel conducting the static test or working within
close proximity of the test site be free of metal that could introduce unwanted anomalous
responses.
3.2.2. Data shall be recorded continuously for a minimum of three (3) minutes. Data recording
will be started after the instrument has been powered-up for a time sufficient to for the
electronics to reach a stable operating temperature. The test must be conducted with the
geophysical system in the same configuration that will be used for the survey work.
Positioning systems must be initialized and in the same configuration that will be used
during the survey. To improve the efficiency of the equipment testing, the GPS Scatter
Test (Section 3.4.1) may be conducted at the same time as the static test.
3.2.3. To pass the static test, 95% of readings must not exceed the maximum background noise
threshold established at the start of the project (e.g. Peak to Peak maximum).
3.3. INSTRUMENT RESPONSE TEST The instrument response (IR) test directly follows the static
test (Section 3.2). The data for the IR test shall be recorded in the same data file as the static
test. The purpose of the IR test is to quantify the response of the instrument to a standard metallic
test item and verify that the reported amplitudes of geophysical anomalies remain consistent
during the course of the survey.
3.3.1. Following the minimum three (3) minutes of data recording for the static test, a metallic
calibration item is introduced at a carefully controlled distance from the geophysical sensor.
3.3.2. The introduction of the item must produce a step anomaly in the recorded data that is at
least ten times (10x) background noise levels. Data shall be collected for at least 1 minute
with the item in place. The item is then removed from range of the equipment and data
shall be recorded at background level for an additional 1 minute.
3.3.3. To Pass the IR test the resulting response amplitude from the calibration item must not
vary by more than 10% from test to test.
3.3.4. The same calibration item and the same distance/orientation from the geophysical sensor
must be used for the duration of the survey. It is critical that careful controls are in place to
Date: Jan 19, 2011

Version: V 2.0
ensure positional consistency of the item with respect to the geophysical sensor from test
to test.
3.4. GEODETIC EQUIPMENT FUNCTIONALITY TESTS These tests aim to ensure that any
geodetic survey equipment (e.g. Global Position Systems (GPS), Robotic Total Stations (RTS) or
similar) that is used for any survey or data capture tasks are properly configured and in good
working order.
3.4.1. GEODETIC SCATTER TEST - The contractor shall verify the positioning precision reported
by the equipment by continuously recording positional data over a minimum three (3)
minute period in a static position. Positional readings must be recorded at the same
sampling/update rate that will be used for the survey work and in the same configuration.
The test may be performed in conjunction with the static test of the geophysical
instrumentation (Section 3.2).
3.4.1.1. If more than 5% of the data readings fall outside the instruments accepted and/or
required operational threshold, the equipment will fail the test and must be
corrected or replaced prior to further surveying.
3.4.1.2. The Geodetic Scatter Test shall be performed at the beginning and end of each day
of work that require use of the positioning-system and may be acquired
concurrently with the Static and IR tests for the geophysical sensor.
3.4.2. GEODETIC ACCURACY TEST For 100% DGM coverage surveys the contractor shall
perform a verification of the absolute accuracy of the positioning system data and verify
that the survey is tied into established survey networks (NAD83). A single kinematic
reading shall be recorded over a local benchmark or an established point. Positioning
accuracy will be measured by evaluating the offset from the known location. In most cases
this test will require that the GPS rover antenna be removed from the geophysical survey
platform and mounted on a survey rod with a level.
3.4.2.1. A kinematic positional error exceeding a 5 cm offset from the known benchmark co-
ordinate will not be accepted and the contractor must correct the problem before
proceeding and/or continuing the survey work.
3.4.2.2. The Geodetic Accuracy test shall be performed at the beginning of each day of
work that requires use of the positioning equipment and after repositioning or
reconfiguring any geodetic base stations.
3.4.2.3. In large survey areas, the contractor may be required to move the GPS base
station to in order to ensure a reliable radio link between the rover unit and the
base station. Whenever any geodetic base station is moved and/or reconfigured,
the accuracy test must be repeated.
3.5. CABLE SHAKE TEST The primary reason for conducting this test is to ensure that movement
of cables on the survey equipment/platform does not introduce significant noise. It also ensures
that there are no loose connections or shorts in the cables that could potentially cause noise
Date: Jan 19, 2011

Version: V 2.0
spikes in the geophysical and positional data during survey execution. The exact method for the
used to meet these quality objectives shall be described and justified by the contractor. It is
required that the test is conducted with the system in survey configuration. Data shall be recorded
in a static location during the test and all data fields that would be recorded during the survey
should be recorded during the test.
3.5.1. If significant noise is present as a result of cable movement it must be addressed

appropriately before proceeding with data collection. Faulty cables or connectors shall be
replaced prior to data collection. Loose cables will be taped to prevent excessive
movement during data collection
3.5.2. The Shake Test shall be performed daily, prior to the start of survey data acquisition.
3.6. PERSONNEL TEST - This test verifies that all personnel operating or working within close
proximity to the survey platform are free of magnetic and/or conductive material that could
potentially affect the survey data. The method used for the personnel test shall be described and
justified by the contractor.
3.6.1. The Personnel Test shall be performed at the start of each survey day and following any
crew change.
3.7. LAG TEST - A lag test determines if there is latency and/or a systematic offset between the
reported location of the geophysical sensor and the true location. The lag test is generally
performed by towing the geophysical system over a suitable target in opposing directions. The
distance or fiducial offset between equivalent points of the target anomaly shall be determined,
reported and applied to the data by the contractor, minimizing any offsets in the response.
3.7.1. The Lag Test shall be performed during the SPO (prior to the survey start). The lag test
shall be repeated if any major component of the data acquisition system (including
software) is modified, reconfigured or replaced. If variable lag is observed at any point
during the survey, a daily lag test shall be performed.
3.8. REPORTING OF EQUIPMENT FUNCTIONALITY TEST RESULTS
3.8.1. The contractor shall record and report on all the functional tests performed as outlined in
Table 1. The contractor shall prepare and deliver a short daily report which summarizes the
results of the equipment functionality tests completed that survey day. A summary report
(e.g. Excel Table) should also be prepared showing the day-to-day variability of these
functional tests.
3.8.2. The contractor shall provide all data (raw and processed) that were acquired during the test
procedures or used in the evaluation of the test procedures. The data formats shall follow
the requirements described Section 9.0.
Date: Jan 19, 2011

Version: V 2.0
4.0 SOFT PROVE OUT
4.1. REQUIREMENTS
4.1.1. Prior to commencement of the geophysical survey, the contractor shall carry out a site-
specific Soft-Prove-Out (SPO) to demonstrate the detection capabilities of each geophysical
system and proposed survey team.
4.1.2. The SPO survey data shall be re-acquired following any modifications to the geophysical
equipment, after remobilization, or after any events that require reevaluation of the
equipment.
4.1.3. The contractor will be responsible for the design, construction, field mapping, data analysis
and the evaluation of the SPO. The design and construction responsibilities include the
selection, acquisition and emplacement of seed items.
4.1.4. The items selected for the SPO must be site specific and should represent the type of
munitions expected in the area as indicated in the SOW and/or historical data. The items
should be placed in a sufficient number of different depths and orientations so that the SPO
is representative of the detection challenges that will be faced during the survey. It is
recommended that the placement of some items should attempt to challenge the detection
limits of the geophysical system within the requirements of the SOW.
4.1.5. Prior to emplacement of the SPO seed items, the design of the SPO shall be approved by
a DCC representative.
4.2. SPO CONSTRUCTION
4.2.1. Site Selection - The location of the SPO should aim to be representative of the conditions
that are expected throughout the survey area. This includes terrain, geology, vegetation
and geophysical noise conditions.
4.2.2. Surface Clearance - Once the area for the emplacement of the SPO items is selected, the
contractor shall establish the boundaries and perform a suitable clearance to insure that the
site selected for the SPO is sufficiently free of existing metallic debris.
4.2.3. Tests and Calibrations All equipment functionality tests described Section 2 of this
document shall be performed on the geophysical equipment prior to their use on the SPO.
The results must be analysed and deemed satisfactory by the contractors geophysicist
prior to continuing.
4.2.4. Background Survey - A survey will be conducted over the SPO site in order to obtain the
geophysical response of the site prior to seeding the target items. The same geophysical
system and configuration that will be used in the survey must be used for all SPO
surveying.
4.2.5. Seed Item Emplacement the seed items shall be emplaced as designed by the contractor
and as approved by the DCC representative.
Date: Jan 19, 2011

Version: V 2.0
4.3. SPO SURVEY
4.3.1. Data acquisition - The SPO survey must be conducted in the same manner as the
production survey in order to demonstrate that the geophysical equipment, survey execution
and data analyses are appropriate. The survey should be conducted so that both worst-
case and best-case detection scenarios can be analysed. For example, a survey line
should be collected directly over the seed items as well as at the maximum lateral offset
from the seed item that could be encountered during a 100% survey.
4.4. DATA ANALYSIS
4.4.1. Static Test Data Noise Levels- The static test data (Refer to Section 3.2), is collected prior
to the SPO survey. This data shall be analysed and used to establish the benchmark noise
level specification for all future static tests for the duration of the survey (for that particular
system).
4.4.2. Instrument Response Test Amplitude The Instrument response test data shall also be
analysed to determine the expected step-response amplitude from the calibration item (refer
to Section 3.3).
4.4.3. The raw geophysical data collected during the SPO survey should be processed and
interpreted to select the anomalies resulting from the emplaced SPO items.
4.4.4. The processing and interpretation procedure must be detailed in the SPO Letter Report
(Section 4.5) and must be representative of the processing and interpretation procedure
that will be used during the geophysical survey of the site.
4.4.5. It is recommended that information from each emplaced item be tabulated with the
minimum following fields: emplaced parameters (items description, actual GPS coordinates,
emplaced depth and orientation), survey results (Geophysical response) and data
interpretation (interpreted target location, offset distance from the emplaced location).
4.4.6. The resulting responses recorded from the SPO should be analysed and used to establish
the methodology that will be used to identify the munitions in the survey area. The target
picking methodology shall be justified by the contractor in the SPO letter report (Section
4.5).
4.4.7. Survey Noise Levels The SPO survey data shall also be analysed in order to approximate
the acceptable geophysical noise levels during survey. Note that the survey noise
specification should be higher than the static test noise level specification as the SPO
survey data will contain noise related to sensor movement.
4.4.8. Detection Depth - The smallest ordnance item that can be reliably detected at the specified
Depth of Investigation (DOI) should be determined by the data analysis. An explicit
statement regarding the detection limits of the geophysical system should be included in the
SPO Letter Report (Section 4.5) - as justified by SPO results.
Date: Jan 19, 2011

Version: V 2.0
4.5. SPO LETTER REPORT - The contractor must submit a SPO letter report, which will
comprehensively describe the SPO. This report shall include a justification for the SPO design
and methodology used. It is critical that the report clearly demonstrates that the geophysical
system and proposed survey methodology is capable of meeting the requirements of the SOW.
4.5.1. The contents of the SPO letter should include the minimum following information:
Introduction
Description of the geophysical system being proven and objectives of the SPO
Methodology
SPO location
SPO Design rationale (How requirements are met)
SPO Construction (Describe how SPO was prepared and constructed)
SPO Survey Specifications and Methodologies (line spacing, survey speed,
sample intervals, data collection and data processing methodologies)
Results/ Conclusions
Functional tests
Static test background noise results
Instrument Response results
Background survey (includes colour map of background survey)
SPO survey results (includes colour map of SPO survey)
Tabulated SPO results (refer to section 4.4.5)
Geophysical noise levels expected during survey
Detection limit statement
Positioning accuracy statement
4.5.2. SPO Map Presentation - The resulting grids/ geophysical maps for the Background survey
and the SPO survey shall be displayed at an appropriate scale and use the same colour
bar.
4.5.3. Digital data of all tests and calibrations as well as data from the Background and SPO
surveys must accompany the SPO Letter report. The SPO digital data must follows the
requirements outlined in Section 9.0.
Date: Jan 19, 2011

Version: V 2.0
5.0 QC SEEDING PROGRAM
5.1. REQUIREMENT OVERVIEW If appropriate for the work being conducted, contractors shall
include a comprehensive QC Seeding Program as a key component of their geophysical survey
plan. Seeding refers to the emplacement and burial of munition-like objects (the QC Seed
Items) in the MR survey area in order to further test and validate the detection process. Critical to
the success of the program is maintaining the secrecy of the QC seed locations from the survey
operators. This will ensure that the survey path is not biased to provide preferential coverage over
the QC Seed locations. The process will also aim to provide a measure of the spatial accuracy
of the geophysical survey data in production mode. This can be accomplished by calculating the
spatial offset of the detected geophysical anomaly centre to the known seed locations. This
requires that the seed locations are carefully emplaced, and that the positions are accurately
recorded using survey-grade positioning equipment.
5.2. PLANNING The contractors should have a seeding program plan that includes the following:
A description of the objects that will be used as QC seeds

Seed distribution plan (quantity, distribution, depths, orientations)
Personnel that will be used to emplace the seeds in the production area
Methods and tools required to safely and accurately emplace the QC seeds in the production
area
Methods used to record burial depth and orientation, and horizontal position
The Seed Registry design (i.e. table fields)
Personnel responsible for maintaining the seed registry
Data evaluation methods
Actions will be taken in the event that a seed is not detected by the geophysical system or
detected but with a positional error outside of the project tolerances (e.g. nonconformance
procedure and a root cause analysis followed by corrective action)
Communication of the seed program status with the DCC representative
5.3. MINIMUM STANDARDS - The following text outline minimum standards that apply only to 100%
coverage surveys conducted with land-based platforms (e.g. man-portable and towed arrays
platforms).
5.3.1. Seed item selection - The contractors QC Seeds should aim to be representative of the
smallest (or most challenging to detect) munition item that is intended to be detected by the
geophysical survey. The QC seed items may be:
1) Inert Ordnance - Actual inert ordnance items that have been verified free of explosives
of the same type that is expected to be found on the site.
2) Munition Surrogates - Metal objects of the same size, material, and general shape that
mimic the geophysical response of the ordnance expected at the site.
3) Industry Standard Object (ISO) Munition Surrogates Refer to Section 6.2.

Date: Jan 19, 2011

Version: V 2.0
5.3.2. Quantity and Distribution - The contractor shall plan to emplace a minimum of one seed for
every Hectare (10,000 m2) of 100%-coverage survey area. If a work grid system is used
with grids that are one Hectare or smaller then at least one seed shall be emplaced in each
work grid. If a work grid system is not used, then an attempt will be made to distribute the
seeds over the survey area in a manner that aims to have at least one QC Seed item
encountered by the survey team in each production day.
5.3.3. Burial depth - The QC seed items can be buried within the range at which the ordnance are
expected to be found on the project down to the maximum depth of investigation (DoI).
5.3.4. Signal Response Validation It is the responsibility of the contractors geophysicist to

select appropriate QC seed items and determine the expected signal response range of the
items at the intended burial depths and orientations. This process shall validate that that
the QC seeds will be detected and selected by the target picking methodology under
normal operating conditions. This may be accomplished by including several QC seeds in
the SPO site at the planned burial depths and orientations. Note that a single QC seed
type may be used across the entire survey area for consistency and to minimize the
number of QC seeds that must be included in the SPO for signal response validation.
5.3.5. Emplacement Seed items shall be emplaced in the production area by UXO-qualified
personnel working under the direction of the UXO QC manager and the Project
Geophysicist. The personnel emplacing the QC seeds should not be part of the
geophysical survey team. It is the responsibility of the contractor to develop a sound
procedure to ensure accurate emplacement depth and orientation.
5.3.6. Survey Equipment - Prior to burial, the horizontal UTM coordinates of the seed shall be
measured in the hole with survey grade equipment by appropriately trained personnel
separate from the geophysical survey team. Equipment used for measurement shall be
capable of passing a scatter test or repeat measurement within a tolerance of 5 cm. All
required functionality tests and QC tests on the positioning equipment should be performed
and verified acceptable prior to seed location measurement.
5.3.7. Measurement - For seed items smaller than 30 cm in length, the position of centre of item
should be recorded (centre of mass). For seed items with a long-axis greater than 30 cm,
the UTM position of the ends of the item should be recorded. Vertically oriented items only
require a central measurement. Burial depth measurement to the top of the item should be
accurate to 10 cm or less. Orientation (inclination / declination) should be accurate to 20
degrees or less.
5.3.8. Burial After measurement, the seed should be covered with the excavated fill, and
suitably compacted, taking care not to disturb the emplaced item position. An attempt
should be made to conceal the evidence of excavation so that the QC seed location is not
obvious to the geophysical survey team.
5.3.9. Seed Registry The contractors geophysicist shall compile the seed position
measurements and other relevant information into a single database or table known as the
Seed Registry. The contractors geophysicist shall be responsible for maintaining and
ensuring the accuracy of the registry. Minimum data fields that should be included in the
seed registry are as follows:
Date: Jan 19, 2011

Version: V 2.0
Seed ID#
Seed description (e.g. 1 diameter x 4 length pipe fitting steel)
Date seeded
Measured horizontal position (UTM Easting and Northing)
Approximate accuracy of measured horizontal position
Work Grid # or Grid Management Unit (GMU) # (if applicable)
Burial depth to item top
Inclination (e.g. horizontal, vertical)
Declination of long-axis (e.g. N-S)
5.3.10. Deliverable - The seed registry shall be provided to the DCC project representative prior to
the start of survey coverage.
5.3.11. QC Seed Positioning Accuracy - Horizontally, 95 percent of all QC seed items must lie
within a 0.70 m radius of the geophysically mapped surface location (Figure 1A). In cases
of where the QC Seed Item has a long axis larger 0.35 m, the mapped position must lie
within an ellipse where the minor axis is 0.70 m and the major axis is equal to the half-
length of the item plus 0.70 m (Figure 1B). All failures should be reported to DCC and
followed up with a root cause analysis and corrective action. Site-specific characteristics
(terrain, topographic features, equipment, etc.) that prevent these specifications from being
met shall be identified and justified by the contractor on a case by case basis.
A B
Radius 70 cm Minor
from item Axis (70 cm)
centre
Major Axis (70 cm + L)
70 cm L
Figure 1.
Date: Jan 19, 2011

Version: V 2.0
5.3.12. No Find if the geophysical mapping process fails to detect or select a blind seed anomaly
as a potential Munition or Explosive of Concern (MEC) the contractor shall flag this as a
QC failure and inform the DCC representative. If deemed appropriate, a root cause
analysis shall be preformed by the contractor and an explanation of the QC failure cause
will be provided in writing to the DCC representative. Corrective measures must be
implemented before surveying can continue. Re-coverage of affected areas (if required)
will be at the contractors expense.
6.0 DCC/DND BLIND SEED PROGRAM
6.1. OVERVIEW On any 100%- coverage DGM and MEC clearance project DCC/DND reserves the
right to secretly emplace standardized Blind Seed Items (BSIs) within the survey clearance
area without additional notification to the contractor. The location of the BSIs (if any) will remain
unknown (Blind) to the entire contractor team until they are located and removed from the site
by the contractors intrusive investigation and clearance team. If utilized, this will serve as
external QC on the contractors geophysical coverage and clearance of the site. DCC/DND seed
items are marked with high visibility paint and contain a decal identifying them as DCC/DND
seeds. The responsibilities of the contractor within this program are to:
record all BSI intrusive investigation contacts as per normal procedures;
return all excavated BSIs to the DCC representative to satisfy the QC test condition and
complete a root cause analysis and implement suitable corrective measures in the event
of a failure to locate a BSI in a clearance area.
6.2. BLIND SEED TYPES - DCC/ DND BSIs that may be used include actual Inert munitions that are
expected on the site -as disclosed to the contractor in the SOW-, or one or more of the three
Industry Standard Objects (ISO) munition surrogates described below:
DCC/DND Blind Seed Munition Surrogates
Small ISO (4)

McMaster-Carr part number 44615K466
Standard-Wall Black Steel Threaded Pipe Nipple - 1" Pipe X 4" L, Threaded Ends, 11/16"
Thread length, Schedule 40
Medium ISO (8)

Standard-Wall Black Steel Threaded Pipe Nipple - 2" Pipe X 8" L, Threaded Ends, 3/4" Thread
length, Schedule 40
Large ISO (12)

Standard-Wall Black Steel Threaded Pipe Nipple- 4" Pipe X 12" L, Threaded Ends, 1-17/64"
Thread Length, Schedule 40
Date: Jan 19, 2011

Version: V 2.0
6.3. BLIND SEED ITEM SELECTION DCC/DND will primarily use ISO standardized munition
surrogates as BSIs. One or more ISO type may be used by depending on the detection goals of
the project. DCC/DND will make every effort to ensure that the ISO surrogate item selection is
appropriate, given the detection challenges of the DGM survey and the known signal responses
of the ISO surrogates for commonly used instrumentation (EM61). The table below summaries
the munition surrogates that may be included in the DCC/DND blind seed program based on the
geophysical detection requirements in the SOW. Note that DCC/DND also reserves the right to
use the actual ordnance that are expected on the site (verified inert) as BSIs if available.
Table 2. Expected DCC Blind seed item selection given project detection goals.
Small Medium Large Actual Ordnance Item

SOW Project Detection Goal
ISO ISO ISO expected on site (inert)
40 mm projectiles or smaller
X X
2 mortars, similar sized munitions
X X X
Larger than 40 mm projectile but
X X
smaller than 105 mm projectile.
3 mortars, rockets and similar sized
X X
munitions
105 mm 155 mm projectiles
X X
All potential MEC anomalies
X X X X
Only MEC Larger than 155 mm
X
6.4. MAXIMUM QUANTITY (For project budgeting purposes). For projects with 100% DGM
coverage and clearance areas larger than 5 Ha, the maximum number of BSIs emplaced by
DCC/DND will be 1 per hectare of clearance area. For projects with a 100% DGM coverage and
clearance area smaller than 5 Ha, the maximum number of BSIs emplaced by DCC/DND will be
5. For high risk clearance areas such as future building footprints, DCC may emplace 1 BSI for
every 0.05 Ha (500 m2) within the high risk site footprint.
6.5. DISTRIBUTION, DEPTH AND ORIENTATION DCC may distribute the BSIs at their discretion
(evenly or unevenly) anywhere within -or on the borders of- the DGM survey and clearance area.
DCC may also opt to not place any BSIs without notification. DCC/DND Blind Seed items may be
buried with any orientation. Burial depth will be determined by DCC based on the expected
penetration depth of munition that the seed attempts to mimic on the site. BSI burial depth will
not exceed the maximum depth of investigation as stated in the SOW.
6.6. FAILURE TO LOCATE If at any stage during the project, the contractor declares an area
cleared or completed but fails to remove any number of the BSIs secretly emplaced by
DCC/DND, the DCC representative will inform the contractor of the QC failure. The contractor
must then perform a root cause analysis. DCC will make every effort to cooperate with this effort,
but It will be the responsibility of the contractor to provide an explanation of the failure in writing to
the DCC representative, and implement corrective measures that are deemed satisfactory to
DCC.
Date: Jan 19, 2011

Version: V 2.0
7.0 GEOPHYSICAL DATA SPECIFICATIONS
7.1. DGM COVERAGE
7.1.1. The contractor is responsible for determining the across-track survey line separation and
station spacing required to meet the specific DGM coverage goals. The coverage
methodology shall be justified in the SPO letter report, and approved by a DCC
representative prior to survey start.
7.1.2. Coverage of an area must meet the requirements of the Statement of Work (SOW) within
the defined project boundaries. A map showing the geophysical coverage of the area must
be provided in the final report which is based on the recorded survey path and accepted
sensor foot print (detection swath width).
7.1.3. The distance between adjacent survey lines of a 100% survey will not exceed the project
design maximum line separation unless impeded by fixed objects, cultural and/or
topographic features. Any data gaps identified in the foot print coverage maps shall
eliminated by re-surveying affected areas.
7.1.4. All survey obstacles preventing 100% DGM coverage shall be identified on the foot print
coverage maps and GIS deliverables. This may involve geographically capturing
unmapped site features with a GPS system.
7.1.5. Station Spacing Along line sample interval of geophysical readings in ground-based
electromagnetic or magnetic surveys shall not exceed 0.20 m. Up to 2% of data readings in
a daily dataset that exceed this specification are acceptable. Data that exceed this
specification may require recoverage at the contractors expense. Survey speed should be
closely monitored during data collection to ensure this specification is being met.
7.1.6. If the SOW specifies a percentage survey (e.g. 10% coverage for wide area assessment),
the contractor shall justify the survey approach (meandering path, transects etc.) and also
provide evidence that the coverage requirements stated in SOW have been met.
7.1.7. If multiple geophysical sensors are used on the survey platform to increase the detection
swath width (e.g. in a horizontal array of two or more EM coils) then positional coordinates
of each sensor or coil shall be provided in the databases.
7.1.8. The contractor shall correct of all geophysical data for Lag (Latency and/or offset) between
geophysical instrument data and the recorded position. This correction will be aided by the
results of the latency test(s) (Section 3.7).
7.1.9. A minimum of 2% of along line data in each survey hectare (or each pre-defined survey
grid - whichever is smaller) must be repeated in order to ensure consistent instrument
performance and data repeatability. The contractors geophysicist shall check the
resulting repeat-line data to ensure to consistency between passes on a daily basis. All
repeat data shall be provided to DCC.
Date: Jan 19, 2011

Version: V 2.0
7.2. GEOPOSITIONAL SPECIFICATIONS
7.2.1. All survey base-stations (if utilized) shall be precisely located over- and referenced to- an
established survey benchmark (monument) using accepted survey procedures.
7.2.2. All survey benchmarks that are used in the project must be fully described in the final
report. This includes a map showing benchmark / control point locations, a description of
the marker, and full geodetic coordinates (including elevation) in UTM projection and
NAD83 datum.
7.2.3. When using a Real Time Kinematic (RTK) GPS (or similar technology that requires a radio
communication link to a base station) - The communication link and RTK initialisation
status at the rover shall be monitored throughout the survey. The RTK fix (initialisation
status) shall be recorded in the survey data to ensure that the recorded positions have the
desired precision and accuracy.
7.2.4. Positional Update Spacing - Valid positional updates (e.g. RTK fixed) provided by the
positioning system -and recorded by the data acquisition system- must occur at intervals
less than 3.5 m meters along the survey line and must occur at intervals less than four
seconds (4.0 s) refer to Figure 2 below. In certain cases a DCC representative may
wave this clause due to technological limitations of the equipment or reduced positional
accuracy needs as required by the SOW.
Valid Positional updates
Reported Survey Path
Dropped
Positional Updates
(e.g. loss of RTK fix)
Geophysical data reading
locations (< = 0.2 m spacing for
ground surveys)
Distance must be less than 3.5 m
Time between measurements

must be less than 4 seconds
Figure 2- Minimum positional update spacing for DGM surveys.

Date: Jan 19, 2011

Version: V 2.0
7.3. ELECTROMAGNETIC DATA SPECIFICATIONS
7.3.1. Leveling - EM data (all coils and all channels) shall be corrected to account for temperature
and equipment drift and leveled to a standard baseline.
7.3.2. Noise Levels - Peak to peak noise levels in the EM data during survey shall not exceed
maximum thresholds established during the SPO (Refer to section 4.4.7). This excludes
power line or other man-made cultural EM noise. Any significantly affected areas will be re-
surveyed unless it is deemed by a DCC representative that lower noise levels cannot be
achieved.
7.3.3. Data Spikes - Data that is affected by spikes resulting in along-line data gaps greater than
50% of the survey design line spacing m will require re-coverage at the contractors
expense.
7.4. MAGNETIC DATA SPECIFICATIONS
7.4.1. Diurnal Activity - The contractor must account for diurnal activity and magnetic storms and
justify the method for removing these errors from the survey data.
7.4.2. Leveling The magnetic data shall be appropriately leveled to remove heading error, lag
and other errors such as sensor drift, baseline offsets and other time-varying errors from the
survey data.
7.4.3. Noise Levels Noise levels of the raw magnetic data will not exceed the maximum
thresholds established during the SPO prior to commencement of the work (excluding
natural anomalies, data spikes, power line or other man-made cultural magnetic noise). It is
recommended that noise in the magnetic data be monitored using a fourth difference filter.
7.4.4. Optimal Sensor Height The contractor must determine the optimal magnetometer sensor
height by performing a height optimization test. This test will aim to determine the sensor
height that will minimize terrain effects (such as from magnetic geology) while maximizing
response to munition items in the subsurface. The test should be conducted over an
established test line (such as in the SPO site). Data is collected with the magnetometer
sensor(s) at three different heights above ground surface. The height that optimizes the
target signal to noise ratio, while maintaining adequate sensitivity should be selected and
used for all survey work.
7.4.5. Magnetometer Sensor Orientation Several magnetometer technologies (e.g. cesium

vapour, potassium vapour) require that the magnetometer sensor be carefully orientated in
relation to the Earths magnetic field vector in order to obtain valid data. If any of these
technologies are in use, the contractor must determine and use the optimal sensor
orientation for the duration of the survey. Magnetic data that is affected by a loss of sensor
lock, or increased noise as a result of non-optimal sensor orientation may require re-
coverage at the contractors expense.
Date: Jan 19, 2011

Version: V 2.0
8.0 HARD PROVE OUT AND CLEARANCE STANDARDS
8.1. CLEARANCE STANDARDS WHEN USING DGM DATA
8.1.1. DGM anomalies selected for excavation by the geophysicist (the dig list) should be ground
located and marked with non-metallic pin flags by a survey team using equipment with an
absolute positional accuracy capability of at least 5 cm.
8.1.2. Flagged DGM anomaly locations should have the geophysical signature reacquired by a
search team for positional verification and refinement of the optimal dig location within pre-
defined search radius. Geophysical reacquisition should be completed using the same
equipment as in the survey if practical. Analog hand held detectors may be used if they are
capable of detecting the same types of metals (e.g. ferrous vs. non-ferrous) as the DGM
survey and have suitable detection depth.
8.1.3. Upon discovery of a metallic item (clutter or MEC) by intrusive investigation, the items
offset distance and compass direction from the DGM dig list location shall be recorded. All
located metallic items should have the following information recorded: item description,
burial depth, estimated mass. Located MEC items shall be fully described (burial
orientation, munition type, condition etc.) and photographed.
8.1.4. If the area is still heavily contaminated, it may be more cost-effective to complete a second
100% DGM survey and repeat steps 1 to 3 above. This is at the discretion of the contractor.
8.1.5. Following removal of a target item from an intrusive investigation site, the contactor must
verify that the geophysical anomaly selected by the geophysicist is no longer present by a
verification survey. This shall be conducted using the same geophysical method as the
original survey in order to prove -and provide a record that - all items that generated the
selected anomaly have been removed. This can be accomplished by collecting a swath of
data over every anomaly location and redirecting the intrusive investigation team to any
remaining anomalies (Refer to Steps 1 to 3 above).
8.1.6. Step 5 above should be repeated until a final map (gridded geophysical data) can be built
in a layered fashion that presents a map which demonstrates that no anomalies that
exceed the agreed upon parameters remain. In some cases, a 100% survey of the entire
area following final intrusive investigation and clearance operations may be the most cost-
effective option.
8.2. DIG LIST POSITIONAL ACCURACY SPECIFICATIONS
8.2.1. All located metallic items shall be tabulated with the minimum information: Burial depth,
offset distance from DGM anomaly location, offset azimuth (compass direction) from DGM
anomaly location, estimated mass, and type (e.g. NMD, MD, UXO)
8.2.2. 100% Surveys Horizontally, 95 percent of all excavated metallic items must lie within a
0.70 m radius of the dig list location (interpreted from the DGM anomaly) (Figure 1A
above). In cases of where the excavated item has a long axis larger 0.35 m, the
interpreted DGM position must lie within an ellipse where the minor axis is 0.70 m and the
Date: Jan 19, 2011

Version: V 2.0
major axis is equal to the half-length of the item plus 0.70 m (Figure 1B). Site-specific
characteristics (terrain, topographic features, equipment, etc.) that prevent this specification
from being met shall be identified and justified by the contractor on a case by case basis.
9.0 GEOPHYSICAL DATA DELIVERABLES
9.1. OVERVIEW - Both raw and processed geophysical data shall be provided for all calibrations
and tests as well as from the SPO and the geophysical survey. If geophysical grids and maps are
used in the analysis, target picking, or presented as figures in the written report they must also be
provided. Site-specific photos of the geophysical platform(s) and equipment, and the survey site
must be provided.
9.2. RAW DATA SPECIFICATIONS - For the purposes of this document raw data is defined as
digital data directly recorded by the data acquisition system, without any modification (or filtering)
that changes the originally recorded numeric values from the geophysical system
9.2.1. File Format For most DGM systems, raw data should be provided in ASCII text format so
that the data files are viewable in text editing software. If the data acquisition system
records data in a proprietary binary format, the contractor shall directly convert the data to
text format before delivery. Recommended file extensions are TXT and XYZ however other
file extensions are acceptable.
9.2.2. Raw data recorded by EM-61 MKII systems should be delivered in .M61 format.
9.2.3. Naming Convention - Each delivered raw file shall have an informative and unique name.
Daily production raw files shall have the acquisition date as part of the file name.
9.3. PROCESSED DATA SPECIFICATIONS - All processed geophysical data, including all tests and
calibrations shall be delivered in Geosoft Database (GDB) format . The GDB must be readable by
Geosofts Oasis Montaj software package.
9.3.1. Minimum Channel Information - Survey and SPO Databases shall include the following
minimum channel information:
Easting (X) and Northing (Y) co-ordinates in UTM projection (NAD 83),
Time (with precision to at least 0.1 s)
Raw geophysical data channels
Processed geophysical data channels.
9.3.2. Data Channel Naming Convention - Any appropriate naming convention for channels in the
database may be used as long as they described in the readme file (refer to Section 9.4).
The same channel names shall be used for the duration of the project.
9.3.3. Database Naming Convention - Each delivered GDB file shall have an informative and
unique name. Final data should include the word final in the database name. Daily
production GDBs shall have the acquisition date as part of the database name.
Date: Jan 19, 2011

Version: V 2.0
9.3.4. Units of Measure
9.3.4.1. All distance units will be reported in meters. If a target depth is specified, the
contractor shall provide the reference datum for the depth (i.e. from EM coil or from
ground surface).
9.3.4.2. Total magnetic field values shall be reported in nanoTeslas (nT).
9.3.4.3. Magnetic gradient values shall be reported in nanoTeslas per meter (nT/m)
9.3.4.4. Positional data shall be presented in the UTM projection. The NAD83 datum shall
be used for all work in North America. WGS84 datum shall be used outside of North
America.
9.3.5. Survey Path Presentation - All delivered databases will be organised into individual survey
lines using the GDB (Geosoft Database) line numbering feature.
9.3.5.1. Standard Survey Path - For standard line-path surveys, (consisting of numerous
parallel to sub-parallel lines), the lines should be broken at the apex of the turn. Each
line must have a unique line number. An effort should be made so that the line-
numbering is sequential across the survey area.
9.3.5.2. Meandering Path Surveys - For meandering path surveys, the data shall also be
broken into individual survey lines, or groups of lines to facilitate improved display of
the data in profile view. The division points may be based on a maximum number of
data readings per line or the discretion of the contractor.
9.4. DATABASE CHANNEL DOCUMENTATION - A readme document file must accompany all
delivered GDB files. The readme file will clearly provide the contents of each channel in the
delivered databases. The text may be organised into a simple table, listing each channel name in
the GDB, the units of measure of each channel, and a brief description of the channel. An
example is provided in Error! Reference source not found. below.
Table 3. Example Readme File layout
Database: Bordern_Oct21_2008.gdb
Channel Name Units Description
X m UTM easting, Zone 17, NAD 83 datum Trimble GPS RTK
Y m UTM northing, Zone 17, NAD83 datum Trimble GPS RTK
Mag1_corr nT Diurnally corrected total magnetic field from Magnetometer 1 (upper)

9.4.1. Acceptable formats for the readme file are: .TXT, DOC (MS Word), and .PDF (Adobe
Acrobat).
Date: Jan 19, 2011

Version: V 2.0
9.5. GEOPHYSICAL MAP FILE SPECIFICATIONS All map files used in the data analysis, target
picking and/or presented in any delivered report shall be provided.
9.5.1. File formats Geosoft map files (.MAP) preferred, however other map files may be
acceptable provided that they are georeferenced and of acceptable resolution and quality
so that all information on the map is easily readable.
9.5.2. If a Geosoft map file is not provided, all digital layers (vector and/or raster) used to create
the map must be provided separately in a georeferenced GIS format.
9.6. GEOPHYSICAL GRID FILE SPECIFICATIONS All geospatial grid files used in the data
analysis, target picking and/or presented in any delivered report shall be provided.
9.6.1. File Format - The file format provided shall be Geosoft Binary Grid (*.grd), and should also
include the associated geographic projection information file (*.grd.gi file).
9.7. DIGITAL PHOTOGRAPHS The contractor shall provide site-specific photographs of the
geophysical survey platform(s), base stations, and survey area that were taken during the survey
described in the SOW.
9.7.1. File format shall be .JPG and have a minimum resolution of 1024 x 768.
9.7.2. Naming Convention - Each photograph delivered should have an informative and unique
name.
9.8. DATA FORMAT SUMMARY - Table 5 summarizes the acceptable digital formats of all digital
deliverables.
Table 4. Summary of acceptable data formats for geophysical deliverables
Recommended Software
Item Acceptable File Extensions
Application(s)
Processed Geophysical Databases Oasis Montaj (Geosoft) GDB
Text editors TXT
Database readme files MS Word DOC
Adobe Acrobat PDF
Raw Geophysical data files (ASCII) Text editors TXT, XYZ, M61
Geophysical Maps Oasis Montaj (Geosoft) MAP (or other GIS format)
Geophysical Grids GRD

Oasis Monta (Geosoft)
Digital Photographs Image Viewers JPG
Table 5 Summary of acceptable data formats for geophysical deliverables
Date: Jan 19, 2011

Version: V 2.0
10.0 DATA TRANSFER
10.1. TRANSFER METHOD Preliminary geophysical data shall be transferred via internet
using file transfer protocol. Access to this DCC or DND FTP site will be provided to the contactor
prior to survey commencement. It shall be the responsibility of the contractor to ensure that
access is obtained prior to survey commencement. Alternative FTP sites may be used for data
delivery upon DCC approval.
10.2. DATA ORGANIZATION - All geophysical data and related files shall be placed in a
directory called Geophysical Data on the agreed upon FTP site. Within this directory, the data
shall be further organized into four main sub-directories, SPO for SPO data, DAILY for
preliminary results provided after every survey day, FINAL for final deliverables after completion
of the survey, and PHOTOS for site specific photographs. Sections 10.2.1 through 10.2.4 below
provides the full directory structure.
10.2.1. SPO Data
Path Description of directory contents

Geophysical Data\SPO\ RAW\ All raw geophysical data collected for the SPO. For data
format refer to Section 9.2.
Geophysical Data\SPO\Field Data\ Oasis Montaj GDB databases used in the SPO. Include the
required readme files for each GDB. Refer to Section 9.3 for
GDB format and Section 9.4 for readme file format.
Geophysical Data\SPO\Test\ All QC / functional test data in GDB format. Include the
required readme files for each GDB. Refer to Section 9.3 for
GDB format and Section 9.4 for readme file format.
Geophysical Data\SPO\SPO Report\ SPO Letter report - Refer to Section 4.5

Geophysical Data\SPO\*\ * Other relevant SPO directories and files may be added at
the discretion of the contractor
10.2.2. Daily Update Data

Geophysical Data\Daily\YYYYMMDD*\ RAW\ All raw geophysical data and test data collected for that day.
For data format refer to Section 9.2.
Geophysical Data\Daily\ YYYYMMDD*\Field Data\ All GDB databases containing processed data collected for
that day. Include the required readme files for each GDB.
Geophysical Data\Daily\ YYYYMMDD*\Test\ All QC / functional test data for that day in GDB format.
Include the required readme files for each GDB. Contractor
may include additional QC reports formats here.
Geophysical Data\Daily\ YYYYMMDD*\Docs\ Other relevant documents, diaries, or logs, for that day
Geophysical Data\Daily\YYYYMMDD*\**\ ** Other relevant daily directories and files may be added at
the discretion of the contractor
* Sub-directory named with the eight digit date (YYYYMMDD) of the day that the data was collected.
Date: Jan 19, 2011

Version: V 2.0
10.2.3. Final Data

Geophysical Data\Final\Field Data\ Final GDB database(s) Include the required readme files for
each GDB.
Geophysical Data\Final\ Targets\ Final target lists and or dig sheets if applicable
Geophysical Data\Final\ grids\ Final Geosoft-format grid files. Refer to Section 9.6.
Geophysical Data\Final\ maps\ Final geophysical map files Refer to Section 9.5.
Geophysical Data\Final\*\ * Other relevant directories for final deliverables may be

added at discretion of the contractor
10.2.4. Photos

Geophysical Data\Photos\ Site specific digital photos of equipment. Refer to Section 9.7
10.3. FINAL DIGITAL DELIVERABLES - Each final hardcopy report delivered to DCC shall
include all above digital data on CD or DVD media for archival purposes. The disc(s) must be
clearly labeled with all pertinent project information.

DCC DGM Standards - V2 0 408586

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

DCC DGM Standards - V2 0 408586

Hochgeladen von

Copyright:

Verfügbare Formate

REFERENCE DOCUMENT

DCC DIGITAL GEOPHYSICAL MAPPING STANDARDS

Prepared by: DEFENCE CONSTRUCTION CANADA

Date: Jan 19, 2011

2.0 SUMMARY OF KEY STANDARDS AND DATA SPECIFICATIONS

Date: Jan 19, 2011

Date: Jan 19, 2011

3.0 EQUIPMENT FUNCTIONALITY TESTS

Table 1. Minimum Frequency of Equipment Functionality Tests

TEST Frequency of testing

Date: Jan 19, 2011

Date: Jan 19, 2011

Date: Jan 19, 2011

3.5.1. If significant noise is present as a result of cable movement it must be addressed

3.8. REPORTING OF EQUIPMENT FUNCTIONALITY TEST RESULTS

Date: Jan 19, 2011

4.0 SOFT PROVE OUT

4.2. SPO CONSTRUCTION

Date: Jan 19, 2011

4.3. SPO SURVEY

4.4. DATA ANALYSIS

Date: Jan 19, 2011

Date: Jan 19, 2011

5.0 QC SEEDING PROGRAM

A description of the objects that will be used as QC seeds

3) Industry Standard Object (ISO) Munition Surrogates Refer to Section 6.2.

Date: Jan 19, 2011

5.3.4. Signal Response Validation It is the responsibility of the contractors geophysicist to

Date: Jan 19, 2011

Date: Jan 19, 2011

6.0 DCC/DND BLIND SEED PROGRAM

DCC/DND Blind Seed Munition Surrogates

Small ISO (4)

Medium ISO (8)

Large ISO (12)

Date: Jan 19, 2011

Small Medium Large Actual Ordnance Item

Date: Jan 19, 2011

7.0 GEOPHYSICAL DATA SPECIFICATIONS

7.1. DGM COVERAGE

Date: Jan 19, 2011

7.2. GEOPOSITIONAL SPECIFICATIONS

Valid Positional updates

Reported Survey Path

Distance must be less than 3.5 m

Time between measurements

Figure 2- Minimum positional update spacing for DGM surveys.

Date: Jan 19, 2011

7.3. ELECTROMAGNETIC DATA SPECIFICATIONS

7.4. MAGNETIC DATA SPECIFICATIONS

7.4.5. Magnetometer Sensor Orientation Several magnetometer technologies (e.g. cesium

Date: Jan 19, 2011

8.0 HARD PROVE OUT AND CLEARANCE STANDARDS

8.1. CLEARANCE STANDARDS WHEN USING DGM DATA

8.2. DIG LIST POSITIONAL ACCURACY SPECIFICATIONS

Date: Jan 19, 2011

9.0 GEOPHYSICAL DATA DELIVERABLES

Date: Jan 19, 2011

9.3.4. Units of Measure

9.3.4.2. Total magnetic field values shall be reported in nanoTeslas (nT).

Table 3. Example Readme File layout

Date: Jan 19, 2011

Table 4. Summary of acceptable data formats for geophysical deliverables

Geophysical Data\Final\\ Other relevant directories for final deliverables may be