> 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/integrations-and-plug-ins/introduction/convert-gint-databases-to-geodinml.md).
# Convert gINT Database to GeoDinML
## Introduction
This tutorial will guide you through the process of converting gINT database files into GeoDinML. The gINT converter will convert the groups **PROJECT**, **LITHOLOGY**, **POINT**, and **SAMPLING** into GeoDinML format. If any groups or parameters are missing, adjustments must be made to the gINT database file before conversion.
## Conversion Process
* Open the gINT Converter
* Choose your gINT database. It can be either a gINT database (.gpj) or a Microsoft Access database (.mdb or .accdb)
* The conversion process will begin automatically. The gINT converter will convert the groups **PROJECT**, **LITHOLOGY**, **POINT**, and **SAMPLING** into GeoDinML format.
* Once the conversion is complete, save the GeoDinML file to the desired location
## Troubleshooting
If the uploaded gINT database does not match the mapping schema, the gINT converter will provide information indicating which mandatory groups or parameters are missing.
You can then adjust the corresponding tables and parameters within the gINT database file either directly in gINT or by renaming the file extension to `.mdb` or `.accdb` and making the necessary changes in Microsoft Access.
## Mandatory Groups and Parameters
The following gINT groups and parameters are mandatory for the conversion:
| **Group** | **Parameters** |
| ------------- | ------------------------ |
| **PROJECT** | Name |
| | Manager |
| | City |
| | Country |
| | Location |
| | Number |
| | Input\_Units |
| **POINT** | PointID |
| | ShortName |
| | East |
| | North |
| | CoordSys |
| | HoleDepth |
| | Hole\_Diameter |
| | Elevation |
| | Drilling\_Company |
| | Driller |
| | Start\_Date |
| | End\_Date |
| | Drilling\_Method |
| | Drilling\_RigType |
| | Logger |
| | Location |
| | Water\_Initial |
| | Water\_Liqu |
| | Water\_Static |
| | CPT\_AreaRatio |
| | CPT\_File |
| | CPT\_Dir |
| | Expl\_Dir |
| | Station\_Number |
| **LITHOLOGY** | PointID |
| | Material\_Description |
| | Material\_Graphic |
| | Depth |
| | Layer\_Bottom |
| | Comment |
| | Line\_Type |
| | Additional\_Descriptions |
| **SAMPLING** | PointID |
| | Sample\_Number |
| | Depth |
| | Bottom\_Depth |
| | Recovered\_Length |
| | Driven\_Length |
| | Sample\_Type |
| | Sample\_Diameter |
---
# 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/integrations-and-plug-ins/introduction/convert-gint-databases-to-geodinml.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.
%20(1).png?alt=media)
%20(1).png?alt=media)