CSV and copied data#

CSV and Copy data both provide numerical coordinates, but they serve different workflows. CSV exports all enabled datasets as one file. Copy data places only the active dataset on the clipboard for immediate pasting.

CSV data#

GraphX writes one adjacent X/Y column pair for every dataset whose Export checkbox is enabled, in the same canonical order shown in the Datasets list. The first row names each dataset above its two columns; the second row provides the X and Y headings using the axis label and unit metadata. For example, a project with two enabled datasets might begin like this:

This table illustrates the layout rather than prescribing the literal headings: GraphX uses the current axis metadata. A label and unit become Temperature (°C); missing metadata falls back to the X or Y axis name.

Datasets may have different numbers of points. CSV preserves point order within each dataset and leaves blank cells where a shorter dataset has no row at that index. A point without a calibrated graph position also produces blank cells in its dataset pair. GraphX does not include disabled datasets, and it does not write trendlines to CSV.

Coordinates use that dataset's selected Precision. This changes the text written to the file, not the stored value used by calibration, editing, regression, or later export.

Copy data#

Open the active dataset in Data points and select Copy data. GraphX copies a small tab-separated table to the system clipboard:

Temperature (°C)    Conversion (%)
20.0                12.5
25.0                18.4

The actual separator is a tab, so pasting into a spreadsheet creates two columns. The copied table has one heading row and then the active dataset's calibrated points in their existing order. Its axis headings use the same label/unit rules as CSV, and its values use the active dataset's precision setting.

Copy data omits points that do not have a valid graph position. It does not include the dataset name, other datasets, project notes, or trendlines. Unlike CSV, it does not consult the dataset Export checkbox: it is an intentional per-dataset convenience action.

For a multi-dataset file or for a stable saved result, use CSV data from Export overview.