Import Static Sensor Data (CSV)

Use the Import Static Sensor Data (CSV) option (Geosoft.uxo.gxnet.dll(Geosoft.GX.UXO.UxaImportAdvancedSensors;Run)*) from the AGC Expert User > Static Data Prep and QC menu to import raw data from advanced EM sensors, collected in static mode, into a Geosoft database. 

Import (CSV) Static Sensor Data dialog options

Master database prefix

Select the optional master database prefix.

Script Parameter: UXANALYZE.MASTER_IMPORT_DBPREFIX

Group

Select the group in the master database.

Default group name is FlagList.

Script Parameter: UXANALYZE.MASTER_GROUP

Geo/Grid ID

Specify the Geo/Grid ID, or select from existing values in the Target ID channel. The ID can be an alphanumeric value up to 32 characters in length.

Script Parameter: UXANALYZE.GEO_ID

Input file(s)

Select the input CSV file(s). Each input file is imported into a separate group/ line in the survey database (_Data).

The dialog supports importing data from CSV format.

Script Parameter:UXANALYZE.INPUT_CSV_FILES

Data type

Select the data type. The data type will be included in the database name. For more information on the data types, see the Data Types help topic.

Script Parameter:UXANALYZE.DATA_TYPE

Sensor/configuration

Select the sensor and configuration used to collect the data. The default values are read from the sensor configuration table; refer to Application Notes below.

Script Parameter:UXANALYZE.SENSORNAME

Sensor ID

Specify the Sensor ID, or select from existing values in the Sensor ID channel. The ID can be an alphanumeric value that will identify the sensor used to collect the data.

Script Parameter: UXANALYZE.SENSOR_ID

Height above ground

Specify the height (in meters) of the EM sensors above the ground surface, which has a minimum value of 0. The following default values are read from the sensor configuration table:

  • TEM2x2x3: 0.20 m
  • MetalMapper: 0.16 m
  • MetalMapper2x2: 0.26 m

Script Parameter:UXANALYZE.SENSORHEIGHT

GPS antenna offset (m)

Specify the GPS antenna offset, which is the offset between the GPS antenna and the EM sensors. The default values are read from the sensor configuration table; refer to Application Notes below.

The GPS antenna offset is used to calculate the sensor coils coordinates.

Script Parameter:UXANALYZE.GPSANTENNAOFFSET

Location ID

Select the Location ID from the file header, or from the file name.

If Location ID is to be extracted from the file name, the name should follow A_B.csv pattern, where A and B are alphanumeric and numeric characters, respectively.

Script Parameter:UXANALYZE.LOCATION_ID

GPS coordinates

Use the Edit button to change the GPS coordinate system. The System and Unit text boxes will be populated with the selected coordinate system.

The default values are:

  • Datum: WGS 84
  • Projection: Geographic (Longitude / Latitude)
  • Unit: degrees.

Script Parameters:UXANALYZE.DATUM_GPS, PROJECTION_GPS, LOCAL_TRANSFORM_GPS, UNIT_GPS

Projected survey coordinates

Use the Edit button to change the projected coordinate system for the survey. The System and Unit text boxes will be populated with the selected coordinate system.

The default values are:

  • Datum: NAD83
  • Projection: UTM
    • The UTM zone will be automatically determined when a new input file is entered. If latitude and longitude are missing from the input file, the dialog will look for UTM_E, UTM_N, and UTM_Zone data to determine the UTM zone. If not successful, it will be replaced by "?" for the user to define it manually.
  • Unit: metre.

Script Parameters:UXANALYZE.DATUM_PROJECTED, PROJECTION_PROJECTED, LOCAL_TRANSFORM_PROJECTED, UNIT_PROJECTED

Magnetic declination

Specify the magnetic declination. The value of magnetic declination is added to Yaw when calculating the location.

There is no default value unless IGRF has been calculated. IGRF will be automatically calculated using the location information from the first file imported.

The field is disabled for TEMTADS sensors.

Script Parameter:UXANALYZE.DECLINATION

Database prefix

Specify the prefix for the names of the sensor (_Data) and target (_Target) databases. By default, your databases will be saved in your current project folder. The output database names are displayed below.

Script Parameter:TARGETGDB

Target group

Specify the target group name, which can be a new group.

The default Target group is named, Targets.

