> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/surfacescout/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/surfacescout/exporting-insights.md).

# Exporting insights

Once you have filtered every case you want to see, you can export all the insigths connected to them. As of right now geoJSON and .CSV are available

<figure><img src="https://901668700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHJMG9DD5fHIVTkjSdwy%2Fuploads%2FNiSILaJXUGDSWIk5PpFt%2Fimage.png?alt=media&amp;token=1d88b065-addb-4f89-9f57-8e0d9b68b042" alt=""><figcaption></figcaption></figure>

### Export a PDF report

**Export PDF Report** produces a report you can print or send on. It is grouped by case: each one gets its criticality, assignee, distance to the asset, activity trail, notes, field photos and every insight attached to it, and insights with no imagery are listed in a table of their own. The first page summarises the cases the report covers and the filters you used to get there.

The report follows the filters that are active on the Cases list. If you tick individual cases before exporting, it covers only those.

<figure><img src="https://901668700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHJMG9DD5fHIVTkjSdwy%2Fuploads%2Fgit-blob-2b30b6dde89092fe79bb6683466626d82d020737%2Fexport-pdf-menu.png?alt=media" alt=""><figcaption><p>Exporting a PDF report</p></figcaption></figure>


---

# 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.live-eo.com/surfacescout/exporting-insights.md?ask=<question>&goal=<user_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.