Plan observations and partnerships

CONAE describes a sixteen-day orbital repeat cycle for an individual SAOCOM satellite and eight days for the pair. SAOCOM 1A and SAOCOM 1B are complementary parts of that constellation. Repeat geometry is not a guarantee that a particular field receives an acquisition in the required mode at each opportunity, or that a usable product reaches a reader immediately.

Use an original planning example with potential observations on days 0, 8, 16 and 24. If the selected mode is unavailable on day 8, the first usable pair may be days 0 and 16. The observed interval is then sixteen days despite an eight-day opportunity pattern. Scheduling, acquisition, ground reception and processing are distinct steps, each of which can constrain a service.

SAOCOM participates with Italy’s COSMO-SkyMed in the SIASGE cooperation. Partnership can broaden available observations while each program retains its own spacecraft, instruments and goals. It does not make every product numerically interchangeable or turn a partnership’s design target into guaranteed coverage of every location.

Imagine combining two fictional radar products with different viewing geometries, spatial sampling and calibration conventions. A larger catalogue is useful only if the comparison respects those differences. Preserve each observation’s mission, time and processing metadata. For a change claim, test whether the difference persists after accounting for acquisition conditions rather than simply subtracting two attractive pictures.

Opportunity spacing and usable observations can differ

A spacecraft’s design lifetime is an engineering target, not an automatic shutdown date. Likewise, a proposed next generation is not an operating constellation until flight and commissioning evidence support that description. The program overview discusses a second generation; this course does not count it as already delivering observations. Current operational availability should be checked in the relevant acquisition and product services.

In a fictional emergency workflow, an observation is acquired on Monday, received on Tuesday and processed on Wednesday. The product’s Wednesday timestamp does not show that the flood was observed that day. A useful bulletin states the observation time and uncertainty alongside the release time. That keeps a technically successful delivery from becoming a misleading claim about conditions now.