Skip to main content

This final webinar in the series takes the form of a mini workshop covering the basics of processing magnetic data.

Good data processing is crucial to the successful completion of a magnetic survey. While often the quality of the processing relies on the experience of the data processor, there are a few rules we can follow to ensure we get good, repeatable results with every survey

Download the data set referred to in this webinar here.

Survey data provided courtesy of Geometrics, Base station data provided courtesy of Honolulu Magnetic Observatory: U.S. Geological Survey.



1 hr

See more on demand videos


Find out more about Oasis montaj

Learn more

Video Transcript

<v Becky>Hi, everyone.</v>

Welcome to the third and final webinar

in our three-part series

on Magnetic Surveying for Anthropogenic Objects.

Today, I’m going to focus on processing the data

with Oasis montaj.

In case you missed it in the webinar description,

by signing up for this webinar series,

you have been given a two-week evaluation of Oasis montaj

with the geophysics and UXO extensions included,

both land and marine.

I’ve made the Hawaii dataset available for you to download

if you wish to follow along

or try it out on your own after this webinar.

This mini workshop is really just an introduction

to our tools.

And with the limited time available to us,

I will be moving quickly through the steps.

And I do skip a few of the easier things

that I think you can probably work out on your own

with our online tutorial.

The recording will be available shortly after the session

on the Seequent and Geometrics website

for you to review and practice on your own

if you wish to do so.

So today we’re going to start by importing the data.

We’re going to create a map, filter and remove some noise,

run a few corrections,

like the base station and background removal.

We’re going to look at gridding the data

and then picking targets.

If we have time, hopefully,

we’ll look at two different methods for picking targets,

dipoles and the Blakley method.

Yeah, so to start, if you don’t have a Seequent ID yet,

that’s the first thing you’ll have to do actually.

So you’re going to go to

And when you get to the Sign In page,

you’re going to click Create a Seequent ID.

Now, I do ask that if you want to use

the license that I assigned,

you need to register with the same email address

that you used for this webinar.

That’s the email address that I assigned

the evaluation license to.

Once you’ve signed up here,

you’ll be sent an activation email

where you’ll have to click on a link

to activate your account,

but then you’ll be able to come back here, sign in,

give it a second. (laughs)

Yeah, so yeah.

So once you’re able to sign in,

you’ll be able to view your license.

If you go to Subscriptions and click on My Subscriptions,

you’ll see the evaluation license, when it expires

and what extensions you have access to.

And if you go to Products,

you’ll be able to download and install Oasis montaj 9.10

from this link here.

All right, so let’s jump into the software now.

If you can open Oasis montaj,

this is the landing page where you can create a new project

or open an existing project.

So we’re going to create a new project

and we’re going to save it in the same folder

where we’ve put the raw data,

that XYZ file that I sent everybody.

And we’re just going to call it Hawaii, something simple.

It doesn’t really matter what this project is called.

So you can see along the top, it’s loaded our core menus.

These are the menus that come with Oasis montaj essentials.

So if you have no other extensions,

you can still do quite a lot with the software.

And these are also the similar tools that you get

with the new Oasis montaj Field version

that if you’re a Geometrics customer, you can get access to.

So that’s a very light version of Oasis montaj,

but it’s sort of similar to these core menus,

just a little bit of background there.

What we’re going to start with

is loading the menus that we want to use today.

So if you click on this Load Menus button,

you’re going to expand the Extensions section.

And I have a full license,

so you see there’s a lot more menus available.

But you should see Geophysics.

So you can load the Geophysics menu.

You should also see UXO Land and UXO Marine.

So we’re going to go ahead and just load both of those

or all three of those menus.

All right, so we’re going to start just by importing the data.

If you right click on Databases, you can click New Database.

And we’ll just call this,

again, we’re just going to call it Hawaii.

I’m going to just accept the default 200 lines, 50 channels

and click OK.

I’ve already done this once, so for me it says overwrite,

for you it should just have created the database.

So I’ve just double clicked it to make it full-screen here.

And just a little trick, if you have the XYZ file,

open here in your working directory

in this processing folder.

You can just click this XYZ file

and you can drag and drop it into the database.

And that’s actually going to just load it automatically.

So XYZ’s a really simple format to work with.

Okay, so we’ve imported the data, we have our coordinates,

we have both latitude, longitude, and x and y in UTMs.

It’s also…

No, it’s currently unknown.

So actually, the first thing we can do

is just set our coordinate system up.

So if you go to Coordinates, Set Coordinate System,

we’re going to assign it to WGS84/UTM zone 4N.

And I have it saved here as a favorite,

but if just type in 4N, for example,

you can scroll down here to World, Northern Hemisphere,

and it’s in this 162 to 156.

That sets our coordinate system,

and you can verify it

in the bottom right-hand corner down here.

I like to create a map right away

and visualize my line path.

I want to see what we’re actually looking at.

So once you’ve set the coordinate systems,

you can create your first map.

So I’m going to go up to the Map menu, New,

and I’m going to just click on Scan Data.

