Dear
List,
It
seems like a good time for an update on a GX sharing vehicle as per a
previous series of emails on [geonet].
The
good news is that we are currently building the "GX Exchange" -- a
repository for submitting and accessing GX functionality from the Geosoft
community. It should be ready in several weeks after going through testing
and so forth.
In
designing the exchange, we decided to make this a resource for submitting
and retrieving source code -- rather than compiled GXs. The reasoning is
that we wanted to help protect the community from unpredictable
GXs or GXs containing viruses, etc.
We also considered having users
submit compiled GXs and then testing all of the GXs inhouse. However, we
quickly ruled this option out because it would mean that our testing group
would have less time for testing Oasis montaj.
When
the new facility is up and running, the process will be to submit GX code.
Each user who wants to access this functionality will then compile the GX. We
strongly recommend that users verify the source code before compiling and
running the GX as Geosoft cannot assume any liability for the proper functioning
of code.
There
may be a little bit of a learning curve for some users who have not used the GX
Developer before but we will provide links to GX compiling documentation to
facilitate this process. We will also let you know how to access the GX
Developer which is already included as part of Oasis montaj.
Will
let you know when all is ready,
Greg
P.S.
Thanks to Brian Appleby for providing us with the information on GNU licensing.
This was a big help!
-----Original Message-----
From: David Humphrey [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 27, 2001 11:25 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [geonet]: Large ascii data sets with no header or channel nam esUnless someone has a way to do this already using existing Oasis facilities, I would write a program (since I'm a programmer). This is a natural application for a perl or python script. For one experienced in one of these languages, this is a half-day type of project. Rather than transforming the header into another header, one might just as well go ahead and import the data directly into a new Oasis database. That being said, sorry, I don't have any code to offer. This is a good one to add to the Oasis request list.Regards,David L. HumphreyManager, Software DevelopmentBell Geospace, Inc-----Original Message-----
From: Ballantyne, Todd [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 27, 2001 10:06 AM
To: Geonet [Geosoft] (E-mail)
Subject: [geonet]: Large ascii data sets with no header or channel namesDoes anyone have a GX or suggestion for converting a "typical" "Geoterrex" listing of column names (in a readme.txt) into a Geosoft "i3" import template. For airborne data sets it can be a very tedious process to create an i3. My current need is to import a data set with 140 data columns containing no header of column names.EXAMPLE OF README.TXTPARAMETER CHARACTERS CONTENTS1 1-10 X (METRES)
2 11-20 Y (METRES)
3 21-30 FIDUCIAL (SECONDS)
4 31-40 FLIGHT NUMBER
5 41-50 RADAR ALTIMETER (FEET)
6 51-60 BAROMETRIC ALTIMETER (FEET)(( deleted remaining channels))EXAMPLE OF i3 FILE./ Wizard Generated Template for .\[IMPORT ARCHIVE]
FILEHEADER 0
RECORDFORM DELIM," \t","","","\""
SKIPSTRING "/"
LINENUMBER 4,6,NORMAL
DATA 0,9,NORMAL,,,,
CHAN X,DOUBLE,NORMAL,9,1,LABEL="X"
DATA 1,10,NORMAL,,,,
CHAN Y,DOUBLE,NORMAL,10,1,LABEL="Y"
DATA 2,10,NORMAL,,,,
CHAN FID,DOUBLE,NORMAL,10,1,LABEL="FIDUCIAL"
DATA 3,10,NORMAL,,,,
CHAN FLT,DOUBLE,NORMAL,10,1,LABEL="FLT_NUM"
DATA 4,10,NORMAL,,,,
CHAN RAD,DOUBLE,NORMAL,10,1,LABEL="RAD_ALT"
DATA 5,10,NORMAL,,,,
CHAN BARO,DOUBLE,NORMAL,10,1,LABEL="BARO_ALT"cheers, todd.Todd A. Ballantyne, P.Geo.
Geophysicist
Ashton Mining of Canada Inc.
=><=><=><=><=><=><=
email - [EMAIL PROTECTED]
tel - (604) 983.7750 ext. 255
fax - (604) 987.7107
