A radar image can have ten-metre pixel spacing while its documented resolution is coarser. The distinction affects supplier comparisons, processing costs and the claims a downstream product can support.
The number beside a radar image is not always its resolution. It may describe the distance between the pixels in the delivered grid. Those quantities are related, but they answer different questions. A buyer who treats them as interchangeable can compare unlike products or pay for a larger file without receiving the improvement it expects.
The distinction is visible in ordinary public satellite documentation. It is therefore a useful question for any commercial data proposal: does the stated figure describe the measurements the product can distinguish, the spacing of its delivered samples, or a later display format? A credible supplier should be able to explain which meaning applies.
The Copernicus Sentinel-1 product table lists the high-resolution Interferometric Wide Swath Ground Range Detected product with 20 by 22 metre resolution and 10 by 10 metre pixel spacing. Its footnote qualifies the GRD resolution values as mid-range values at mid-orbit altitude, averaged across swaths. The specification deliberately keeps resolution and spacing in separate columns.
The example does not mean that every ten-metre radar product has the same resolution. It means that the grid number alone cannot establish the answer. A commercial product from another sensor or processing chain needs its own documented characteristics.
The Alaska Satellite Facility's software manual explains the underlying distinction: spatial resolution concerns the separation that measurements can discriminate, while pixel size can refer to spacing in the image grid. The measurement concept remains useful even though the manual's software context is historical.
For a purchasing team, the immediate improvement is simple: give the two quantities separate fields in a comparison. Add the relevant product type and processing version beside them. This prevents a salesperson's shorthand from becoming the only specification that survives into the customer's order.
The Sentinel-1 example also shows why one rounded number can be incomplete. Resolution can be described in two directions. A product's samples may form a square output grid while the documented resolving characteristics differ across those directions. Reducing everything to a single figure loses information about the product being offered.
A buyer does not need to reproduce the sensor's technical design. It needs the supplier to state the coordinate meaning of the numbers and the product to which they apply. The specification should make it possible to distinguish a source-data characteristic from a value introduced by a later conversion.
That is especially relevant when integrating data from several providers. A platform can place different products on a common grid for convenient use. The common grid improves compatibility, but it does not make the underlying measurements identical. The customer's documentation should preserve the characteristics that matter to its own output.
This is a data-quality distinction, not a claim about the ability to recognise a particular object. Such a claim would require separate, appropriate evidence. Resolution figures by themselves do not establish the reliability of every downstream interpretation.
Processing services can deliver the same source material at different pixel spacings. ASF's Sentinel-1 RTC guide describes 10, 20 and 30 metre output options and explains that the underlying source imagery and elevation model remain the same regardless of that choice. It also warns that resampling an elevation model to a finer output grid does not increase the source model's native resolution.
The commercial lesson extends beyond that specific service. A data product should identify the lineage between its source observation and its delivered file. If a supplier offers a finer grid as an upgrade, the buyer can ask which additional information or supported function the upgrade provides. The answer may be improved compatibility or a more suitable representation of existing detail, rather than a new observation.
That can still have value. A customer application may need a particular grid to align its inputs or simplify integration. The important point is to price the actual benefit. Paying for a convenient prepared product is different from paying for evidence of additional measured detail.
The same distinction should appear in marketing. A downstream company can accurately describe its output spacing while preserving a separate statement about source resolution. Combining the two into an unsupported headline risks promising customers more information than the product contains.
ASF's guide includes an illustrative comparison in which 30, 20 and 10 metre RTC outputs have file sizes of 267, 600 and 2350 MB respectively. These are examples from the displayed data, not universal file-size estimates. They show that the output choice can materially affect storage and processing even when it begins with the same source material.
A product team should therefore compare the complete cost of the proposed delivery. Larger files can change transfer requirements, storage, processing time and the work required to provide customer previews. Those costs may be justified by the application, but they should be connected to an evaluated benefit.
A hypothetical environmental-data service might use a coarser prepared product for a regional summary and retain a different supported product for more detailed customer review. The choice depends on what each output must establish. It should not be driven solely by the assumption that the smallest grid spacing is always the best purchase.
Pricing can reflect these differences transparently. A supplier might sell processing and hosting as part of its service, or supply data that the customer handles itself. Comparing the two offers requires recognising where those costs sit rather than treating every price as the cost of the original imagery alone.
A proposal should identify which product the sample file represents and whether its processing matches the standard commercial delivery. A specially prepared showcase can be informative while leaving questions about the ordinary service. The customer needs a supported example of what it will actually receive.
The accompanying metadata should explain the source and processing lineage well enough for the customer's intended quality review. It should identify missing information and any relevant differences between a preview and the analytical file. A clean image on a web map is not a substitute for that account.
This helps when assessing derived products. If a supplier sells a classification or environmental indicator rather than imagery, the buyer needs evidence for that output as well as the input specification. A finer grid may change the number of reported cells without changing the reliability of the conclusion attached to each one.
Our analysis of GAO's commercial-space data adoption findings places such technical questions alongside licensing and integration. Data suitability is one part of the service that a customer has to adopt.
The comparison should remain useful after the first purchase. If a provider changes a processing version, introduces a new output grid or replaces a source collection, the customer needs to know which documented characteristics have changed. A stable product name does not necessarily answer that question.
For a downstream business, the consequence may be a new validation requirement, an adjusted storage budget or an update to customer-facing documentation. Recording the original assumptions makes those changes easier to assess. It also helps the supplier explain an improvement without relying on an ambiguous resolution claim.
Company context, including our BlackSky profile, helps readers understand the broader imagery market. A technical comparison needs the more precise record: source product, delivered resolution, pixel spacing, processing lineage and evidence for the customer's intended output. Those fields turn a small number on a specification sheet into an intelligible commercial choice.
Copernicus and Alaska Satellite Facility product documentation supplies the numerical examples and measurement distinctions. BDI's purchasing examples concern data-product quality and cost, without imagery exploitation or operational targeting instructions.
Suggest a correction