And so that looks at the minimum maximum x, y,

and fills in the blanks for us automatically.

So we’re going to click Next

and we’re just going to give it a name.

So again, I’m going to just call it Hawaii

and I’m going to leave the map template.

That’s just the page size.

If you were going to print this, you need to tell it here

what size page you want to print it on.

I’m going to click Scale.

It’s going to pick the minimum scale

that this data fits on this page.

And then I usually just round that up.

I like even numbers.

I’m going to say 7,500 here.

And make sure your coordinate system is correct

and click Finish.

That just creates this empty map for us.

And then I’m going to go to Line Path.

So that’s under Map Tools, Line Path,

and this is going to display for me

the path that the boat collected the data along.

So just because I know from experience,

I want to just make my labels a little bit smaller.

And there’s an option down here which says Break on Gaps,

and this means if there’s a gap,

what this does is it connects the dots.

So it just draws a straight line

from one data point to the next.

But this can be a little bit misleading.

If you actually have big gaps in the data,

it basically draws the line across it.

So if you want to actually be able to visualize gaps

that are greater than, let’s say half a meter,

you can just put in here

where you want multiple line segments.

So it’s going to connect the dots

for anything that’s smaller than half a meter.

And if it’s greater than a half a meter,

it’s actually going to show you in your line path

where that gap in the data is.

So let’s just put half a meter here.

Also for UXO, I tend to put the thinning resolution to zero.

This just means that for larger datasets,

to make it a little bit faster,

it can remove the amount of points it uses to define a line,

but for UXO, when we’re getting down

to the really nitty-gritty detail,

this can sometimes cause offset in where your data is

and where the line path is drawn.

But if we reduce this to zero,

the line path should match your points exactly.

It can slow your map down a little bit,

so just something to be aware of.

All right, so now we have our path,

and I don’t see any gaps in the data,

so that’s sort of like our first QC

to know that we don’t have any gaps

of half a meter or larger in this dataset.

I just kind of got OCD in me,

I like everything to look nice.

I want to actually put a base map on here,

I want a legend, a scale bar, things like that.

So we’re going to go to Map Tools, Base Map,

and we’re going to draw our base map.

If you wanted to change your scale,

you can do so at this stage when you draw your base map.

And then I’m just going to adjust my margins.

So I want to leave a gap at the bottom,

but I don’t need a bigger gap around each of the edges.

And then this inside data margin

is the amount of space you’re going to leave

between the data and the start of your maps around.

So if you actually want to see

what’s happening around your dataset,

so around this line path,

you can just increase these inside data margins.

And so this is an interesting area because it’s near shore.

Normally with these offshore surveys,

I don’t set this inside data margin to be very big

because there’s nothing to see but water.

But in this case, since we’re near shore,

we’re in the harbor actually,

I think it’s actually Pearl Harbor,

if we just increased that a little bit,

we can start to see the shore

and we can actually figure out

where we are exactly in Hawaii.

And so then we can click Next.

I have a bit of a standard here.

My maps, I select to gray for my UTMs.

And I always put my latitude longitude

as edge ticks only.

So that means the only lines I’m going to get on my map,

the coordinate grid is going to be the UTMs,

but I will still see where the lat longs are

just around the outside.

And then this is the simple title block.

So we’re just going to call this Hawaii.

This is a single mag dataset.

So we’re going to call it Single mag, maybe Total Field.

We’re using a G-882 Geometrics magnetometer.

This is actually a dataset from Geometrics.

So they provided this.

And yeah, it’s a total field magnetometer.

So maybe here, we can say,

you can put your name as the processor,

and then at the bottom you can put the date

and then click Finish.

And then on your map, you can click on this world button

and it will just take you to the full view of your map.

So that looks a little bit nicer.

We have some background images that you can add.

So if you go up to the Data Services menu,

and you click on Add Azure Maps Imagery,

this will give you a satellite image in the background.

So we can select Aerial and click OK.

And this is the image I was talking about where,

because we left that extra space around the data,

we can actually see parts of the land,

and we can see that we’re working inside this Harbor area.

On your map, if you just expand your map manager,

and then I like to pin it open

and then we click on that Full World button,

if you expand the data view and the base view,

this will just show you what layers you have

displayed currently on your map.

So I like to have this open at all times.

And the difference here

is that anything in the data view at the top here

is geo-referenced.

And so you don’t want to move

or reposition any of these layers.

And they should be locked so that it doesn’t let you.

And if you want to just adjust this aerial image,

you can highlight, you can select it.

And then there’s this transparency option down here.

So if we make it a little bit transparent,

we can actually see the line path on top of it.

Okay, so this just sort of sets the background.

One of the things we need to know for when we grid the data

is we need to know what the line separation is

in this dataset.

So if we just click this button here, which is Zoom to Box,

we can draw a box, a small box, over our line path.

And you can use your mouse roller to zoom in and out

just to adjust it a little bit.

But what I want to do

is I want to measure the approximate distance

between these lines.

So if you right click on your map,

