How to Export Total Station Coordinates Correctly

A survey can be perfectly observed in the field and still create expensive problems in the office if its data is exported in the wrong format, coordinate system or order. To export total station coordinates reliably, you need to protect the link between the instrument job, the control used on site and the software receiving the data. This is not simply an administrative task. It is the handover point between measured observations and decisions made by designers, engineers, machine operators and setting-out teams.

For UK surveying and construction teams, the right export process reduces rework, avoids transposed point data and keeps a clear audit trail. The exact menu options vary between Leica, GeoMax and other total station platforms, but the principles remain consistent.

Start with a clean, checked field job

Coordinate exports are only as dependable as the job held on the controller or instrument. Before transferring anything, confirm that the correct job is open and that its coordinate reference is understood. Check the active station setup, backsight, prism details and any site calibration or localisation applied during the survey.

This matters especially where a project uses local grid coordinates rather than a national mapping grid. A drawing may be issued in OSGB36-based coordinates, a GNSS receiver may be working in a transformed local system, and the total station job may contain coordinates established from a site control network. Exporting points without documenting this context can leave the office team with numbers that look plausible but do not fit the design model.

Review the point list before export. Look for duplicated point IDs, placeholder codes, unusually high or low levels, and observations recorded while the wrong prism constant or target height was selected. It is quicker to correct a suspect point while the surveyor and site are still available than to investigate it after the design team has identified a clash.

Choose the right format to export total station coordinates

There is no universal best format. The correct choice depends on the package receiving the data and what information must travel with each point.

A CSV or plain-text file is often suitable for spreadsheets, basic CAD imports and checks. It is widely readable, simple to archive and easy to inspect, but it can lose valuable structure if the column order is not agreed. A typical survey export may contain point number, Easting, Northing, level, code and sometimes a timestamp or quality field.

For CAD and survey processing software, a format that retains point codes, linework definitions and observations may be more useful. Native job files can preserve considerably more detail than a generic coordinate list, although they may only open in compatible software. LandXML is commonly used where surfaces, alignments or design information need to move between specialist platforms.

The practical approach is to export a working file for the immediate recipient and retain the original instrument job as the source record. A CSV may be ideal for an engineer requesting setting-out checks, while the native job remains essential if the survey needs reprocessing, auditing or adjustment later.

Agree the column order before sending data

A coordinate file becomes risky when its labels are unclear. The familiar order of Easting, Northing, height is not universal. Some applications expect Northing, Easting, elevation, while others use X, Y, Z with no indication of what X and Y represent.

State the format in the filename or accompanying transmittal, for example: `Project_PointSurvey_ENZ_2026-10-27.csv`. Include a header row where the receiving software permits it. If no headers are allowed, document the field order separately and use a consistent export template across the project.

Do not assume that a recipient will interpret “height” correctly either. Confirm whether the required value is an ellipsoidal height, orthometric height, local datum level or a reduced level related to the project benchmark.

Follow a controlled export workflow

Once the job has passed basic checks, export it through the manufacturer’s field software or data manager rather than copying individual values by hand. Manual rekeying is slow and creates avoidable opportunities for missed decimals, swapped coordinates and altered point IDs.

First, select only the points required. A completed total station job can include setup points, backsight checks, temporary marks and repeat observations that are not intended for design or drawing production. In some cases these are useful for quality control, so exclude them from the delivery file only after retaining the full job.

Next, apply the required point filter or code selection. For example, a topographical survey may need all measured detail points, whereas a setting-out report might require only the design points checked on site and their measured residuals. Make sure the export distinguishes between design coordinates and as-built observations if both sit within the same project.

Then select the output format and field order. Confirm decimal precision, delimiter and whether point codes will be included. Commas can cause problems where a code description contains punctuation, while tab-delimited text may be more reliable for some legacy workflows. If the file will be opened in a spreadsheet, take care that the software does not automatically change leading zeros in point numbers or convert coordinate values based on regional settings.

Save the export into a controlled project folder with a meaningful name, revision reference and date. Avoid labels such as “final” unless the project has a documented final issue. “Rev03” or “Issued_2026-10-27” provides a clearer record when files are updated.

Verify the exported file before it leaves the survey team

A quick visual check catches a surprising number of errors. Open the export in the intended receiving software where possible. Confirm that a few known control points plot in the right location, check that levels are sensible and inspect whether point codes have remained attached to the correct points.

For setting-out work, compare several exported design points against the approved drawing or model. For as-built work, overlay the points on the relevant CAD base plan or model and inspect obvious features such as building corners, kerb lines or grid intersections. A consistent shift usually indicates a coordinate-system, orientation or station-setup issue. Randomly displaced points may point to coding, selection or file-parsing problems.

It is also good practice to check point count. If 842 detail points were selected but the output file contains 837 rows, do not assume the missing observations are unimportant. The difference may be explained by duplicate IDs or filtered codes, but it should be understood before issue.

Common problems and what they usually mean

When coordinates arrive in the wrong place, resist the temptation to apply an arbitrary shift until the drawing appears to fit. Find the cause first. A constant translation may indicate that local control and design coordinates are from different versions of the grid. A rotation may suggest an incorrect backsight, occupied point or grid orientation. A scale discrepancy can arise where ground coordinates and grid coordinates have been mixed.

Points with correct plan positions but incorrect levels often indicate the wrong instrument height, target height, benchmark or vertical datum. Where only certain points are affected, check whether prism and reflectorless observations were processed with the correct target settings.

Missing linework is another common issue. Point codes alone do not always recreate feature strings in CAD. If the receiving package relies on code libraries, linework rules or field-to-finish conventions, send the agreed coding standard and confirm that it matches the survey team’s configuration.

Build export into the project quality process

The strongest export process is repeatable rather than dependent on one experienced operator remembering every setting. Establish project templates for coordinate systems, point coding, export formats and filenames. Keep a short register of what was issued, to whom, when and from which source job.

For larger or higher-risk schemes, retain a copy of the raw observations, processed job, exported file and a PDF or screenshot of the final check. This takes little time compared with revisiting a live construction site after an incorrect setting-out file has been used.

Training also pays for itself. Modern robotic total stations and field software can move data quickly, but they cannot decide whether a particular client needs ENZ, NEZ, local coordinates or an agreed transformation. Survey Tech can help teams select suitable equipment and arrange practical support where workflows, field controllers or data transfer need to work reliably across a project.

A coordinate export should give the next person confidence, not another problem to solve. Treat the file as a surveyed deliverable, check it against control and issue it with enough context for its purpose. That discipline keeps field accuracy intact all the way to the drawing, model or setting-out stake.