> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/importing-data/supported-formats.md). # Supported data formats One-page reference of every data format GeoDin imports and exports - geotechnical exchange, CAD/GIS layers, and report outputs - with links to each how-to. This page lists every data format GeoDin can read or write, in one place. Use it to answer "can GeoDin work with X?" - then follow the link for the full how-to. Formats are grouped by what they carry: geotechnical data, map and CAD layers, and report outputs. ## Geotechnical data exchange | Format | Import | Export | Carries | How-to | | ------------------------------------ | ------ | ------ | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | **AGS 4** (4.0.4 and 4.1.1) | Yes | Yes | Complete site investigation data: locations, ground descriptions, samples, lab results | [AGS import](/importing-data/ags-import.md), [AGS export](/exporting-data/ags-export.md) | | **GeoDinML** | Yes | Yes | GeoDin's own XML exchange format; the bridge from GeoDin Onsite field data to the office | [GeoDinML import](/importing-data/geodin-ml-import.md), [GeoDinML export](/exporting-data/geodinml-export.md) | | **SEP3** | Yes | - | German state-authority borehole data, delivered as an Access database and read via an exchange database | [SEP3 exchange database](/importing-data/sep3-exchange-database.md) | | **GEF** | Yes | - | CPT data in the format standard in the Netherlands | [Data sequences import](/importing-data/data-sequences.md) | | **Free-format ASCII** | Yes | - | CPT and other depth-oriented measurement series with configurable import filters | [Data sequences import](/importing-data/data-sequences.md) | | **gINT databases** | Yes | - | Legacy borehole databases, converted to GeoDinML by the gINT converter (PROJECT, LITHOLOGY, POINT, and SAMPLING groups) | [Convert gINT databases](/integrations-and-plug-ins/introduction/convert-gint-databases-to-geodinml.md) | | **CSV** | Yes | Yes | Tabular object and measurement data | [CSV and Excel import](/importing-data/csv-and-excel-import.md), [CSV export](/exporting-data/csv-export.md) | | **Excel** | Yes | Yes | Tabular data; an Excel export can serve as the template for a later import | [CSV and Excel import](/importing-data/csv-and-excel-import.md), [Excel export](/exporting-data/excel.md) | | **GeoDin database** (cross-database) | Yes | Yes | Objects copied directly between two GeoDin databases, no file in between | [Cross-database object copying](/importing-data/cross-database-object-copying.md) | ## Map and CAD layers | Format | Import | Export | Carries | How-to | | -------------------- | ------ | ------ | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | **SHAPE** | Yes | - | Vector GIS layers displayed in GeoDin Maps | [Adding layers](/maps/adding-layers.md) | | **DXF** | Yes | Yes | Vector CAD data: as a map layer in, and as editable layout geometry out | [Adding layers](/maps/adding-layers.md), [DXF export](/exporting-data/dxf-export.md) | | **JPG / TIFF / ECW** | Yes | - | Raster base maps (grid data) displayed in GeoDin Maps | [Adding layers](/maps/adding-layers.md) | | **WMS / web tiles** | Yes | - | Live web map services as background layers | [WMS and web tile layers](/maps/wms-and-web-tile-layers.md) | ## Reports and integrations | Format | Import | Export | Carries | How-to | | ---------------- | ------ | ------ | -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | **PDF** | - | Yes | Borehole logs, cross-sections, and layouts, single or in bulk | [Bulk print and PDF export](/visualization-layouts-and-reporting/report-templates/bulk-print-and-pdf-export.md) | | **Leapfrog Geo** | - | Yes | Borehole data handed to Leapfrog Geo for 3D modeling | [Leapfrog Geo export](/integrations-and-plug-ins/leapfrog-geo-export.md) | | **ArcGIS** | Yes | Yes | Borehole planning and results exchanged with ArcGIS Pro / ArcGIS Online through an Excel-based workflow | [ArcGIS integration](/integrations-and-plug-ins/overview.md) | | **QGIS** | Live | Live | Direct access to GeoDin databases from inside QGIS via the GeoDinQGIS plugin - no file exchange involved | [QGIS integration](/maps/qgis-integration.md) | *** ## Reference: choosing an exchange format * **Field to office:** GeoDin Onsite publishes GeoDinML - import it rather than re-entering field data. See [GeoDinML import](/importing-data/geodin-ml-import.md). * **To or from other geotechnical software:** AGS 4 is the broadest standard route in and out. See [AGS 4](/object-types/ags-4.md) for how AGS groups map onto GeoDin object types. * **Migrating a legacy database:** use the gINT converter for gINT databases; German SEP3 deliveries go through the exchange database. * **Bulk tabular edits:** export Excel, edit, re-import - the export doubles as the import template. See [CSV and Excel import](/importing-data/csv-and-excel-import.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.geodin.com/importing-data/supported-formats.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.