# AGS Export

## Export Formats (PDF, AGS, DXF, CSV, Excel, GeoDin ML)

Export commands (red dot + two arrows icon) are available on most tabular views: general data, sample table, measurement data tables, data sequence series.

Any data table (general data, samples, measurement data) can be exported to Excel via the red-dot export button — the recommended way to inspect expected headers/structure before preparing an import table.

Data sequence series can be re-exported as CSV files — useful when users import, modify, and re-export.

The `All Objects > Data Management > General Data` tabular view shows metadata for all locations at once and can be exported to Excel.

**Publish and Export** feature creates a zip file containing an Access database with the selected objects — available at project level and at individual borehole level.

A borehole exported via Publish and Export produces a single-borehole Access database that can be re-imported elsewhere.

**AGS export**: AGS 4.0.4 and AGS 4.1 formats supported via Publish and Export → AGS export; user can choose which groups to export, then Execute.

**DXF export**: the internal PDF printer can export layouts as DXF files for use in AutoCAD or other CAD software.

Internal PDF printer supports vector output (not just raster), preserving quality for CAD/publication.

GeoDin Onsite has two export mechanisms:

Onsite form export options include `Export to PDF` and `Export GeoDin` (GeoDin ML).

Onsite PDF exports contain a "DRAFT" watermark unless the form was produced via `Publish as Complete`; GeoDin ML exports never carry a draft watermark.

Onsite default export path is controlled by `Configuration > Folders > Export folder path`; supports shortcut codes like `[my documents]` and `[desktop]`.

Onsite exports are always placed in a project-named subfolder inside the configured export path (Onsite auto-creates the subfolder).

AGS format is supported as an Onsite output — `Publish as Complete` generates the full deliverable set (GDOF, PDF, GeoDin ML, AGS).

When Onsite `Publish as Complete` runs, only the `.GDOF` file stays visible locally as a photocopy; the full deliverable set is placed in the shared delivery folder.

## AGS Format Support

For AGS object type imports with Access databases, GeoDin creates the AGS database structure on the fly at import time.

For AGS imports into SQL Server databases, users must first manually create a dummy AGS object to prepare the database table structure before importing.

AGS import handles custom field definitions with warnings but still imports successfully.

AGS imports can handle nested measurement data (e.g. SCPG/SCPT) in a single procedure because the data is self-contained in the AGS group format — this advantage is NOT available for G1 object type imports.

For AGS workflow, the main user effort is getting the AGS file format correct — GeoDin handles the import from there.

AGS 4.0.4 and AGS 4.1 export formats are supported via `Publish and Export > AGS export`.

AGS export lets the user choose which groups to export, then Execute.

## AGS Format Integration

AGS 4.0.4 and AGS 4.1 export formats are supported via `Publish and Export > AGS export`.

AGS export lets users choose which groups to export, then execute.

AGS import capability exists (not demonstrated in training sessions).

Onsite currently supports Step 3 (ISO) and G1 forms producing GeoDin ML; the EN ISO E2 standard is temporarily disabled in Onsite due to a bug in the GeoDin GeoDin ML importer specific to E2-flavoured GeoDin ML.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.geodin.com/exporting-data/ags.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.