How to Transfer Coordinates Between Job Files on a Data Collector

Applies to: Trimble Access, Topcon Magnet Field, Leica Captivate, Sokkia SurveyPro, and most modern field data collectors

Construction surveyors frequently need to move coordinate points between job files — pulling control from an office-created job into a stakeout job, consolidating multiple phase files into a single as-built record, or sharing control points with a second crew. Done incorrectly, coordinate transfer silently corrupts a job by mixing coordinate systems, inverting units, or duplicating conflicting point IDs. This guide covers the correct procedure for coordinate transfer across all major data collector platforms.

Step 1: Confirm Coordinate Systems Match

Before transferring any coordinates, confirm that the source job and the destination job use identical coordinate system settings. This includes: projection (State Plane zone, UTM zone, or calibrated local grid), datum (NAD83, WGS84, local), unit system (International feet, US survey feet, or meters), and geoid model if vertical datum is involved.

On Trimble Access, navigate to Job Properties and review the Coordinate System tab for each job. On Topcon Magnet Field, check Job Settings and Coordinate System. On Leica Captivate, review Job Properties under Coordinate System. If the settings differ between source and destination jobs, resolve the discrepancy before any data transfer — do not assume coordinates will convert correctly on import unless the software explicitly performs a coordinate system transformation during import.

The most common error is transferring points from a calibrated local coordinate system into a raw State Plane job. The numbers will import without error messages but will place every point kilometers from the correct location. Always verify by checking that at least one known point imports with the expected coordinates.

Step 2: Export Points from the Source Job

Open the source job on the data collector and navigate to the export function. Most platforms export to CSV (comma-separated values) with columns for Point ID, Northing, Easting, Elevation, and Description. Export the full point list or a filtered selection — for large jobs with hundreds of points, exporting only the relevant control points or stakeout list keeps the destination job clean.

Common export formats and their use cases:

CSV (Northing, Easting, Elevation, Code): most portable format, works on any platform, import without a proprietary reader. DC format (Trimble): preserves additional Trimble metadata but is not compatible with other platforms. JOB format (Topcon): proprietary Topcon format, not transferable to Leica or Trimble. DXF: useful for importing into CAD but loses elevation precision and code information.

Save the exported file to an accessible location — internal storage, SD card, or USB drive depending on your data collector model. Name the file clearly with the source job name and date so the recipient crew can identify its origin without opening it.

Step 3: Import Points into the Destination Job

Open the destination job on the data collector and navigate to the import function. Select the file format matching the export format used in step 2. The import dialog will typically ask you to map the file columns to data collector fields — confirm that Northing, Easting, Elevation, and Code columns map to the correct fields. Swapping Northing and Easting here (a common mistake in files with ambiguous column headers) will place every point in the wrong location.

During import, the data collector may flag duplicate point IDs — points that already exist in the destination job with the same ID as an incoming point. Choose the correct resolution: keep existing, overwrite with incoming, or create new (renamed) duplicates. For control points shared between jobs, overwriting is usually correct if the incoming coordinates are more accurate. For stakeout points that should not change, keep existing. Never import blindly with overwrite-all without reviewing what will be replaced.

Step 4: Verify the Transfer

After importing, select two or three control points that exist in both the source and destination jobs and compare their coordinates directly. On the data collector, view the point list and compare Northing, Easting, and Elevation values against the original values from the source job or the engineer's coordinate file. They should match exactly (or within rounding to the displayed decimal places).

In the field, if possible, occupy a control point with the total station and perform a resection or known-point setup using the imported coordinates. Compare the resulting orientation to what you expect — the backsight azimuth should match previously established values within 10 arc-seconds for a correctly transferred control framework.

If the coordinates do not match or the field setup produces unexpected orientation residuals, the coordinate system settings likely differed between the source and destination jobs. Delete the imported points, correct the job settings, and repeat the import from step 1.

Step 5: Document the Transfer

Record the transfer in field notes: source job name, export date, destination job name, import date, and crew member performing the transfer. For control points specifically, note the original source (survey monument ID, GPS control session, or engineer-provided design file) and the number of points transferred. This documentation is your chain of custody for the coordinate framework used in the work.

Gradelog field records can capture control point IDs, coordinate values, and the survey sessions they came from, creating a traceable lineage for every point used in layout or as-built documentation.