+91 98765 43210 | info@asav.com | Mon – Sat, 09:00 – 19:00 IST
Noida, Uttar Pradesh 201301
  1. Home
  2. Services
  3. Photogrammetry
  4. Planimetry
Photogrammetry

Planimetry

Stereo feature compilation to a defined specification, with completeness verified.

Planimetry — representative deliverable
Overview

Planimetry

Planimetric compilation is skilled interpretation work, and its quality depends almost entirely on how rigorously the feature specification is applied. Where does a driveway end and a parking area begin? Is a building's footprint at eave or at wall? Is that a track or a path? Inconsistent answers across a project produce a dataset nobody can analyse.

We compile in stereo to a written feature specification, with the ambiguous cases documented as decision rules during a calibration phase at the start of the project. Every compiler on the job works to the same rules, and the checker verifies against them rather than against personal preference.

Completeness is verified by systematic re-examination of a sample against the imagery, reported as a percentage by feature class. Positional accuracy is checked against independent survey where available.

What you receive

Every item below is issued in your own template, with your layer conventions, title block and revision scheme.

  • Building footprints captured at the specified reference (eave or wall)
  • Transportation — pavement edges, kerbs, driveways, tracks, paths, rail
  • Hydrography with flow direction and connectivity where specified
  • Utility surface features — poles, chambers, cabinets, pylons
  • Land-cover and vegetation boundaries
  • Walls, fences, retaining structures and other linear features
  • Point features to the specification's capture list
  • Attribute capture including height where stereo supports it
  • Feature decision-rule document agreed at project calibration
  • Completeness and positional accuracy report by feature class

Production detail

Key production parameters for Planimetry
Typical turnaround150–400 km² per month per team by feature density
Mapping scales1:500 to 1:10,000
Typical completeness98–99.5% verified by sample audit
Positional accuracyTo project specification, verified against survey where available
Specifications worked toYours, or national mapping standards
Output formatsDGN, DWG, GDB, SHP, GeoPackage
RevisionsIncluded until completeness target is met

Software and formats

We work in your toolchain. If something you use is not listed, ask — the list below is only what we use most.

SOCET SETSummit EvolutionTrimble InphoArcGIS ProMicroStationAgisoft Metashape

Frequently asked

With a calibration phase at the start where the ambiguous cases in your specification are resolved into written decision rules, reviewed with you, and then applied by every compiler. Most consistency failures come from a specification that never addressed the hard cases.

Yes where stereo imagery supports it — eave and ridge height, or a derived storey count. Accuracy depends on image scale and base-to-height ratio, and we state the expected tolerance before starting rather than after.

Yes — change-only updating against new imagery, with changed, new and removed features flagged so you can audit the update rather than accepting a wholesale replacement. It is usually far cheaper than recompilation.

Stereo compilation is better for features defined visually — surface types, markings, boundaries, land cover. LiDAR is better for anything defined by geometry and height. Many projects use both, and we will recommend the split rather than pushing the service you happened to ask about.
Step 2 of 4 in Photogrammetry

Send one planimetry job and see how we work

Scope, price and programme come back in writing before anything starts. Most first projects are a single deliverable so you can judge us on output, not on a pitch.

Call an engineer