GIS Labs

Solutions

Built for the people who own the data

The defects differ by discipline, and so do the rules. Find the one that describes your job.

National mapping · Cadastre

Government & land registry

A parcel overlap is not a rendering artefact. It is two people holding title to the same ground.

What goes wrong

  • Overlaps and gaps across a registry too large to review by hand
  • Registered area disagreeing with the geometry on file
  • Metadata gaps blocking publication of otherwise finished layers

What changes

  • Every parcel checked before registration
  • Legal and computed area reconciled to a stated tolerance
  • An audit trail of who validated what, and when

Packs that apply

Core · 144 checksCadastre & Real Estate · 42 checksMunicipal · 27 checks

Base maps · Addressing

Municipalities & smart cities

Your base map is the foundation every other city system reads from.

What goes wrong

  • Address points that do not fall inside their own parcel
  • Building footprints overlapping roads and each other
  • District boundaries that overlap or leave gaps

What changes

  • Addresses validated against parcel containment
  • Footprints checked for closure and encroachment
  • A quality score you can track quarter to quarter

Packs that apply

Core · 144 checksMunicipal · 27 checks3D & Buildings · 28 checks

Water · Gas · Sewer

Utilities

A network model that is not connected cannot be analysed.

What goes wrong

  • Pipes that stop centimetres short of a junction and break the trace
  • Pipes whose upstream or downstream node is not in the inventory
  • Assets in the inventory that attach to nothing

What changes

  • Every segment verified as connected
  • Node references checked against the structures they name
  • Contractor deliveries checked before loading, not after

Packs that apply

Core · 144 checksUtilities · 34 checks

Fibre · Feeders · Coverage

Telecom & power

A route that is wrong on paper is wrong in the ground.

What goes wrong

  • Fibre routes with breaks that only surface during construction
  • Dangling conductors that stop outage analysis tracing upstream
  • Coverage modelled for sites not in the asset inventory

What changes

  • Route continuity verified end to end
  • Feeder topology checked for dangles and isolation
  • Designs signed off before civil works begin

Packs that apply

Core · 144 checksElectric & Telecom · 26 checks

Roads · Intersections

Transportation

Routing engines are only as good as the topology you feed them.

What goes wrong

  • Centrelines that do not meet where the map shows a junction
  • Direction codes outside the code list
  • Bridges and tunnels modelled as at-grade crossings

What changes

  • Intersection connectivity verified network-wide
  • Same-grade crossings without a junction found
  • Isolated fragments found before a routing release

Packs that apply

Core · 144 checksTransportation · 31 checks

Deliverables · Sign-off

Surveying & consultancies

Prove the deliverable passes the client specification before you submit it.

What goes wrong

  • Deliverables rejected on QA, with the rework at your cost
  • Every client having a different schema and tolerance
  • No evidence of quality to attach to a submission

What changes

  • Client specifications encoded once as a reusable rule set
  • A validation report attached to every hand-over
  • Rework caught internally rather than by the client

Packs that apply

Core · 144 checksCadastre & Real Estate · 42 checksTransportation · 31 checks

Don’t see your sector?

The core pack is cross-industry and applies to any spatial dataset. If your discipline needs checks none of the packs cover, we write them.

Try it on your own data.

Run the checks for your field on a real layer of your own. You’ll know within an afternoon whether it’s worth it.