ON THIS PAGE
Resolution is one of the most visible specifications in satellite imagery procurement. It is also one of the easiest numbers to misunderstand. When a buyer sees “15 cm HD,” the natural assumption is that the satellite collected the ground natively at 15 cm. That is not the case.
Vantor’s 15 cm HD imagery is created by applying proprietary HD processing to native 30 cm WorldView imagery. The source observation remains native 30 cm data; the HD product is an enhanced representation designed to provide additional visual clarity.
Native resolution and HD output are different specifications
Native spatial resolution describes the approximate ground sampling at which the imaging system records the scene. In simplified terms, a native 30 cm panchromatic image samples the ground at approximately 30 cm intervals.
HD processing happens after collection. It works with information contained in the native imagery to create a denser visual representation. It does not change the fact that the original observation was collected at 30 cm native resolution.
Why buyers should care about the distinction
If a tender specifically requires a native acquisition resolution, a 15 cm HD output should not automatically be described as native 15 cm imagery. The requirement and the product need to use the same terminology.
For visual interpretation, planning and some automated workflows, however, the HD output can provide a practical advantage even though the source observation is native 30 cm.
What HD processing can improve
The most immediate benefit is interpretability. Edges can appear more distinct, closely spaced features can be easier to separate visually and dense urban scenes can become easier for analysts to review.
- urban mapping and planning review;
- development and construction monitoring;
- road-context analysis;
- high-detail basemap presentation;
- stakeholder visualization;
- selected feature-extraction workflows;
- visual inspection of small or closely spaced structures.
What HD processing cannot do
Enhancement should not be interpreted as unlimited information recovery. Processing cannot reveal a surface hidden behind a tall building, remove cloud that covered the ground during acquisition, or create engineering-grade measurements from information the sensor did not observe.
HD processing also does not eliminate limitations caused by cloud and haze, shadow, viewing geometry, building lean, seasonal conditions, motion or atmospheric effects.
More pixels do not automatically mean more independent information
An enhanced output can contain a denser grid, but useful interpretation still depends on the quality of the original observation. A technically literate comparison should therefore examine the source, acquisition conditions and intended use rather than the output pixel size alone.
Native 30 cm imagery is already highly detailed
It is a mistake to frame 15 cm HD as the “good” option and native 30 cm as the “basic” option. Native 30 cm WorldView imagery is already suitable for many demanding mapping and monitoring tasks.
- regional urban planning;
- land-use interpretation;
- development monitoring;
- road and infrastructure context;
- environmental basemapping;
- GIS background imagery;
- large-area monitoring programmes.
Choose resolution by asking what feature matters
A better specification describes the smallest object or change the project needs to identify. The requirement may be to detect a building, distinguish individual roof structures, understand road geometry, or simply see broad development.
- Do we need to detect the feature?
- Do we need to classify it?
- Do we need to measure it?
- Will a human analyst interpret it?
- Will a computer-vision model use it?
Image quality is affected by more than nominal resolution
Two images with the same nominal resolution can feel very different to an analyst. Atmospheric clarity, haze, contrast, sun angle, viewing geometry and acquisition conditions affect how much can be interpreted.
A clear native 30 cm scene may be more operationally useful than an enhanced image affected by haze or severe off-nadir geometry.
Urban viewing geometry can be as important as pixel size
When a satellite observes a city at an oblique angle, tall buildings lean away from the sensor and can hide roads or ground surfaces behind them. In high-rise areas, this occlusion can matter more than the difference between 30 cm native and 15 cm HD output.
Panchromatic, multispectral, pansharpened and HD describe different things
- Panchromatic: high-resolution grayscale imagery;
- Multispectral: imagery recorded in multiple wavelength bands;
- Pansharpened: a visual product combining panchromatic spatial detail with multispectral colour;
- 15 cm HD: an HD-enhanced output derived from native 30 cm imagery.
Where additional visual clarity can help
Urban planning
Dense urban areas contain closely spaced buildings, roads, parking areas, plots and construction sites. Added visual clarity can help analysts separate features during planning review.
Construction monitoring
High-detail imagery can improve visual review of development stages across large sites, although acquisition date and consistent collection remain just as important.
Basemap presentation
Executive portals and planning viewers benefit from clear, visually attractive imagery. Enhanced detail can improve presentation even when the analytical workflow does not require it.
Computer vision
Some feature-extraction models may benefit from the enhanced product, but the effect must be tested. Model accuracy depends on labels, training geography, feature size and preprocessing.
When native 30 cm is likely sufficient
- the AOI is very large;
- the smallest required feature is comfortably visible at 30 cm;
- the imagery is primarily contextual;
- the final output is generalized into GIS features;
- budget efficiency is important;
- the analytical workflow benefits from the native source product.
When aerial survey may be a better answer
If the project requires engineering-grade mapping, very fine GSD, custom flight geometry, oblique views, LiDAR or extremely detailed site mapping, aerial survey may be more appropriate than pushing satellite imagery beyond the task it was designed to perform.
Common mistakes when comparing 30 cm and 15 cm HD
Mistake 1: Comparing only the number
A comparison that considers only 30 cm versus 15 cm ignores acquisition date, viewing angle, cloud, spectral configuration, processing and intended use.
Mistake 2: Writing “native 15 cm” in a specification
If the desired product is Vantor 15 cm HD, procurement language should describe it as an HD-enhanced output derived from native 30 cm imagery.
Mistake 3: Assuming enhancement improves positional accuracy
Visual sharpness and geometric accuracy are different characteristics. If a project has an accuracy requirement, state it independently.
Mistake 4: Ignoring final display scale
If imagery will always be displayed as a regional basemap at small scale, users may never see the practical advantage of additional detail.
How to evaluate both products objectively
Where possible, compare samples over a representative environment and ask users to perform the real interpretation task. Score feature visibility, edge clarity, separation of closely spaced objects, model performance if relevant, storage implications and commercial difference.
Storage and delivery considerations
Higher-density outputs can increase file size and downstream storage. Large-area programmes should consider how imagery will be tiled, compressed, published and archived.
Procurement specifications should be precise
- native source resolution;
- HD-enhanced output resolution;
- processing level;
- spectral requirement;
- positional accuracy;
- acquisition-date requirement;
- license;
- delivery format.
How SIME can help
SIME can review the AOI, intended use, date requirement and smallest relevant feature, then compare native 30 cm imagery and 15 cm HD in the context of the complete workflow.
Further reading
How to run a practical side-by-side evaluation
For high-value projects, a specification comparison alone may not be enough. A representative sample can help the end users judge whether the HD output provides a meaningful operational advantage.
Select a sample that resembles the real project environment—dense high-rise, low-rise residential, industrial, desert, coastal or mixed urban—and ask users to perform the same interpretation tasks they will perform in production.
Possible evaluation criteria
- ability to distinguish road edges and access points;
- visibility of small buildings or rooftop structures;
- separation of closely spaced objects;
- clarity of construction-stage features;
- ease of interpretation at the intended display scale;
- effect on feature-extraction accuracy, if automation is planned;
- storage and delivery implications;
- commercial difference between options.
The goal is not to prove that one image looks sharper. It is to determine whether the sharper appearance changes the decision, analysis or workflow enough to justify the selected product.
Storage, tiling and publishing can influence the choice
Higher-density outputs can increase file size and downstream storage. On a small AOI this may be insignificant, but large-area programmes should consider how imagery will be tiled, compressed, cached and published.
If the imagery will be served through ArcGIS Enterprise or another web platform, test performance using the real target architecture. The most detailed source product is useful only if the delivery environment can serve it efficiently.
Consider consistency across a multi-date monitoring programme
If imagery will be compared over time, product consistency can matter as much as individual-image sharpness. A monitoring programme should define whether every acquisition will use the same product type, whether historic 30 cm imagery will be compared with future HD outputs, and whether the change-analysis method can tolerate those differences.
For human visual review this may be straightforward. For automated pixel-level change detection, inconsistent preprocessing can create false differences. Establish a repeatable preparation workflow before scaling the programme.
How 15 cm HD fits into a broader procurement decision
A complete imagery decision should consider native source resolution, HD enhancement, acquisition date, archive versus tasking, processing level, spectral needs, cloud tolerance, viewing angle, license and delivery method together.
This avoids the common mistake of optimizing one specification while compromising the requirement that actually matters most.