you have this Measure Distance function.

And you can click on one point and then click on the next,

and you can see this is about 13 meters.

You can click Done, and then do it again.

Let’s measure somewhere down here.

That’s like 12 meters, eight meters.

So I think the idea here is that this was supposed to be

roughly 10 meter distance between lines.

You can see that they have quite a lot of variation

along their lines here.

So it wasn’t smooth sailing the whole time.

We can assume a 10-meter line separation.

So when we come to grid this data,

we can start with something

that’s roughly a quarter of that line separation.

So our cell size will be about 2.5 meters.

All right, let’s look at the database though.

Let’s look at the actual data

that we’re going to be working with.

In this database, there’s a few QC channels.

When you get the data in,

you might want to check out the mag first of all.

So we can right click on a number in the mag column,

and we can click Show Profile.

And that’s actually just going to give us

this graph of the data.

Another one that you’re going to look at is Signal.

So this is a really good QC channel.

We don’t use it to process,

we’re just using it to check

that we’re getting a good mag reading.

And so the higher the signal,

the better quality the data is.

If this signal drops below 500 or 200,

I think most of the time industry standard

is just to delete that data,

because it usually means there was a problem,

the mag values cannot be trusted,

maybe the magnetometer wasn’t oriented correctly.

It could have hit a dead zone,

or there was something wrong with it,

you’re not getting good signal.

And so you just want to really QC this

for any really low values.

And so you can do that by taking the statistics.

We can do it visually.

If you display it on a profile window like this,

you can use the arrows here to move up and down,

and we can inspect it.

And you can see here where the minimum values are,

but we can also take statistics.

So if I click on Signal, the name, three times,

I highlight the name and the data,

this means that when I say Statistics,

when I right click again and click on Statistics,

I’m going to be looking at the statistics for the data,

all the data on all the lines in this database.

If I had clicked twice and only highlighted the data

and not the name when I click Statistics,

I’d only be looking at the statistics for this line only.

So the signal channel on this line.

And so that’s just a little clue

as to what you have highlighted

and what statistics you’re taking.

So you can see here it says all lines

because I have everything highlighted.

And I can see that my minimum value is 449

and my maximum is 1500.

So depending on what your contract says,

if it’s 500, then there’s some values here,

and especially on this line right here,

that you might need to delete.

If it’s 200 or something a little lower

then you’re safe and this isn’t bad.

I don’t know what the standard is,

maybe that’s a good question

for Bart and Gretchen at the end.

I’ve seen different requirements for the signal value.

In this case, you can see that it’s actually very close

to what looks like an anomaly,

but if we just play the altitude channel,

you can see that they’ve just sort of skimmed the seabeds,

the altitude has gotten really, really low

right at this location.

So that probably has something to do with this signal.

Maybe it dipped or there was some really fast movement

and that caused a variation in that signal channel.

And so that probably means

that there’s something a little hinky about this anomaly.

It could just be a jerk,

the cable jerked or something like that.

We’d probably want to look at this

a little bit more carefully

and see what we could determine from this data.

We’re going to leave it.

We’re going to accept everything right now.

So what we want to do is, actually,

we’re going to use these arrows

and we’re just going to look through our data

and we’re going to see if there’s any problems

that we need to fix.

And I do believe there’s one spike that we need to clean up.


So if we end up on line 18, you can see here,

there’s actually a spike in the data.

So we can see it in the altitude

and in the magnetometer channel.

So I’m going to right click in that top profile window,

and I’m going to click Zoom,

and I’m going to draw a little box over the base of that spike.

All right.

There’s a number of ways that you can get rid of this.

I’d like us to try using the nonlinear filter.

So it’s a really good filter

that captures these really sharp spikes in the data.

So we’re going to go to database tools, filters,

and we’re going to click nonlinear filter.

We’re going to select the mag channel.

And best practice here

is that you never edit your original data.

If you need to leave an audit trail.

If the customer that you’re delivering this database to,

they want to see everything you’ve done

to the original data.

That means, every time you run a filter

or you make a change,

you’re going to output a new channel name.

So in this case, I’m going to say Mag underscore edit.

So this is just the first edit.

It could be a manual edit, it can be a filtered edit.

It doesn’t really matter,

but this is usually what I call my D-spiked channel.

Now for the nonlinear filter,

it needs a width and a tolerance or amplitude.

What this is looking for is how many fiducials.

So this filter width is in fiducials.

And when I say the word fiducial,

what that means is, it’s a row number,

the number of rows or the number of samples.

So let’s cancel this ’cause we’re going to look at this spike

in a little bit more detail.

But it needs to know what is the width of the spike

that I’m going to delete that I want it to filter through

and what is the tolerance or what’s the amplitude,

so what’s the size of the spike.

I’m just going to cancel this for now.

And what I’m going to do is I’m going to highlight

the width in the profile window here.

And you can see that what I’ve highlighted

is three fiducials.

It looks like it’s only one fiducial,

but I always include one before and after.

So I would actually say that this is a three-fiducial spike.

