PIX4Dcatch + Emlid RX2 for GPC in Singapore

PIX4Dcatch on a compatible iOS device can receive RTK positions from Emlid Reach RX2 and geotag captured imagery for processing into a georeferenced point cloud. For utility work, the reliable unit is the complete evidence chain: exposed surfaces, correct receiver mounting and offsets, suitable NTRIP corrections, explicit coordinate references, good image coverage, controlled processing and independent checks.

Technical content reviewed against official sources · 16 November 2026
01

Equipment and project preparation

Use a PIX4D-supported iPhone or iPad, the current PIX4Dcatch application, an Emlid Reach RX2 with suitable mounting, a correction service with site coverage, and a processing route through PIX4Dmatic or PIX4Dcloud. Prepare independent checkpoints or other verification observations appropriate to the acceptance criteria.

Before mobilisation, record the required horizontal coordinate reference system, vertical reference, utility types, exposure sequence, delivery formats and responsibility for any regulated survey observations. SVY21 and height-datum requirements must not be inferred from the NTRIP mountpoint or left until processing.

  • Supported mobile device and mounting arrangement
  • Reach RX2, charged and configured for the intended NTRIP workflow
  • Correction account, host, port, mountpoint and credentials
  • Project CRS, geoid/height reference and camera-offset convention
  • Checkpoint procedure, safety access and backfill contact
02

Configure the RTK chain before capturing the asset

Connect the RX2 to PIX4Dcatch using the supported iOS workflow and configure NTRIP. Confirm that the correction input reference, output reference and camera offsets are correctly represented. Automatic offsets apply only to known device and mounting combinations; custom arrangements require measured values and checking.

A fixed RTK solution is necessary for the intended geotagging route but not sufficient evidence for the finished model. Review positional quality, correction age and reconnections, and document interruptions. Where connectivity is unreliable, a properly configured base/NTRIP arrangement may be evaluated; PIX4D-compatible rovers do not use a direct UHF or LoRa correction link for this workflow.

03

Capture visible utility geometry, not an assumed network

Coordinate with the site team so pipes, cables, ducts, chambers and connections remain visible and safely accessible. Walk a consistent path that produces overlapping views from suitable angles. Include the full exposed length, junctions, terminations, nearby reference features and trench context. Avoid rushed captures, strong motion blur and systematic gaps on dark, wet, reflective or weakly textured surfaces.

Photogrammetry records surfaces visible to the camera; supported device LiDAR also remains line-of-sight. Neither detects utilities through intact soil or concrete. Occluded surfaces and inaccessible areas must be logged as gaps rather than completed by interpolation and presented as observation.

04

Process, inspect and independently verify

Export or upload using the supported project route. In PIX4Dmatic, inspect calibration and georeferencing before reviewing dense geometry. In PIX4Dcloud, review processing reports and coverage before sharing. In either environment, distinguish an attractive textured model from a validated spatial record.

Compare independent checkpoints and suitable known dimensions, investigate systematic offsets and record residual differences using the project’s acceptance method. If results do not meet requirements, recapture or apply the agreed corrective workflow rather than hiding the exception. The final handover should identify observed data, interpreted GIS features and any separately certified drawings.

05

A defensible handover package

The exact package is scoped to the recipient, but a useful GPC record normally combines spatial data with its provenance. Do not reduce delivery to a viewer link or a single LAS file without coordinate and quality context.

  • Georeferenced point cloud and, where useful, textured mesh
  • Source imagery or project export where agreed
  • Coordinate reference and vertical-datum statement
  • Processing report, checkpoint evidence and exception log
  • Optional interpreted utility lines/attributes as a separate scope
  • Clear statement that GPC supplements rather than automatically replaces required utility surveys

What to carry into the project.

RX2 support applies to the compatible iOS workflow, not Android RTK capture.

RTK-fixed does not validate final reconstruction accuracy.

Coverage gaps and datum assumptions belong in the exception record.

GPC does not replace certified drawings or regulated survey responsibilities.

Continue the technical review.

PIX4Dcatch technical pageGPC utility guide
PIX4D · Supported RTK workflowPIX4D · Emlid NTRIP base-station guidancePIX4D · iOS and Android comparison

Features and availability can change. Confirm the exact version, plan, sensor and commercial scope before procurement or project issue.

Specify the working system, not only the licence.

Share your source data, required outputs, users and constraints. Easepect can scope product supply, a technical demonstration, implementation and training.