Clean planimetrics, built to your data model.

Human-reviewed feature extraction from orthophotos, oblique imagery and fused LiDAR for municipal, utility and engineering systems.

THE OUTCOME

Define the feature catalogue, capture rules and target schema first. Review geometry, attributes and applicable topology rules, then test a sample in the receiving GIS.

Request a pilot ↗︎
BEST FIT

A focused production service.

  • Municipal planimetric updates
  • Engineering and utility feature inventories
  • Change-detection and GIS maintenance programs
DELIVERABLES

What arrives.

Final scope follows your project specification and accepted calibration sample.

01

Building footprints and roof outlines

✓
02

Road, curb and sidewalk geometry

✓
03

Impervious surfaces and land cover

✓
04

Visible utility and transportation assets

✓
05

Water, drainage and vegetation features

✓
06

Change detection and update layers

✓
PRODUCTION WORKFLOW

Controlled from input to acceptance.

Each stage has an explicit output, responsible reviewer and defined check.

01

Schema calibration

Required layers, attributes, capture rules and minimum mapping units are converted into an executable SOP.

02

Feature capture

Automation can assist repeatable capture; human review distinguishes visible features, inferred geometry and areas that need clarification.

03

Topology control

Overlap, gaps, self-intersections, open rings, dangling lines and invalid attributes are checked systematically.

04

Completeness review

An agreed sample and visual review assess omission, commission and attribution errors. The report identifies review coverage and limitations.

FORMATS TO CONFIRM IN PILOTSHPFileGDBGeoPackageGeoJSONDWGPostGIS
SPECIFICATIONS TO AGREEClient feature catalogueOGC Simple FeaturesMunicipal GIS schemaAgreed completeness and accuracy checks
INPUTS AND ACCEPTANCE

Define a handoff your team can verify.

Provide imagery dates and resolution, horizontal reference information, the feature catalogue, minimum mapping unit and an example of accepted attribution.

  • Review footprint versus roof-outline rules and obscured features
  • Measure sampled omissions, commissions and attribute errors
  • Check topology only against rules appropriate to each layer
SCOPE LIMITCapture-date differences, shadows and roof displacement can affect interpretation. Flag uncertain features; do not treat image-derived geometry as a legal boundary or verified underground asset.DELIVERY EVIDENCEAgree the output inventory, source references, validation results and exception log. Set review deadlines and correction responsibilities in the written scope.
COMMON QUESTIONS

Before a pilot.

Can you match an existing municipal geodatabase?+

Yes. We work from your schema, coded domains, subtype rules and representative accepted data.

Is extraction fully automated?+

No. Automation is used where it improves throughput, but final geometry and ambiguous features are reviewed by people against documented rules.

Can imagery and LiDAR be used together?+

Yes. Fusing elevation, intensity and imagery often improves building, curb, canopy and infrastructure interpretation.

CALIBRATE BEFORE YOU SCALE

Define the source, output and review boundary.

Share a representative area, the working template and the acceptance conditions your team will use.

Start with a short brief. Fields marked optional can be left blank; you do not need to have a specification ready.

Send a description only. Do not include source-data links, passwords, controlled data or personal information about other people. Data transfer and any confidentiality requirements should be agreed separately.