And then the tolerance is basically the difference

between the background values and the actual spike.

So in this case, it drops down to 1,300 from about 35,000.

So we don’t need to be specific about this amplitude,

you don’t need to put the exact 35,000 minus 1300,

because it’s more general than that.

What we can do is we can give it something that’s smaller.

That’s almost 34 or 33,000.

That’s roughly 34,000.

We don’t need to put in 34,000

because we know that at a much smaller amplitude,

it would still be considered a spike.

So we could put something here like 5,000 nanoteslas.

And what we’d be saying is that,

if there’s a three fiducial anomaly

that has an amplitude of 5,000 nanoteslas, get rid of it.

And so you can capture many more spikes

by making it a little bit smaller,

and you can even make it wider.

So we could say even five nanoteslas.

If we have anomaly that’s five fiducials

that changes by 5,000 nanoteslas,

that would still be considered a spike

’cause there’s no UXO or object

that’s going to cause a change that rapid.

So let’s go back here to Filters, Non-linear Filter.

We’re going to select again the mag,

call it Mag underscore edit.

So let’s try that, five and 5,000.

And then we’re going to click OK.

Now it’s output this new channel.

So right away, what I’m going to do

is I’m going to right click on a number

under this new channel and click Show Profile.

And it looks like there’s an offset,

but that’s really just because

we have to change our y-axis options.

So you’re going to right click in that profile window,

and you’re going to click, under Profile Scaling,

you want to select Same Access Scale for All Profiles.

And then you see that it shifts them

so that the y-axis is the same for the mag

and the mag edit channel.

And then I’m just going to zoom in again on the top here.

And you can see it’s drawn a straight line

just as we’d expected.

And to see it a little bit better,

if I actually just remove the original mag and rescale,

I can actually see where it used to be down here

and what it now looks like.

And it’s just basically drawn a straight line

through those three fiducials.

This dataset only had the one spike.

Normally you’d have to inspect each line

and make sure it did what you want it to do.

This is a really important step.

You need to make sure you’ve really cleaned it up.

This is really clean data,

so we don’t really need to do much to it.

You could filter it.

There’s small amounts of noise here and there,

but it’s really minor

and it’s not going to cause any significant difference

to our results whether we smooth it at this stage or not.

So we’re just going to carry on.

The next thing I want to do here is,

one of our participants in the previous webinar

asked me about a base station correction.

Now, generally off shore, we’re not running a base station

because we can’t get one close enough to our survey area

because the base station needs to be stationary, right?

There are some marine base stations, but they’re few,

and they’re few and far between let’s say.

The base station is not really generally done.

With this dataset, since we’re in Hawaii,

there is actually a magnetic observatory really nearby,

really close to the survey area.

And so just for the purpose of this exercise,

I’m going to run the base station correction

so that you can see how it’s done.

And so, actually, there is no base station tool

in the UXO Marine menu.

And that’s actually why I gave you the UXO Land tool.

Because if you go to Data Preparation for UXO Land

and you go to Data Corrections,

base station is the first correction that you’re going to do.

And so it is a lot more common

to see this correction done on land in UAV drone surveys,

or just land-based magnetic surveying.

All right, so we’re going to click this file, this tool.

And it’s looking for a couple of things here.

So first of all, it’s asking us for our survey database.

So that’s the only database we have at the moment,

so it’s Hawaii.gdb.

The date channel is just called date, time is called time.

And then it’s asking us for the input channel,

which is the mag channel that we want to actually correct.

So we’re going to use mag edit.

And you can actually save the base station.

So the base station file right now is a text file

that you should have in the zip file that I uploaded.

We’re going to go to base station.

So we’re going to load that base station file.

This is Honolulu, this is the date.

The magnetic observatory measures the field every minute,

so we have a once-per-minute reading.

You can click on this text file.

And then what you do is you select the first line

and then from the dropdown, you can tell it

which channel matches these fields, required fields.

So the mag-based field is actually this F.

Hon is for Honolulu field, I think.

So it’s at this Hon F.

The time field is just the time channel.

Date field is the date channel.

It’s asking us for the date format,

so that’s an that’s in year, month, day.

Now, this base station tolerance,

if your contract has a specification,

for example, for some surveys that says,

“You’re not to survey if the base station is reading,

if it’s changing two nanoteslas for every five minutes.”

So that could be one of your specifications.

So what this is asking us actually is,

“What is your tolerance in the contract?”

And it’s the unit is nanoteslas per minute.

So you’ll have to just work out to be what the…

If it says two nanoteslas per five minutes,

you just need to work it out what that would be per minute.

You put your tolerance in here,

and it will actually flag your data

where you shouldn’t have been surveying

because the base station tolerance is out of spec.

So this is actually a really nice simple step.

This saves you from having to import the base station

as a separate database and processing that.

So this should save you a lot of time.

It’s a really neat compact tool that does it all for you.

It also D-spikes your data.

So there is a filter here

that will get rid of all of the spikes of the database.

And that can happen

