Archive Imagery or New Tasking: How to Choose the Right Route

One of the first decisions in a satellite-imagery project is also one of the most consequential: should you use imagery that has already been collected, or should you request a new satellite collection?

At first glance the choice appears simple. Archive imagery exists already, while tasking asks a satellite operator to collect something new. In practice, the decision affects timing, risk, cost, recency, processing, licensing and the entire monitoring strategy.

The correct route therefore begins with the decision the imagery needs to support. A planning authority updating a basemap, a developer monitoring construction, an environmental team studying coastline change and an emergency organization seeking current situational context may all need high-resolution imagery, but they should not necessarily buy it in the same way.

Begin with the project question, not the satellite name

A strong enquiry starts with a practical statement such as: “We need to understand construction progress across this 180 km² development between July and September,” or “We need imagery from before and after a major site change.” Those statements are much more useful than starting with “we need 30 cm imagery.”

Once the purpose is clear, the technical choices can be matched to it: acquisition date, native resolution, HD enhancement, cloud tolerance, viewing angle, processing level, file format, license and delivery.

Questions to answer before comparing products

• What is the exact area of interest?
• Is the required condition historical, current or future?
• How close must the imagery be to a particular date?
• Does seasonality matter?
• What is the smallest feature or change that matters?
• Will the imagery be used once or repeatedly?
• Will the output support GIS, a report, an application, monitoring or automated analysis?

What archive imagery gives you

Archive imagery is data already collected and stored by the operator. Modern commercial archives can contain repeated observations of the same locations over many years. That makes them valuable not only for quickly obtaining existing imagery but also for reconstructing historical conditions.

The major advantage is that collection risk has already passed. The image exists. The remaining task is to determine whether it is suitable.

Archive imagery is usually a strong starting point when:

• a historical baseline is required;
• the project needs a before-and-after comparison;
• a suitable recent image already exists;
• the exact acquisition day is flexible;
• speed of delivery matters;
• the team wants to evaluate an area before committing to recurring tasking;
• the client needs several historical dates rather than one current image.

For example, a municipality reviewing urban expansion from 2018 to 2026 should begin with historical archive coverage. A real-estate developer conducting due diligence on a site may need several prior years. A utility investigating changes near a corridor may need imagery from immediately before and after a construction period.

An archive search is more than an overlap test

Finding an image that intersects the AOI is only the first step. A technically useful archive review also considers acquisition date, cloud cover, haze, viewing geometry, native resolution, processing level, spectral configuration and whether the important portion of the AOI is actually visible.

A scene can cover the project polygon and still be unusable. Five percent cloud sounds small, but it is irrelevant if that cloud sits directly over the site. A highly oblique image can be technically sharp but may hide streets or ground surfaces behind tall buildings.

Archive-selection checklist

• Date: Is the acquisition close enough to the required period?
• Cloud: Are the priority features visible?
• Atmosphere: Is haze acceptable?
• Viewing angle: Is the geometry appropriate for dense urban interpretation?
• Resolution: Can the required features be interpreted reliably?
• Coverage: Is one scene sufficient or will a mosaic be required?
• Processing: Is the available product suitable for the intended workflow?
• License: Can the imagery be used and shared as the project requires?

When new tasking becomes the better route

New tasking means requesting a fresh collection over a defined AOI during an agreed acquisition period. It becomes important when current or future conditions matter more than historical availability, or when the archive simply does not contain suitable imagery.

Tasking is especially relevant to active construction, fast-changing urban areas, infrastructure development, event-driven monitoring, seasonal environmental analysis and recurring programmes where a client requires systematic updated observations.

Tasking is commonly considered when:

• the ground condition must be current;
• the project has a future collection window;
• available archive scenes are too old or unsuitable;
• repeat acquisitions are required;
• season, water level, vegetation state or other time-sensitive conditions matter;
• the AOI is operationally important enough to justify proactive collection planning.

Tasking is a collection plan, not an exact appointment

Satellite tasking should not be communicated like booking an aircraft for a guaranteed photograph at 10:00 AM. Collection is affected by orbital access, weather, cloud, viewing geometry, collection priority and other operational constraints.

