Managing GPC and Underground Utility Documentation in PIX4Dcloud

PIX4Dcloud can make georeferenced utility captures accessible to authorised project reviewers, but a defensible GPC record needs more than a shared 3D model. Preserve source provenance, coordinate and height information, checkpoint evidence, coverage exceptions and the distinction between observed geometry and interpreted utility assets.

Technical content reviewed against official sources · 16 November 2026
01

Structure projects around the exposure event

Name records by project, work area, utility or chainage and capture date according to the owner’s convention. Keep repeated visits distinguishable and avoid overwriting the only copy of a pre-backfill record. If the project uses Pro sites and timelines, confirm that chronological organisation does not obscure different trenches or asset packages.

  • Project and contract reference
  • Exposure or work-area identifier
  • Capture date and field team
  • Horizontal and vertical reference
  • Processing version or route
  • QA status and exception state
02

Control who can view, annotate and share

Apply the organisation’s approved access model and share-link policy. Utility records can reveal sensitive infrastructure, so external sharing must be authorised. Reviewer annotations are collaboration data, not automatic updates to an authoritative GIS or certified drawing.

03

Attach the quality narrative to the spatial model

Review the processing report, reconstruction coverage and independent checkpoint evidence before marking the dataset ready for issue. Document where RTK was interrupted, where cameras could not observe a surface and where height or coordinate transformations require attention.

  • Observed: point geometry and imagery of visible surfaces.
  • Checked: independent checkpoint and completeness results.
  • Interpreted: utility lines, attributes or classifications created for GIS.
  • Certified: any separately signed drawing or regulated survey product.
  • Exceptions: occlusion, access, georeferencing and processing limitations.
04

Handover is a separate step from sharing

Agree which recipients need browser access and which require governed files. Export the agreed point cloud, mesh, imagery, annotations and metadata, then test them in the recipient environment. Preserve the QA and exception report with the spatial data. A link can expire or permissions can change; it should not be the sole archival record.

What to carry into the project.

Do not use public links for sensitive infrastructure without approval.

Keep observed, interpreted and certified information separate.

Include QA and exceptions in the project record.

GPC supplements required utility-survey workflows.

Continue the technical review.

RX2 GPC field workflowData sharing and project access
PIX4D · Cloud support hubPIX4D · PIX4Dcatch RTK workflow

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.