if you have somebody checking on your base station

while you’re surveying.

Often, when that person comes near,

if they have anything metallic on them,

you can see a little spike in the base station data.

So this tool will actually get rid of those spikes

so that you don’t…

Again, so it just saves you from having to do any processing

on the base station data.

And that’s it, so it should match everything up,

and it should give us…

Because we selected Save Interim,

we can see what the base station readings were

before it actually subtracted it from our survey data.

So let’s click OK.

And it’s going to run the correction.

And it’s giving us the mag edit base station corrected data.

And if we just load the hidden channel here,

this was the actual base station data.

So what it’s basically done is just subtracted

the overall base station reading from our survey reading.

And it’s left us with something

that looks a little bit like a residual,

although in this case it’s still quite a large number.

So the next step that we would do here

is a long wavelength removal.

But actually, just to see that difference,

let’s pause here and actually grid these results.

So I’m going to go to Grid and Image, Gridding,

Minimal Curvature.

We’re going to select our base, or diurnal corrected data.

And generally I just copy and paste that into my output.

And this is where we can actually select 2.5 meters

because that’s 1/4 of our line spacing.

Now, if you wanted the gridding

to actually reflect your footprint of your system,

you can adjust the blinking distance here.

So what I mean by that is,

if you’re doing something like a reconnaissance survey

where your lines are actually very far apart,

but you know that you only have a maximum detection range

of something like five meters,

you might only want to see a five meter swath

on either side of every line.

So you can put five meters in here and that will limit,

let’s say, the distance away from the line

that you’re greeting the data.

I’m going to use six meters in this case,

because there’s about a six-meter detection range.

They were flying at an average of four meters

above the sea bed,

and they needed to clear two meters below the seabed.

So the total detection range below the magnetometer

is about six meters.

And we know that on the surface

it’s a bit of like a semicircle.

So if it’s six meters below,

it’s six meters to either side as well.

We can set a six meter blinking distance,

so we’re going to get a total swath of 12 meters

for every line of data.

I’m going to click Finish.

So that’s given us this initial grid.

This is just a grid window, so you can see it has this GRD.

We can just close that.

I’m going to click on my map.

From the project explorer, I’m going to expand the grid layer.

I’m going to drag and drop my grid onto the map.

And then I’m going to use

just this Zoom to Full Extents button.

And that’s our first grid.

So I’m going to just turn off the line path.

So you can see that actually,

if they had a six-meter detection range,

they probably needed a little bit more coverage

in this dataset.

In reality, they probably had a much bigger detection range,

which is why this data was accepted and it’s actually okay.

But that’s fine, we can leave it like this.

This is actually really normal.

You will often see gaps in your data.

You will sometimes see gaps in your data and it’s real.

So that’s something you need to consider.

This can be areas where you can plant infills,

where you’re going to re-fly and collect more data

to fill in these gaps.

But what we’re seeing in this grid is a long wavelength.

So what we’re interested in

are these small discrete dipoles.

But what we actually see is this big, long wavelengths.

So you can see there’s a high on the left-hand side,

on the Western side of the grid,

and then the Northeast there’s this low.

This is part of a larger wavelength

that could be caused by geology

or something that’s just buried a lot deeper.

The next obvious step

is to remove that long wavelength from the data.

And that’s going to really bring out

and highlight these small discrete objects.

So let’s go back to our database,

and we’re going to run a background removal.

So if you go into the UXO Marine mag menu

and go to data corrections,

we’re going to do the background removal.

Now, the purpose of this background removal is, like I said,

to get rid of that long wavelength.

So we’re going to load in the base station corrected channel,

and we’re going to call it,

mag edit underscore base underscore background.

We’re going to do this in a couple of steps

so that you can see what the correction is

that we’re actually performing.

So I’m going to start with a nonlinear filter,

and I’m going to actually…

50 fiducials in this case works really well,

but I’m going to increase my tolerance

to about 10 nanoteslas.

And you’ll see the results in a minute

once we actually run this.

And that’s it.

So we’re just looking at the background first.

We’re trying to get an idea for what that really looks like.

So then I’m going to display the new channel.

So again, we’re going to right click on a number,

click Show Profile, and we’re going to look at this.

This is the actual background value

that we’re going to subtract from the original data.

And this is a good example here.

So what it’s done is,

everywhere where the green line matches the red line,

once we subtract the two, this is going to become zero.

And that’s really what we’re looking for.

We’re trying to isolate what we think are UXOs.

So over here on the left-hand side,

we have a really nice dipole.

So this is definitely something

that’s going to show up really well

after we remove this background.

And everywhere else, it’s just going to become zero.

And that looks okay.

On this line, same thing.

None of these really look like you UXOs,

but this could potentially be one.

These ones are probably a bit small and a little bit wide,

but after we subtract the green from the red,

we will be left with something that we can look

to see if it actually matches

what we’re looking for in our objects.

Now, the only thing is that this line,

because of the 10 nanotesla tolerance, is very noisy.

We’re going to run this again.

