> 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/maps/cad-and-gis-exports.md).

# CAD and GIS Exports

Get GeoDin data out to CAD and GIS: export layouts as DXF from the internal PDF printer, and export query results as point shape files for ArcGIS.

GeoDin's internal PDF printer can export layouts as DXF files for use in AutoCAD or other CAD software.

DXF export makes GeoDin graphical output (borehole logs, cross-sections) directly consumable in AutoCAD workflows.

The internal PDF printer supports vector output (not just raster), preserving quality for CAD and publication use.

For the DXF route in detail (block vs linear structure, `ACAD_COLORS.TXT` colour mapping), see [DXF Export](/exporting-data/dxf-export.md).

## Exporting query results as a shape file

The **Export shape files** method turns the result of a GeoDin query into a point shape file that any GIS can read. It sits inside the **Publish and export** method, which is available on object and measurement point nodes as well as on queries and groups.

{% stepper %}
{% step %}

#### Step 1: Select the source

Select the object node, measurement point node, query, or group whose data you want to export.
{% endstep %}

{% step %}

#### Step 2: Open the export method

Open **Publish and export** and choose the method **Export shape files**.
{% endstep %}

{% step %}

#### Step 3: Decide whether to add the shape in ArcGIS

The option to add the shape in ArcGIS is only active when the GeoDin Extension for ArcGIS is already connected to GeoDin. If it is not connected, create the shape here and add it to the ArcGIS project - or to any other GIS - manually afterwards.
{% endstep %}

{% step %}

#### Step 4: Run the export and name the output

Click **\<Execute>**, then either select an existing output shape or enter a new name for it.
{% endstep %}
{% endstepper %}

For the ArcGIS side of the connection, see [ArcGIS integration](/integrations-and-plug-ins/overview.md).

## Reference: shape attributes written by the export

GeoDin always creates a **point data shape**. The result fields of the query are attached to it as attribute fields, with two rules worth knowing before you design the query:

* **Short field names when several tables are involved.** If a query draws on more than one GeoDin table, the short names of the fields are used in the shape. The complete `tablename.fieldname` notation exceeds the maximum field length allowed by the shape attribute column definition.
* **XCOORD and YCOORD are added automatically.** So that the point data can be located, the fields `XCOORD` and `YCOORD` from the GeoDin general data are added to the object automatically. They appear as shape attributes even when they are not part of the query result fields.

The coordinate system the exported coordinates belong to is the one stored on the object - see [Coordinate Systems and EPSG](/maps/coordinate-systems-and-epsg.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 dynamically by asking a question.

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

```
GET https://docs.geodin.com/maps/cad-and-gis-exports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.