> 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/exporting-data/csv-export.md).

# CSV Export

GeoDin can export any tabular data view - general data, samples, measurement data tables, data sequence series - to CSV. CSV is the right choice when the downstream tool prefers plain text or expects a delimited format.

For Excel exports of the same tables (with column titles preserved as cell formatting), see [Excel Export](/exporting-data/excel.md). For preparing import templates by exporting and re-importing, see [CSV and Excel Import](/importing-data/csv-and-excel-import.md).

## Tabular CSV export

Export commands are available on most tabular views via the **red dot with two arrows** icon. The available views include:

* General data tables
* Sample tables
* Measurement data tables
* Data sequence series

The exported file uses GeoDin's internal parameter names as column headers, ready for round-trip re-import.

## Data sequence series re-export

Imported data sequence series can be re-exported as CSV. This is useful when you need to:

* Pull a series out of GeoDin to edit the values in another tool, then re-import.
* Hand off raw depth-indexed data to a process that doesn't read GEF or other CPT formats.


---

# 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/exporting-data/csv-export.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.