> 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/overview/generate-reports.md). # Generate Reports Generate borehole log and CPT reports in GeoDin and export them as one PDF per object, ready to attach to ArcGIS features This workflow generates borehole log and CPT reports in GeoDin and exports them as one PDF per object - the attachment-ready files the ArcGIS workflow consumes in the next step. {% embed url="" %} > **Video chapters:** 0:00 Selecting a borehole for the report | 0:23 Choosing a borehole report template | 0:32 Generating the borehole report | 0:52 Selecting CPT data | 1:09 Generating the CPT report and accessing print preview | 1:27 Exporting the report as PDF | 1:48 Verifying the exported files | 2:02 Generating reports for additional areas ## Requirements * A GeoDin project containing borehole and/or CPT data. * No layout setup required - the report layouts used here ship with GeoDin (loaded from `C:\ProgramData\GeoDin\Layouts\`). ### Step 1: Open the report layouts and select an object Select a borehole and start the **Graphic printing and editing** method. The **Available layouts** tree loads, with borehole log layouts under **1 - Borehole logs** and CPT/parameter layouts under **2 - Parameter vs depth**. Confirm whether you are working with a **borehole** or **CPT data** before choosing a layout - they use different layouts (and exist in Metric and USCU unit-system variants).

Graphic printing and editing with the Available layouts tree

### Step 2: Generate a borehole report Choose a borehole log layout (for example, **Geotech soil log (A4 landscape) - Metric**) and verify the preview: the log, strata descriptions, and header metadata all render from the database.

The borehole log rendered from the selected layout

### Step 3: Generate a CPT report For CPT data, choose a CPT layout (for example, **CPT Classification Robertson 1986 Density - Metric**) and verify the preview the same way.

The CPT classification report rendered from the CPT layout

### Step 4: Select the objects to output and open print preview Drag the objects you want to output into **Objects to display** - you can drag the whole **All objects** node to queue every borehole at once. Then open the print preview and review before exporting.

Dragging All objects into Objects to display

### Step 5: Export the reports as PDF Open the export menu and choose **Create a PDF per object**. This produces one PDF per borehole - the format the attachment workflow expects.

The export menu with Create a PDF per object

### Step 6: Verify the exported PDF files Open the destination folder and confirm one PDF exists per object. Note the naming: a `/` in the object name becomes `_` in the file name (`BH12/CPT12` becomes `BH12_CPT12.PDF`) - this matters when [attaching reports in ArcGIS Pro](/integrations-and-plug-ins/overview/attach-reports.md).

The exported PDFs with the underscore naming

### Step 7: Repeat for additional projects or areas Generate and export reports for the remaining areas the same way, keeping one folder per project so the files stay easy to find and batch-attach.

Reports generated for an additional project area

## Optional settings * **Layout variants** - borehole vs. CPT layouts, each in Metric and USCU unit systems; match the layout to the object type. * **Print preview** - review before export to avoid rework; confirm the destination folder afterwards. *** ## Working with reports Drag the whole **All objects** node into *Objects to display* to report an entire project in one run. **Create a PDF per object** produces exactly the per-borehole files the [Attach Reports](/integrations-and-plug-ins/overview/attach-reports.md) workflow consumes, and one-folder-per-project keeps batch attachment simple. When reporting multiple areas, verify each folder individually so no files go missing. For the exhaustive reference on layouts and bulk output, see [Report Templates](/visualization-layouts-and-reporting/report-templates.md) and [Bulk Print and PDF Export](/visualization-layouts-and-reporting/report-templates/bulk-print-and-pdf-export.md). *** **Next step:** [Attach the exported reports to ArcGIS feature classes](/integrations-and-plug-ins/overview/attach-reports.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/integrations-and-plug-ins/overview/generate-reports.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.