[GRASSLIST:3887] Re: Geophysics White Paper, 1st Revision

[Benjamin Ducke]

Being an archaeologist, my ideas about geophysics are certainly
very limited. I basically need functionality that enables me to
quickly get clear visualisations of built structures that are not
very far below ground. In my work, I cover areas of rather limited
extent (say a few hectares) with off-the-shelf equipment (gradiometer,
caesiometer) and lots of measurements.

I realise that people who work in, say, exploration may have quite different
needs.

Because of this, I am especially interested to know whether the
system I outlined in the white paper would suffice for other fields as
well AS A LOW LEVEL BASIS.
I guess that, to compete with commerical products, there would
have to be a lot more high-level functionality, e.g. for visualising and
analysing cross sections, 3D visualisation etc.

So, maybe your company will contribute?

Cheers,

Benjamin 

On Tue, 13 Jul 2004 10:56:42 -0700
"Syd Visser" <sydv at sjgeophysics.com> wrote:

> Benjamin
> 
> i haven had time to figure out how to put answers on the list so i am
> answered to you directly. Hope that is ok.
> 
> I have been trying to put in my 2 bits for some time now but we are finaly
> (after about 10 bad years) extremely busy. We are very heavily involved in
> doing the data collection, processing (including 3D inversion on our 24 node
> cluster) and interpretation of non seismic data (airborne and ground
> magnetic, gravity, resistivity, Induced polarization, airborne and ground
> electromagnetic).
> We are using grass to do some geophysical data processing and are very
> interesting to adding to it.
> 
> Instead of writting a note at this piont may suggest you look at two web
> sites of commercial software who specialize in geophysical software to get
> some ideas.
> 
> http://www.geosoft.com/
> 
> http://www.encom.com.au/
> 
> I hope to find time later in the year to get our company more involved with
> this project.
> 
> an answer to one of your questions is that airborne data is usually
> collected in long, lat coordinates due to zone boundary problems with xy
> coordinates but plotted using xy coordinated.
> 
> 
> Syd
> 
> 
> 
> 
> 
> 
> 
> We have had serious problems with email delivery therefore we have added a
> request for a delivery receipt.
> Thank you for replying
> 
> ///////////////////////////////
> Syd Visser P.Geo
> SJ Geophysics Ltd.
> sydv at sjgeophysics.com
> www.sjgeophysics.com
> ----- Original Message -----
> From: "Benjamin Ducke" <benducke at compuserve.de>
> To: <grasslist at baylor.edu>
> Sent: Tuesday, July 13, 2004 10:12 AM
> Subject: [GRASSLIST:3883] Geophysics White Paper, 1st Revision
> 
> 
> > To everyone interested in GRASS 5.7 geophysics applications:
> >
> > Please find attached the latest revision of the white paper
> > that describes the to-be-developed GRASS 5.7 geophysics framework.
> > It took quite some time for this update to happen, but I decided
> > to overhaul and simplify basically everything.
> >
> > Those of you who have read the first version of the document should
> > find everything easier to understand, less overloaded with terminology
> > and generally untangled.
> >
> > These are my suggestions on how to proceed from here:
> >
> > 1. check and improve white paper:
> > - spelling and other mistakes, legibility
> > - any fundamental changes necessary?
> > - anything that would appear flawed/not to work by design?
> >
> > 2. Complete white paper
> > - make a list of filter functionality
> > - additional functionality needed?
> > - have the white paper reviewed by external peers
> >
> > 3. Start coding!
> > The following things could be coded in parallel:
> > - raster data filters
> > - tcl/tk GUI for selecting filters and parameters
> > - tcl/tk GUI for creating colour ramps
> > - modules for data import etc. as outlined in the white paper
> > White paper should be turned into regular documentation and completed
> > in the process.
> >
> > So, who has got some idle time to spend on these things?
> >
> > Michael: I tried to merge most of your ideas with mine. Hope you can
> > live with the result.
> >
> > Craig: I put your description of data corrections into the white paper
> (sec. 3.2).
> > I think, there would be need for the same thing regarding standard
> > filters, like high pass, low pass, destriping etc. (sec. 3.1).
> > We also need some thoughts on how to handle the filter list using XML.
> >
> > I have put both your names on the author's list. Maybe you would like
> > to also add institutions and e-mail addresses?
> >
> > Hamish: I hope the 'd|v.survey.grids' module addresses the field sheet
> functionality
> > you were asking for
> >
> > Cheers,
> >
> > Benjamin
> >
> 
>