Export to Geosoft Oasis Montaj Database

GeoHammer is not meant to replace full-blown geophysical packages like Oasis Montaj, Prism2 or Geolitix — but a survey rarely ends in GeoHammer either. Once the data has been filtered, cropped and checked, it often needs to be handed off to Oasis Montaj for gridding, levelling, or any other processing that GeoHammer itself does not offer. The Export as Geosoft (Oasis montaj) database script closes that gap: it writes the currently opened CSV file out as a Geosoft .gdb database that Oasis Montaj can open directly.

Since the script declares the csv wildcard in its template, it appears in the Scripts drop-down for any opened CSV file, regardless of the sensor it came from.

Note: this script only runs on Windows, and only on a machine where Geosoft Oasis Montaj (or the Geosoft Desktop Applications runtime) is installed — it relies on Geosoft's own geosoft.gxpy Python API to actually write the database.

Workflow summary.
The script uses the opened CSV file and turns it into a Geosoft data line:

• Selects the channels: every column pandas recognizes as numeric is exported as a channel; text columns (names, statuses, timestamps stored as strings) are skipped, and the log lists what was skipped.
• Projects the coordinates: if the file has Longitude and Latitude columns, they become the X/Y channels and are reprojected from WGS84 into the UTM zone matching the average position of the data, so the database opens already georeferenced in Oasis Montaj.
• Sanitizes channel names: column names are cleaned up into valid Geosoft channel names (invalid characters replaced, duplicates disambiguated), with X/Y always placed first as Geosoft expects.
• Tags known units: well-known channels — coordinates, Heading, Altitude, TMI / Bx/By/Bz — get their unit of measure (m, deg, nT) set automatically.
• Writes the database: all rows are written as a single line into a new .gdb file, named after the input file.

---

1. Use the "Open files" toolbar button or drag & drop the CSV file you want to hand off to Oasis Montaj.

2. Do whatever cropping, filtering or column processing you need in GeoHammer first — the export is meant to be the last step before leaving GeoHammer, not a replacement for it.

3. In the Scripts panel, choose Export as Geosoft (Oasis montaj) database. Since the script declares the wildcard csv template, it is available for any CSV file.

4. Click the "Select" button next to Output folder and pick where the .gdb should be written. This field is required — the script will not run without it.

5. Click "Apply". The script will automatically download all required dependencies the first time it runs.

Since the script only produces the external .gdb file and does not touch the opened CSV, there is nothing to reload in the chart — the database simply appears in the folder you chose, ready to be opened in Oasis Montaj.

One small technical note!

Geosoft expects a named coordinate system catalog entry, not a bare EPSG code — that's why the script picks the UTM zone matching the data's own location (e.g. WGS 84 / UTM zone 35N) instead of just tagging the database with EPSG:32635.

If Longitude/Latitude are missing from the file, X/Y are simply not written and the database is exported without a coordinate system — everything else still works.