A useful observation programme begins with a decision that somebody can act on. Before selecting imagery or instruments, define the area of interest, the people responsible for inspecting it, and the time available for a response. This planning perspective connects remote measurements with the practical questions that shape a survey or monitoring service. The aim is to identify which observations would change a decision, how supporting evidence would be collected, and what should happen when information is incomplete. A clear plan makes later technical choices easier to assess against an operational purpose.
This working guide considers how pointing and motion affect satellite imagery along mangrove forest margins. The immediate decision is to review changing mangrove cover. Useful reference evidence includes tidal context, canopy boundaries and representative field plots. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Separate the different pointing requirements
A camera can point near its intended target while still producing an image with poor geometry or blur. Pointing accuracy describes how closely the spacecraft achieves a commanded orientation. Pointing knowledge describes how well that orientation is estimated. Stability concerns changes over a relevant interval, including the detector integration period. These quantities serve different purposes and should be specified separately with a clear reference frame and time basis.
Orientation estimates combine information from sensors such as gyroscopes, Sun sensors and star trackers, depending on the architecture. Actuators then change or maintain the attitude. Reaction wheels exchange angular momentum with the spacecraft, while magnetic torquers interact with Earth's magnetic field and may support momentum management. Their suitability depends on the orbit, operating modes and disturbance environment. A component's advertised accuracy does not automatically become the pointing performance of the integrated spacecraft.
Evaluate the complete image motion budget
Ground features move across a detector because the spacecraft travels along its orbit and may rotate during imaging. Exposure time, scan timing and any motion compensation must be consistent with that movement. Residual motion during integration spreads signal across pixels and reduces contrast. High frequency vibration can produce a different image effect from slow drift, so one average attitude error may conceal an important problem.
Build an image motion budget that includes control behavior, structural response, actuator disturbances and timing uncertainties. Consider the mechanical path between attitude sensors and the optical payload: a flexible interface can change their relative alignment. Thermal distortion can also alter boresight alignment over an orbit. Test realistic operating combinations, including wheel speeds and other mechanisms that may run during an exposure, and assess whether laboratory support equipment affects the measurement.
Geometric processing uses orbit information, attitude knowledge, timing and an Earth model to locate observations. Ground control and image matching can improve some errors, but processing cannot always restore information lost to blur. For repeat observations, test relative registration as well as absolute location. Report residual errors across the field and across relevant operating conditions. A useful requirement links a user consequence, such as registration between spectral bands, to a measurable spacecraft or payload behavior and a verification method. This keeps pointing discussions connected to the quality of the delivered imagery.
The setting: Mangrove forest margins
Mangrove monitoring takes place at a changing boundary between land and water. The observed surface depends on canopy structure, tidal conditions, exposed sediment and the arrangement of channels. A narrow fringe may contain a high proportion of mixed observations even when the surrounding image appears detailed. Begin by defining whether the task is mapping canopy extent, detecting disturbance or studying a forest attribute, and establish the spatial unit that the data can represent defensibly.
Comparisons between dates should account for water and sediment conditions as well as cloud, haze and shadow. A change near the canopy edge may reflect different water exposure or geometric alignment rather than a new loss of trees. Retain the acquisition dates and relevant tidal context where available. Mapping rules should distinguish canopy, water and other surfaces consistently, while acknowledging locations where their contributions cannot be separated reliably at the chosen resolution.
Field observations should describe canopy boundaries, vegetation structure and the setting of sampled plots or inspection points. Record whether a visit represents an edge, a channel margin or the forest interior. A mapped vegetation response alone cannot establish carbon stock, habitat quality or the cause of a disturbance. Those interpretations need suitable evidence. A practical initial product provides a traceable cover-change assessment and a prioritised set of locations where field review would resolve important uncertainty.
Keep an auditable review record
A review record should explain how a result moved from an analytical output to an accepted interpretation or operational decision. Preserve the product identifier, the evidence considered, the reviewer role, and the outcome of the review. A short, consistent record is often more useful than an extensive free-text note that cannot be compared between cases. The objective is to make important decisions traceable without turning routine review into unnecessary administrative work.
Separate observations from conclusions within the record. Describe the evidence visible to the reviewer, the alternative explanations considered where relevant, and the reason for accepting, qualifying, or rejecting the result. If a correction is required, identify what should change and how the revised product relates to the earlier version. Keep unresolved questions visible so that they can be addressed by another observation or by the person responsible for the next action.
Use the accumulated record to improve the workflow. Recurring review reasons can reveal unclear requirements, missing contextual information, unstable processing steps, or an evaluation gap. Examine whether similar cases receive similar decisions across reviewers and over time. Preserve the relationship between feedback and subsequent revisions so that improvements can be assessed against the evidence that motivated them. An auditable record supports learning, accountability, and consistent delivery while allowing the technical process to evolve.
Use observation labels with consistent meanings
A reference label should describe an observation that another person could recognise or reproduce. Broad terms such as good, damaged, or unusual can conceal substantial differences between collection teams. Begin by defining the feature or condition being recorded, the observation unit, and the evidence needed to assign a label. Where possible, distinguish a direct measurement from an interpretation made by the observer.
Provide a short collection guide with examples, boundary cases, and a way to record uncertainty. Train observers using shared cases before relying on independently collected labels. If two observers disagree, preserve the disagreement long enough to understand its cause. It may reveal an unclear definition, a genuinely ambiguous condition, a difference in observation scale, or a problem in matching the reference record to the remote measurement.
Retain the context that makes the label interpretable. Location, time, collection method, observer role, and relevant surface conditions can be essential for later review. Changes to the label scheme should be documented and related to earlier versions where a defensible correspondence exists. Consistent labels do not eliminate uncertainty, but they make it possible to investigate disagreement, evaluate analytical methods, and identify where better definitions or additional measurements would improve the evidence.
Bring the evidence back to the decision
The practical outcome should be a short observation plan that another team can follow. It should name the decision, the required evidence, the responsible roles, and the conditions that trigger a field visit or further analysis. Keep the plan small enough to test, then revise it using the results of real inspections. A useful monitoring workflow improves because its assumptions are examined systematically, and its observations remain connected to decisions throughout the process.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.


