# Line Data Report

The Line Data report is a **coordinate listing** for every measured line definition in the active tunnel. It does not compute deviations — use {doc}`line-vs-theoretical` or {doc}`dr-trend` for DR analysis. The report answers three practical questions:

- Which sections contain data for each measured line?
- How many measured points are in each (section × line)?
- What are the exact section-local coordinates — and, when horizontal geometry is available, the world X/Y/Z — of every measured point?

## Dialog

Open **Reports → Line Data...** from the main menu.

| Control | Effect |
|---------|--------|
| **From / To** | Restrict the report to sections inside the chainage band. Pre-filled with the alignment's start and end chainage when the dialog opens; edit to narrow the band. |
| **Line Definitions** | Tick the measured line definitions to include. All measured lines of the tunnel are listed; template lines are never offered here. |
| **Mode — Summary** | Produces only the Point-Counts table (one row per section × line). |
| **Mode — Full Detail** | Produces the Point-Counts table followed by Per-Point Detail pages. |
| **Format — PDF / XLSX** | Output type. |

Default selection: all line definitions ticked, Mode = *Full Detail*, Format = *PDF*.

## Point-Counts table

Always emitted, regardless of Mode. One row per (section × line) combination:

| Column | Content |
|--------|---------|
| **Chainage** | Station formatted km+m (e.g. `0+125.500`). |
| **Section** | Section name as stored on the cross-section. |
| **Line** | Measured line definition name. |
| **Points** | Number of measured points the line currently has in that section. |

The table is sorted by chainage ascending and, within the same chainage, by line name. Sections where a line has no points are still listed with **Points = 0** so gaps in survey coverage are visible at a glance.

### PDF output

Rendered as a continuous table on A4 portrait pages. Column headers repeat at the top of every page. Zero-point rows are shown in light grey so the eye skims past them.

### XLSX output

One sheet named **Counts** with a header row and one data row per entry. All point counts are written as integers.

## Per-Point Detail

Emitted only in *Full Detail* mode. One row per measured point, grouped by section then by line.

Every row reports the **section-local coordinates** — the (X, Y) of the point expressed in the section's own frame, where X is horizontal offset from the axis and Y is elevation relative to the axis. When the alignment has horizontal geometry configured (non-empty `Engine.HGeometry`), the **world X/Y/Z** columns are also filled. When no horizontal geometry is available the world columns render `-` and the report still produces a complete section-local listing.

### Columns

| Column | Content | Notes |
|--------|---------|-------|
| **Chainage** | Station of the section. | |
| **Section** | Section name. | |
| **Line** | Line definition name. | |
| **Layer** | Line's layer name (from the line definition). | |
| **Colour** | Colour swatch of the line. | Rendered as a filled rectangle in PDF, as a hex value in XLSX. |
| **#** | Zero-based point index within the line. | |
| **Sect X** | Horizontal offset in metres. | Negative = left of axis. |
| **Sect Y** | Elevation relative to the section's axis point, in metres. | Negative = below axis. |
| **World X** | Easting in metres. | `-` when horizontal geometry is missing. |
| **World Y** | Northing in metres. | `-` when horizontal geometry is missing. |
| **World Z** | Elevation (height) in metres. | Computed from `SetoutOffset`'s `PointHeight`. |

The world transform calls `Alignment.Engine.SetoutOffset(Station, SectX, SectY)` for each measured point. This routine places the point on the alignment's 3-D geometry, so bearings and super-elevation are honoured: the world X/Y is where the point actually sits on the ground, and World Z is that point's terrain-referenced height.

### Colour column

The colour column shows the colour as configured on the line definition. In the PDF report it is rendered as a filled rectangle so that a reviewer can match ink on paper with what they see on screen (see {doc}`../sections/line-definitions`). In XLSX the same column holds the 6-digit hex code (e.g. `#2F7FBF`) so that conditional-formatting rules can still pick it up.

```{tip}
The Line Data report is the fastest way to hand raw survey data to an outside party. Export the Full Detail PDF for a signed-off paper copy, and export the XLSX for onward processing in spreadsheet software.
```

## PDF layout

A4 portrait, 15 mm margin on all sides.

- **Page 1 — Counts**: tunnel and project header, then the Point-Counts table.
- **Pages 2+ — Detail**: one continuous table, paginated. Each page repeats the header row.

A footer line is drawn across the bottom of every page with the page number and the project/tunnel name.

## XLSX layout

Two sheets:

- **Counts** — the Point-Counts table.
- **Detail** — the per-point rows, written only when *Full Detail* is selected.