And actually, if you right click on the last channel,

you can re-run it from the right click menu.

So after we run this non-linear,

we’re going to run a baseline,

and that’s actually going to smooth the results for us.

So we’re going to run this at 0.8 smoothness and 0.2 tension,

and I’m going to click OK.

And it’s actually going to overwrite it,

so we should see right away the results

in our display channel.

There we go.

So that looks a little bit better.

So that second filter has really smoothed our results.

Now, one setting, one background calculation

will not always work for all lines.

So you do need to look at this really carefully,

and you’re going to see some that don’t look as nice.

For example, here, are these really UXOs?

We’re going to be left with small anomalies,

and you can see that it didn’t really draw a straight line

through them as we’d expect, or as we want to see.

So this is not a great fit.

And so I might actually use my line selection,

Select None, and then re-select just this line

and try to run a background correction

that better fits this individual line.

So this is a really, really important step

and it requires a lot of attention.

Unfortunately, there’s not really a faster way

that I know of at the moment.

It is what it is.

You just have to spend time on each line

and make sure you’re getting the best background removal

that you can get.

Like this one, this one’s not bad actually.

This is doing a pretty good job all the way along.

Yeah, this is okay.

For this workshop, we’re just going to leave it,

but in reality,

you will probably need to run more than one calculation.

So just be aware of that.

For example, like here, this is a really bad one,

because you’ll see that if we subtract

the green from the red,

it’s really going to cut short this anomaly and make it…

It’s going to give us two positives and a negative.

But really, I would expect this green line

to go across the base of this anomaly here.

The 50 probably wasn’t wide enough and we’d need to make it,

this might be like a 16 or a 70 width.

So we would rerun that background on this line

with a wider width.

But again, just for today, we’re going to accept it.

It looks pretty good on most lines.

It’s not perfect, but we’re going to move on.

So what we’re actually going to do now,

we’re going to go back to that same tool

and we’re going to click this button at the bottom,

which is Subtract the Background From Your Input.

And we’re going to change the output name to Residual.

So now we have an edited base

corrected residual mag channel.

And what you should see if we open a second profile window

is that it’s really centered around zero

except where we saw a difference

between the green and the red.

On some lines we’re left with these little anomalies,

and these probably are not UXO,

but we wouldn’t pick them when we do our target picking.

It’s fine that they’re there,

but we know that they’re probably not a UXO-like object.

This is one, this isn’t bad.

This might be actually picked

because it has a very big negative anomaly, negative dipole.

But yeah, so you can just kind of look through this

and see what the results look like.

Now that brings us to the last step,

which is picking targets.

So let’s grid this residual channel

and see how it compares to the other gridded image.

So we’re going to go back to Grid and Image, Gridding,

Minimal Curvature.

I’m going to grid the residual.

And again, I’m just going to copy and paste that

into my output.

I’m going to use the same cell size

and the same blinking distance.

And I’m going to, again, just close this

and I’m going to drag it onto my other map.

I don’t like looking at it with this color scale,

it’s showing a lot of noise.

So what I’m going to do

is I’m going to click on that grid in my map manager,

and I’m going to click the color tool,

and I’m going to use a normal distribution,

but I’m going to set the mean to zero,

so that means this yellow color

will be right on the zero mark,

and I’m going to increase my standard deviations.

I’m going to select something like 25.

And that means that really what I’m going to see

when I click OK here are just,

the high values are really going to stand out.

So these are the ones that I consider to be more UXO-like.

It’s just a really nice way of getting rid

of a lot of that very low-level noise in the data.

So now we can actually see

where some of these nice dipoles are

and what we actually might consider as UXO

or UXO-like object.

So from this, we can actually pick targets

using the dipole method.

We’re going to go to the UXO Marine mag menu,

and we’re going to click Pick Targets, Pick Dipoles.

No, it’s Find Magnetic Dipoles.

So we’re going to give it the input grid,

so that’s our residual.

And it’s asking us for a minimum positive peak.

Now these values will be different for every survey,

depending on what your height above the ground is

and what the object is that you’re looking for.

And really the only good way I have of determining this

is to do your surrogate item test.

And that’s where you put the object on the seabed

and you fly over it at different heights

before you start your survey.

And that’s because if you have a desktop study

and you know approximately what you’re looking for,

you can try to find an object

of the approximate same value.

And then at the different heights,

you can really see what the magnitude

of your anomaly will be.

And that’s going to help you decide

what these target picking parameters are.

And so that’ll be very different for every survey

and for every area based on the items

that you’re looking for

and based on your background values.

So if you’re in a very magnetically noisy area,

like I think the Baltic Sea

is a lot noisier than the North Sea,

you might need to fly a lot closer to the seabed

because you need your UXO to stand out

on top of the noise levels.

So again, those surrogate item tests,

you don’t just fly over the item,

you do background readings as well.

So you’re going to fly over a line where there’s no item,

and then you’re going to put the item down

and you’re going to go over it at different heights.

And that’s going to show you what the background levels are

and what it looks like with the object.

