Embedding-Only Uplink for Onboard Retrieval Under Shift in Remote Sensing

arXiv cs.CV / 4/7/2026

📰 NewsSignals & Early TrendsIdeas & Deep AnalysisModels & Research

Key Points

  • The paper studies an “embedding-only” uplink for onboard remote sensing, where the ground station transmits compact embeddings and metadata instead of raw pixels to avoid downlink bottlenecks.
  • It evaluates robustness under explicit remote-sensing distribution shifts, including cross-time, cross-event/location, multi-site cloud shifts (15 sites), and cross-city AOI holdouts.
  • Using OlmoEarth embeddings on a multi-task benchmark, the study finds the uplinked embeddings are the key enabler, but the best onboard decision module differs by task.
  • Results show kNN-style retrieval is significantly better for cloud classification, while class centroids are much stronger for temporal change detection.
  • The authors conclude that once embeddings are available onboard, systems can switch optimal heads per task without extra uplink cost, keeping telemetry under 1 KB per query.

Abstract

Downlink bottlenecks motivate onboard systems that prioritize hazards without transmitting raw pixels. We study a strict setting where a ground station uplinks only compact embeddings plus metadata, and an onboard system performs vector search to triage new captures. We ask whether this embedding-only pipeline remains useful under explicit remote-sensing shift: cross-time (pre/post-event), cross-event/location (different disasters), cross-site cloud (15 geographic sites), and cross-city AOI holdout (buildings). Using OlmoEarth embeddings on a scaled public multi-task benchmark (27 Sentinel-2 L2A scenes, 15 cloud sites, 5 SpaceNet-2 AOIs; 10 seeds), we find that all effective methods rely on the same uplinked embeddings, but the optimal decision head is task-dependent: kNN retrieval is significantly superior for cloud classification (0.92 vs. centroid 0.91; p<0.01, Wilcoxon), while class centroids dominate temporal change detection (0.85 vs. retrieval 0.48; p<0.01). These results show that embedding-only uplink is the key enabler--once embeddings are onboard, the system can select the best head per task at no additional uplink cost, with all telemetry under 1 KB per query.