A feasibility review establishes whether the requested acquisition window is realistic, what opportunities may exist and whether the required geometry and product can be achieved.

Factors that can affect collection

• AOI size and shape;
• satellite access opportunities;
• local cloud climatology;
• season;
• required viewing angle;
• acceptable acquisition window;
• competing collection priorities;
• need for recurring observations.

Archive and tasking often belong in the same programme

The decision is not always either/or. A common monitoring design uses archive imagery as the historical baseline and new tasking for the current condition. This creates a natural before-and-after pair.

Archive analysis can also help design future monitoring. If historical imagery shows that a site changes slowly, quarterly or seasonal acquisition may be sufficient. If change is rapid, a denser cadence may be justified.

Recency should be defined operationally

“Recent” is not a technical specification. For one application, an image from the previous year is sufficient. For another, anything older than two weeks is unusable.

Define recency in terms of the decision:

• latest available suitable image;
• collected within the last 30/60/90 days;
• collected after a known event;
• collected before a specified project milestone;
• collected during a defined season.

Cloud tolerance should focus on the AOI, not only scene percentage

A commercial scene may carry a cloud percentage, but the client should care about cloud over the operational area. A low total cloud percentage can still render the priority location unusable.

For critical projects, distinguish between cloud over the full scene, cloud over the AOI, cloud over priority sub-areas, thin haze versus opaque cloud, and cloud shadows that may affect interpretation.

Viewing geometry can change what is visible

High-resolution imagery collected at an oblique angle may show sides of buildings but can also produce building lean and ground occlusion. In dense city centres, a lower off-nadir angle may be more useful when the objective is to see roads or ground surfaces between towers.

If building lean or occlusion matters, state that requirement during archive selection or tasking.

Resolution should be tied to the smallest meaningful feature

Instead of asking for the highest available resolution, describe what must be detected, classified or interpreted. Broad land-use mapping has different needs from construction-detail review or small-object analysis.

This is also where a comparison between native 30 cm imagery and 15 cm HD becomes useful. The decision should reflect the workflow rather than a desire for the largest number of pixels.

Processing can be as important as acquisition

The project may require orthorectification, pansharpening, multispectral delivery, mosaicking, colour balancing, tiling or another production step. These choices affect both usability and cost.

For change detection, additional co-registration and radiometric normalization may be necessary. For enterprise basemap use, seamless mosaicking and efficient tiling may matter more.

Licensing should be decided before delivery

Government and enterprise imagery may be used by multiple departments, consultants and contractors or displayed through applications. Usage rights should reflect the real operating model.

• used by one internal project team;
• shared across an enterprise;
• provided to consultants;
• included in external deliverables;
• published in a public or customer-facing application;
• used to train or operate AI/ML workflows.

Compare total workflow cost, not only the scene price

A lower-cost image that needs extensive processing or fails the project date requirement may be more expensive operationally than a more suitable product. Conversely, paying for new tasking when a good archive scene already exists may add cost without adding value.

Total project economics can include acquisition, processing, storage, delivery, GIS publishing, analyst time and future updates.

A practical decision matrix

Requirement	Archive first?	Tasking likely?
Historical baseline	Yes	Usually no
Latest suitable condition	Check first	If archive is insufficient
Specific future window	No	Yes
Before/after analysis	Yes for “before”	Often for “after”
Recurring monitoring	Useful baseline	Often appropriate
Urgent project	Best if suitable coverage exists	Depends on collection opportunity

How SIME approaches the request

Space Imaging Middle East can begin with the AOI, date requirement and operational purpose rather than requiring the client to specify a satellite product. The imagery team can review archive options, assess new WorldView tasking, compare suitable resolution and processing options, and advise on delivery and licensing.

What to include in the first enquiry

• AOI as KML, KMZ, GeoJSON, shapefile, coordinates or a marked-up map;
• date range or preferred acquisition window;
• short explanation of the purpose;
• approximate project deadline;
• known processing requirements;
• how the imagery will be used and shared.

Next step: Request satellite imagery or explore Satellite Tasking.