But anyways, for this survey,

we’re going to pick a minimum peak of 10 nanoteslas.

So what it does is it searches for the positive,

and then you give it a search radius in distance,

like in meters, around that positive

that it’s going to look for the negative.

So here, we’re going to put 25 meters.

And we’re going to save this in a new target database.

We’re going to call it Dipoles.

And then it’s going to create a dipole amplitude channel.

So this is the peak-to-peak value,

so from the negative to the positive.

And if we actually tell it what our survey database is,

it’s going to find the location of the target

on the closest line in our survey database.

So I really like selecting that option.

It’s not required though.

And then let’s click OK.

Okay, so here are the results.

And unfortunately it does change the colors.

There’s a little bug there that we need to fix.

So we’re going to put that back to zero and 25.

And you can see where it’s picked our dipoles for us.

So if I just zoom in on an area here,

you can see that it’s picked these dipoles.

So it’s showing you the black cross is the inflection point.

So that’s actually the location of the target

below the dipole.

And then it’s picking the most positive

and the most negative peak surrounding that.

So you can move around and you can inspect your results.

You can check that they make sense,

or if you need to tweak your parameters a little bit.

In the target database here,

you will get the location of the black cross,

so that’s the center of the dipole.

You’re going to get that dipole amplitude.

So that’s the peak-to-peak value.

You also get a length.

You get the closest line to that location.

So that’s from your survey database.

The distance along the line where it’s found,

and then the fiducials of the actual row it’s on.

And then we also give you a lot of information.

You also get the location of the positive peak,

the location of the negative peak.

But that’s it.

So that’s really all we have time for today.

I hope that was useful.

I’d really appreciate any of your comments or feedback.

And again, just to remind you,

you have your evaluation license for two weeks.

I’ve shared this dataset with you,

and you should be able to find this recording online

in a couple of days.

I’d say, give it at least a day and then check.

I don’t know when we’re going to get it up,

but we won’t wait too long.

And if you have any problems,

you can contact me directly,

or you can email [email protected].

We’ll be around afterwards.

Gretchen, Bart and I will be around afterwards

for any questions, but thanks very much.

<v Gretchen>Thank you, Becky.</v>

That was a really good training.

I personally enjoyed it.

I’ve had data I’ve had to process with Oasis montaj before,

and I wish I’d had you there to give me a hand.

I just wanted to mention that Geometrics and Seequent

are inviting you to be part of our early adopter program

to try out Oasis montaj Field for free for three months.

This special goes until April 29th.

It’s a free license to any Geometrics customer

who would like to try out the newest software offering.

Oasis montaj Field is a user-friendly prototype

that will still enable you

to visualize and perform on the spot quality control tests

or collected magnetic geophysical field data,

all within at the Oasis montaj environment.

It’s designed for people who are in the field

and aren’t looking to be weighted down

with every feature Oasis montaj offers,

but really those features that are special to them.

All right, thank you.

<v Becky>Thanks Gretchen.</v>

I see there’s a couple of people with their hands raised.

I’m not sure you’re going to be able to unmute yourself,

but if you want to type your question

in the question box.

So I think I see one now.

Let me look at that.

Sorry, one second. (giggles)

Right, okay.

So the first question in the chat was:

You chose UXO Marine Grad and UXO Marine Mag,

but is there any module for utility detection?

We don’t have a specific utility detection tool.

However, the picking targets that we did,

they won’t just work for discreet objects.

For example, if you run…

I used the dipoles, the dipole picking option,

but if you calculated an analytic signal

and used the Blakley method,

you can actually pick things that look like pipes.

There’s a couple of different settings

where you can pick discrete objects or you can pick ridges.

So if you see a ridge or a linear feature

in your magnetic data,

there is an option as part of the UXO target picking

that will let you pick those linear features.

And so that’s really what you can use

for cables and pipelines.

I’m not sure if there’s any other utility

that you’d be looking for.

I think we’ve actually been discussing

renaming UXO Marine UXO Land,

because the same tools can be applied for archeology,

for utilities and other things.

So it’s basically the same tools,

UXO Marine can be used

for any offshore near surface investigation, let’s say.

Okay, there’s another question here

about the altitude correction.

So the new platform, observation, altitude,

what value should be taken

for a very unstable altimeter values?

Yep, so that’s actually something

I didn’t really have time to get into very much.

We did a base station correction,

and we did a background removal,

but there is another tool

which will do an altitude correction.

If you have a really unstable altimeter values,

I would definitely run the altitude correction.

And then the new altitude that you use going forward,

so if you’re going to be calculating depths from that data,

all of your depths

would hang off of that new corrected altitude.

So you’d be correcting your altitude to a constant.

So if you said four meters,

that four meters becomes your new altimeter value

for the whole dataset.

Basically, once you do that altitude correction,

you’re kind of getting rid of the other altitude channel.

I hope that answers your question.

Another question here.

Is it possible to calculate depth

for discreet object or utility?

So, yeah, so again, we do have a couple of tools.

