4.5 Control Point Marking During Scanning
Control points must be marked correctly during the scan or they produce no benefit in processing. The naming convention is the same for every device, and a single naming error renders a point useless no matter how accurately it was surveyed.
Naming Convention
Point names are case-sensitive. The name you type in LixelGO at the marker must match the name in your coordinate file exactly, character by character, including capitalization. There is no fuzzy matching and no warning at processing time. If the names differ, the point is ignored.
Naming Rules
- Use short, distinctive names you can type without error in the field
- Use only ASCII letters and digits. Avoid spaces, punctuation, accented characters, and symbols
- Set a convention before site (project code plus sequence number is reliable)
- Use the exact same name across every scan that shares the same physical point for Map Fusion
Valid Names
GCP01 GCP02 GCP03
DC1-A1 DC1-A2 DC1-B1
CP001 CP002 CP003
Short, ASCII-only, distinctive, easy to type accurately on a phone keyboard in the field.
Invalid or Mismatched Names
gcp01 vs GCP01 in the file (case difference)
GCP 01 with a space
GCP–01 with a non-ASCII character
"GCP01" with stray quote characters
Each fails silently in LixelStudio even when the operator believes the point was marked correctly.
Write your point names on paper before site. Type them into both the coordinate file and LixelGO from that list. Do not invent names while scanning; inconsistency between memory and what you type is the most common cause of control point failures.
L2 Pro and K2 Workflow
Marking a control point means seating the scanner on the exact surveyed point. The procedure is the same for both devices.
- Confirm the Target Is on the FloorThe marker can be an XGRIDS reflective sticker, a checkerboard target, or any clear, stable floor marker. It must sit on a flat, floor-level surface where the scanner can rest on top of it and stay vertical. Never mark a control point on a wall.
- Seat the Scanner on the Exact PointPlace the scanner on the control point so it sits vertical, using the control point base to seat it on the exact spot. Set it down gently. Jarring the device at placement adds positional error at that point that cannot be corrected later.
- Add the Control Point in LixelGOWhile the device is stationary, open the control point interface and type the point name exactly as it appears in your coordinate file, including case. Confirm and wait for the success message before moving.
- Lift Slowly and ContinuePick the scanner up slowly. Sudden movement immediately after marking degrades that point. Remain near the marker for a few seconds before moving on.
The one rule that matters: mark the exact same physical spot, with the exact same name, every time. This includes every scan that shares a point for Map Fusion. A point marked a foot away, or under a slightly different name, is a different point as far as processing is concerned.
PortalCam Workflow
The PortalCam procedure differs because the device sits on a tripod rather than resting on the ground. Control point support requires recent LCC Scan and PortalCam firmware; confirm both are up to date before relying on it.
- Deploy the PortalCam on Its Tripod at the PointSet up stably at the control point. Choose good lighting, clear texture nearby, and open space. Avoid corners, dark alcoves, and areas next to mirrors or glass.
- Add the Control Point in LCC ScanOpen the control point interface and type the name. Hold the device stationary for at least 5 seconds after submitting. The extended hold ensures enough scan data is collected at the stationary position.
- Circle the Point After MarkingWalk the PortalCam in a circle around the point to capture surrounding geometry from multiple angles. This improves target detection in LCC Studio.
Shared control points across Map Fusion sessions. Each map that does not use RTK needs a minimum of 2 shared control points, 3 ideal. Device placement at a shared point need only be approximately consistent between sessions: position within 0.5 m (1.6 ft), orientation within 20 degrees, height within 10 cm (4 in). Exact repeatability is not required, but gross inconsistency degrades fusion quality.
Marking for RTK Accuracy Verification
When verifying RTK accuracy against target stickers, the procedure differs from GCP marking. You do not seat the device on the target. Walking around the sticker while scanning is enough to capture it for verification, and the device does not need to be stationary.
The sticker still needs to be scanned well for automatic target detection. Walk around it at close range, within 0.5 m (1.6 ft), and make sure it is clearly visible in the scan path before moving on.
Ending a Session After the Last Control Point
If the last action before ending the scan is marking a control point, do not stop immediately. Wait at least 15 seconds after the confirmation before ending. Stopping too soon means the point carries insufficient scan data around it, and LixelStudio may not recognize it.
The 15-second rule is a minimum. If the project permits, continue scanning for 20 to 30 seconds and walk a small loop before ending, to give the last point full coverage in the dataset.
Control points marked. Next: 4.6 Coordinate Systems, what you need to configure LixelStudio for the correct output coordinate system.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer

