EO SAT GPT
Home › Technical Guides › Satellite Operations
Satellite Operations

Archive Satellite Imagery vs. On-Demand Tasking: How to Choose

A practical framework for deciding when historical archive catalogs satisfy baseline analysis and when dedicated satellite tasking is operationally required.

Core Differences Between Archive Catalogs and Dedicated Tasking

Archive satellite imagery comprises scenes already captured, downlinked, calibrated, and indexed in searchable catalogs. Analysts verify exact cloud percentages, sun elevation, and viewing geometry before purchase, eliminating weather risk. Because collection costs are shared across buyers, archive tiles deliver predictable pricing for baselines and model training.

On-demand tasking schedules a future pass over a user-defined Area of Interest (AOI) within a target window. Tasking becomes essential when organizations need current ground truth after a port disruption or infrastructure milestone where no recent clear archive exists.

  • Archive offers immediate delivery and zero weather risk because cloud cover is known upfront.
  • Tasking unlocks current visibility when existing scenes exceed your decision latency horizon.
  • Archive Minimum Order Areas (MOAs) are typically smaller than dedicated tasking polygons.

Evaluating Latency, Cloud Risk, and Viewing Geometry

Every tasking order balances window duration, maximum off-nadir angle, and cloud-cover ceiling. Tightening off-nadir below 15 degrees limits relief distortion in dense ports but cuts eligible passes per week; widening to 35 degrees speeds revisit while lengthening shadows.

In coastal or monsoon climates, requiring under 10% full-scene clouds can stall optical orders for weeks. Separating AOI cloud acceptance from outer-frame clouds prevents unnecessary rejections.

  • Set 15-20 deg off-nadir for structural measurement; 25-35 deg for rapid presence checks.
  • Verify ground station downlink cadence, which adds 2 to 18 hours post-capture.

Cost Governance and Minimum Order Area Optimization

Issuing isolated assured tasking orders for scattered small targets wastes Minimum Order Area capacity. Clustering nearby facilities into shared corridors lowers per-site cost, while opportunistic archive harvesting satisfies routine inland oversight.

Clear escalation rules prevent ad-hoc urgent orders from draining budgets: reserve priority tasking exclusively for verified anomalies, time-sensitive port checks, or post-event assessments.

Building an Archive-First Acquisition Pipeline

Leading teams unify archive and tasking sequentially. Automated orchestrators query SpatioTemporal Asset Catalog (STAC) endpoints across optical and radar archives for scenes captured within the past 7 to 14 days before ordering new collections.

Only when freshness SLAs fail does the platform dispatch a tasking API call with fallback SAR criteria if optical cloud forecasts exceed 50%.

Archive Imagery vs. Standard vs. Priority Tasking

ParameterArchive ImageryStandard TaskingPriority Tasking
Delivery LatencyMinutes to 2 hours3 to 14 days12 to 72 hours
Cloud Certainty100% known pre-orderBest-effort under limitGuaranteed / auto-retasked
Relative Cost / sq kmLow baselineModerate (1.5x-2.5x)High (3x-5x)
Off-Nadir ControlFixed historical passFlexible (up to 35 deg)Tight (<15 deg) available
Best Use CaseBaselines & ML trainingRoutine monthly trackingUrgent alerts & port audits

Ranges reflect commercial constellation norms and vary by resolution and minimum order area.

Worked Illustration: Optimizing a Port Monitoring Budget

A logistics team monitors 10 bulk terminals (5 sq km each) monthly where archive costs 1 unit/sq km and assured tasking (25 sq km MOA) costs 4 units/sq km.

  1. Naive Tasking: 10 separate monthly orders x 25 sq km x 4 units = 1,000 units/month.
  2. Archive Baseline: Pull 6 historical timestamps across the exact 50 sq km footprint (300 units one-time).
  3. STAC Check First: Weekly catalog checks satisfy 70% of monthly updates via recent archive scenes (35 units/month).
  4. Selective Tasking: Dispatch assured tasking only for the remaining 30% persistently cloudy or anomalous sites.

Worked Outcome: An archive-first check paired with selective tasking preserves budget for genuinely urgent collections.

Pre-Tasking Verification Checklist

  • Query STAC archive catalogs from the past 14 days before opening any tasking order.
  • Match sensor resolution to target size instead of defaulting to sub-meter.
  • Set off-nadir tolerances based on local shadow and crane height.
  • Evaluate cloud thresholds strictly inside the target polygon.
  • Cluster nearby sites into shared tasking corridors.
  • Define SAR fallback triggers for cloudy coastal windows.

Frequently Asked Questions

When is archive imagery better than new tasking?

Archive imagery is ideal for historical baselines, ML training, and any workflow where a recent clear scene within 7-30 days meets decision latency.

Why do tasking orders require larger Minimum Order Areas?

Tasking consumes finite satellite maneuvering, storage, and downlink bandwidth along an orbital pass, requiring a minimum swath footprint.

Can optical tasking guarantee zero cloud cover?

No operator controls weather; assured tasking guarantees repeated attempts until cloud thresholds are met, or pairs with all-weather SAR.

How far back do commercial satellite archives go?

Public medium-res archives span decades, while commercial sub-meter catalogs typically run from the mid-2000s or 2010s onward.

Primary Standards & References

  • Open Geospatial Consortium (OGC) — SpatioTemporal Asset Catalog (STAC) Specification
  • Committee on Earth Observation Satellites (CEOS) — Analysis Ready Data (CEOS-ARD) Framework
  • ISO 19115-2 — Geographic Information Metadata Extensions for Imagery and Gridded Data

Related Earth Observation Guides