Script Parameter:UXANALYZE.TARGETGROUP

Application Notes

The advanced EM sensors collect a massive amount of data that can be exported into a text (CSV) file. When imported into Oasis montaj, the data are read and saved into a pair of Geosoft databases. There are two databases, a survey database (_Data) that contains the raw sensor data, and a target database (_Target) which contains the target and header information.

A third database (_Source) is created when inversion and modelling are performed on the data, and it is used to store the modelling and classification results.

Each input file will be imported as separate groups in the sensor data database (_Data). The target information and the header or parameters are imported into the target database (_Target).

A range of files can be selected to be imported at once, however, only files of the same data type should be selected to be imported simultaneously.

Dates are assumed to be in the US short date standard of MM/DD/YYYY. The tool is designed to create projected coordinates from the GPS coordinates found in the input files. The GPS coordinates are detected by looking for columns that start with LAT (for latitude) and LON (for longitude). If found, the projected channels are named UXA_Y_Raw and UXA_X_Raw.

Examples of Static Sensor Data (CSV) Headers

During the Import Process:

  • For each input file a unique Target ID is created.
  • The locations of each of the receiver coils in projected coordinates are calculated from the GPS (geographic) coordinates of the array found in the input files. The GPS coordinates are detected by looking for columns that start with LAT (for latitude) and LON (for longitude).
  • The IMU (heading/yaw) data are corrected from magnetic declination.
  • If the current data values are present, the sensor data are normalized to the maximum current.
Master Database

In the master database (if selected), the following channels are created if they don't exist:

  • UXA_Measurement_Number
  • UXA_ACQ_DATE
  • UXA_ACQ_TIME
  • UXA_CSV_FILE
  • UXA_SensorID

As each data file is imported:

  • Read from the master database:
    • the measurement number (UXA_Measurement_Number): increment and use for the measurement id
    • the flag locations (UXA_Flag_X and UXA_Flag_Y)
  • Write to the Master database:
    • Update the measurement number (UXA_Measurement_Number)
    • Store the UXA_ACQ_DATE
    • Store the UXA_ACQ_TIME
    • Store the UXA_CSV_FILE
    • Store the UXA_SensorID
Geo/Grid ID

The Geo/Grid ID can be any alphanumeric value up to 32 characters in length and is intended to clearly define individual grid areas. The Geo/Grid ID is identified in the group/line name in the survey database.

Target ID

The target ID (for example, "01_001_01") is made up of three parts;

  1. The location or flag ID, which is numeric and can be populated from the file header or the file name. If Location ID is to be extracted from the file name, the file name should follow A_B.csv pattern, where A and B are alphanumeric and numeric characters, respectively.
  2. The measurement ID, which is numeric and comprised of three digits and is automatically populated with sequential numbering. If the location ID already exists in the output databases the measurement ID will automatically increment to the next available number.
  3. The source ID, which is comprised of two digits and is populated based on the targets source ID.
Sensor/Configuration Table

The sensor configuration table is a lookup file containing information about the sensors and configuration, such as the relative location of the sensor coil, number of gates, etc. The default sensor/configurations are:

  • MetalMapper: static, standard configuration (8msec and 50 gates)
  • MetalMapper B: static, long time window configuration (25msec and 60 gates)
  • TEM2x2x3: static, standard configuration (25msec and 121 gates)
  • TEMTADS: static, standard configuration (25msec and 121 gates) raw data
  • TEMTADS B - Processed: static, standard configuration (25msec and 121 gates)

You can modify the parameters for the existing sensors or add new sensors to the file. The file "SensorTableAdvanced.xml" is located in the "C:\Program Files\Geosoft\Desktop Applications \etc" folder.

  • If you want to customize the SensorTableAdvanced.xml file, you should manually copy the file to your "%USERPROFILE%\Documents\Geosoft\Desktop Applications \etc" folder (so that you don't lose your changes during a software update).
  • If the Magnetic declination and/or the offset between the GPS antenna and the sensor coils have already been accounted for, prior to importing the data, you should enter zero (0) in the respective fields.
  • *The GX tool will search in the "gx" folder. The GX.Net tools, however, are embedded in the Geosoft.uxo.gxnet.dll located in the bin folder. If running this GX interactively, bypassing the menu, first change the folder to point to the bin folder, then supply the GX.Net tool in the specified format.