How do you use the plan files on an RTK controller?
Load the CSV files on your RTK controller, walk to each point in ID order, and survey the target where you actually put it. The planner makes one CSV for GCPs and one for checkpoints, each in the coordinate system you chose, with IDs numbered in walking order. Use the coordinates you measure on site for processing, not the planned ones.
Why are GCPs and checkpoints in separate files?
ASPRS says checkpoints should be independent of the GCPs used in processing (ASPRS C.1). Separate files, each with its own closed walking route and its own ID prefix (GCP01, CP01), stop the two being mixed up in the field. Each file name ends with the EPSG code of its coordinates, such as EPSG27700 for British National Grid or EPSG32630 for WGS 84 / UTM zone 30N. That way projected eastings and northings are never mistaken for latitude and longitude (EPSG4326).
What is in the CSV files?
Eight columns: ID, Role, Easting, Northing, Height, CRS, Latitude and Longitude. Height is left blank on purpose, because the planner works in two dimensions and you measure the true height on site. Rows follow the walking route, so GCP01 is the first stop and the route returns to the start.
Should I use the planned or the surveyed coordinates?
Always the surveyed ones. The planned file is a guide to sensible spots that meet your spacing, edge buffer, clearances and checkpoint rules. If a planned spot is on long grass, under a parked car, in standing water or unsafe, put the target on the nearest clear, firm, safe ground and survey its centre there. Export the measured points from your controller at the end of the job and use that for processing and accuracy testing.
Reference
American Society for Photogrammetry and Remote Sensing (2024) ASPRS Positional Accuracy Standards for Digital Geospatial Data, Edition 2, Version 2. Available at: https://publicdocuments.asprs.org/PositionalAccuracyStd-Ed2-V2 (Accessed: 7 October 2026). doi: 10.14358/ASPRS.PAS.2024