We have Euler deconvolution,

which will do depth to a discrete object or a pipe.

Again, the Euler deconvolution

uses something called the structural index,

and there is a structural index for linear objects.

So you can pick a structural index

for a pipe or a barrel.

So there’s a couple of different ones that you can use.

We also have something called potent queue,

which is a bit like an inversion style depth calculation.

And that’s also really good for pipes and cables.

And then, okay, another question here.

Although we didn’t cover Blakley method today,

I was wondering if there’s an easy way

to merge the target list by target locations

obtained from both the Blakley analytics signal

and magnetic dipoles.

It’s a really good question.

We do have a merge tool right now,

and I agree it’s not the greatest.

And it’s something we’re working on

for the next release.

So in the spring release, I believe,

we should have a new merge feature.

So I would say, hold on for now.

Let’s come back to that question.

There’s actually, well,

I know this was from somebody who uses UXO Marine.

There is a merge tool in UXO Land.

So while you have UXO Land for a couple of weeks now,

you could look at the merge tool

that’s available in UXO Land

’cause it’s a little bit better.

It has a couple more features.

So I think it might do a slightly better job

than the UXO Marine merge tool.

But we’re looking at ways also

where you could bring in something like a target list

from side scan sonar,

and you could cross-reference your targets

with your magnetic targets.

So this is something that we get asked a lot

and it’s something we’re trying to improve

how it currently works.

We have a few more minutes, so I’ll just keep going.

Questions are coming in fast and furious now.

How would you discriminate the autopicked target for UXO?

Yeah, so that’s another really…

That’s a hot topic, target discrimination.

So from magnetic data alone,

it’s really difficult to discriminate what you have.

So we don’t have a library

of magnetic signatures, for example.

If you were using EM, an advanced EM system

like the MetalMapper on land,

we have a library of signatures

that you would match the EM’s signature to.

And you can actually get a much better idea

on what’s clutter, or what’s garbage,

and what’s actually a known UXO.

With magnetics, we don’t provide you a library

because it’s too difficult.

We don’t have a list of what the signature looks like

at specific depths for specific UXOs.

I know that some people out there have been working on this,

and there’s a couple of third-party tools

that using magnetic moment and the depth and height

and et cetera, they do a bit of a better job.

So I think that’s an area

where you might just keep your eyes open

for new developments,

but at the moment we don’t have any discrimination tools

in Oasis montaj.

All that we can say

is that there is something magnetic there

and depending on how sharp it is and how big it is,

it could be a UXO.

Okay, another question.

The mag data was in the range of about 35,000,

but after the base station,

you plotted the difference of actual mag

and it was around 500.

Was that the corrected magnetic field?

So, yeah.

So our survey was reading around 35,000

and the magnetic observatory was around 34,500.

So when we subtracted it,

it left us with a residual of about 500.

I’m not really used to working so close to the equator.

I usually work in the 50,000 range up in the North Sea,

but yeah, we subtracted the actual,

the full values and that’s what it gave us.

So I hope I got the correct…

I did download it really quickly the other day

from the observatory.

It might be worth,

I don’t know exactly how far the observatory is

from our survey area.

And if we had actually put a base station

closer to the survey area,

we might’ve gotten slightly more accurate,

but I don’t think that that’s unusual.

But yeah, that is the corrected field.

And then after that we took the long wavelength removal

to get it down to zero.

Okay, another question.

I don’t know if we’re going to be able to answer

all the questions today,

but I will email you a response

if we don’t get to your question right now.

I think I’ll take probably just one more.

Here’s one.

What does it constitute to be a Geometrics customer?

I think that there’s actually…

What we’ll do, we’ll send a follow-up email

with the link to where you can sign up

for Oasis montaj Field.

And then I don’t know what checks they’re doing,

but you can register for it and see what happens.

And then there was a question here about the data.

Was it UXO total-field or gradient?

And this was a single magnetometer, but to be honest,

just because of the time we had today,

I took one magnetometer out of a TVG frame.

I can share afterwards if you’re interested,

the full dataset,

and it actually consisted of two magnetometers.

And that’s probably why we saw some gaps

in the gridded data,

because there really was another set of lines.

We didn’t have time today

to look at the full gradient processing,

that’s a much more involved processing sequence.

So I took just a single total field magnetometer

and showed you the workflow.

But to be honest,

that survey is actually a gradient survey

using the TVG frame and two G-882s.

You can find that data with the two magnetometers,

if you wanted to play with that

and try to process the full gradient.


So I think that’s all we have time for today.

Thank you so much for your questions

and for coming to one or all three of them,

if this is the third one that you’ve watched.

The recordings will be available

on the Geometrics YouTube channel,

as well as on the Seequent community video page.

I’ll talk to our marketing department

and we’ll try to get it up tomorrow

so that if you wanted to replay this one with the data

and your evaluation license,

you have the full two weeks.

Your licenses will expire two weeks from yesterday.

So you have two weeks minus a day.

All right.

So thanks again and enjoy the rest of your day, everyone.