GPC services and implementation

Commission the outcome, or equip your team to deliver it.

Choose managed capture, GIS vectorisation, a complete equipment/software workflow or an on-site demonstration and training programme. Each engagement is scoped around exposure frequency, survey responsibility, outputs and data handling.

No fixed package is presumed to fit every trench. Quotations follow the site, schedule, required formats and acceptance criteria.

01

Managed GPC capture

Contractors with intermittent trench openings; teams without in-house processing capacity.

Scope

Pre-site scoping, agreed photographic capture, RTK/control coordination, processing, visual QA and the contracted output package. GIS digitisation and Registered Surveyor involvement must be explicitly scoped; they are not automatically included.

What changes the quotation

Site access, safety requirements, number/length/depth of trenches, exposure window, travel, night work, security, asset complexity, coverage, survey-control availability, output formats, rework, turnaround and approval requirements.

Quote my capture project
02

Vectorisation and GIS data production

Survey teams and contractors who already hold an appropriate georeferenced point cloud.

Scope

Data review, manual or semi-automated feature extraction, 3D polyline creation, attribute mapping, projection/height checks, export and an agreed QA note.

Client provides

Original data, reference systems, geometry definitions, attribute schema, required official formats, acceptance criteria, and ownership or permission to process.

Request a GIS output review
03

Buy the field-to-office workflow

Contractors and consultants expecting regular captures.

Scope

PIX4Dcatch; a supported Emlid GNSS/RTK receiver such as Reach RX2; an approved correction service; compatible mobile device; PIX4Dmatic and/or PIX4Dcloud; PIX4Dsurvey and/or Global Mapper; suitable accessories; training and basic QA templates. Exact compatibility and licences are confirmed at quotation.

Procurement scope

Hardware, software, subscriptions, corrections, accessories and onboarding are selected around the intended workflow—not supplied as an unexplained bundle.

Build my GPC kit
04

On-site demo and professional training

Survey managers, digital leads, large contractors and utility owners comparing capture approaches.

Scope

Possible agenda: goals and specifications, site and control assessment, live capture, processing demonstration, point-cloud review, vectorisation example, limitations/QA discussion and a recommended adoption roadmap. Exact duration and charge basis are set by agreement.

Implementation approach

Start with a controlled pilot rather than an unsupported rollout. Establish a practical method for capture, QA and handover with both field and processing teams.

Arrange a GPC demonstration

A practical selection guide

Match the engagement to your operating pattern.

Occasional openings

Start with managed capture.

Avoid building an internal processing operation before capture frequency and output demand justify it.

Existing 3D records

Scope GIS production.

Review source quality and the target schema before committing to vectorisation.

Regular field demand

Build a controlled kit.

Combine compatible capture, corrections, processing, GIS tools and training.

Undefined requirements

Run a technical pilot.

Test responsibilities, data handling, capture conditions and handover on an agreed scope.

Before requesting a quotation

Bring decisions, not credentials.

Useful inputs include the general location, exposure count and dimensions, opening/backfill dates, required file formats, applicable specification, available control and Registered Surveyor involvement.

Do not send NTRIP passwords, subscription tokens or sensitive infrastructure plans through the general enquiry form. Where secure transfer is necessary and approved, arrange it separately.

Prepare a project enquiry

Plan before the excavation window

Not sure which engagement model fits?

Describe the expected capture frequency, current data and required outputs. We can help define the smallest sensible starting scope.

Discuss GPC