- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper introduces WideUAV, a benchmark for cross-view satellite-tile retrieval and target-extent grounding, comprising 3,505 satellite tiles and 112,160 UAV images. It combines wide satellite coverage with off-center targets and controlled variations in UAV altitude and heading. The authors also propose UNISAG, which integrates retrieval and grounding through shared visual representations and incorporates altitude and heading information for localization.
Critical strengths
WideUAV addresses a meaningful problem by combining satellite-tile retrieval with within-tile target localization over wide satellite regions with off-center targets. The proposed benchmark and accompanying method provide a useful foundation for future research.
Critical weaknesses
The rationale for the altitude-dependent box sizes and the practical assumptions behind gallery construction need further clarification. In addition, using the same rendering source for UAV and satellite images leaves uncertainty about how well the results generalize to real UAV imagery.
Questions for authors
-
Appendix A.4 maps UAV altitudes of 150, 200, 250, and 300 m to nominal box side lengths of 330, 414, 528, and 678 pixels, respectively. Could the authors clarify how these specific box sizes were determined?
-
The main evaluation provides each query with 100 candidate tiles, including its paired tile. In practical use, how would the geographic coverage of the satellite gallery be determined before localizing the query? Would this require prior knowledge of the operating area or an approximate UAV location? Does the method assume that the target is always within the predefined gallery?
-
Both the UAV and satellite images are generated using the same Google Earth rendering pipeline. Could the authors discuss whether this shared source reduces the difficulty of cross-view matching, and what implications it has for applying the method to real UAV imagery?
4 comments
Q3: Both the UAV and satellite images are generated using the same Google Earth rendering pipeline, which leaves uncertainty about how well the results generalize to real UAV imagery. Could the authors discuss whether this shared source reduces the difficulty of cross-view matching, and what implications it has for applying the method to real UAV imagery?
A3: When collecting UAV images in Google Earth, we enable the "3D Buildings" option to obtain textured 3D building models, whereas this option is disabled for satellite images. These different acquisition settings introduce clear visual and geometric differences between the two views. Moreover, WideUAV includes wide-area satellite coverage, off-center targets, and visually similar neighboring regions, making cross-view matching challenging despite the shared rendering environment.
To examine generalization to real UAV imagery, we conduct a zero-shot transfer experiment using 93 real UAV queries from SUES-200 at 150 m altitude, paired with corresponding wide-area Google Earth satellite tiles. UniSAG and eight external baselines are trained exclusively on WideUAV and evaluated on SUES-200 without fine-tuning, using the same model weights. Each target region uses a pixel box, and headings are estimated from the paired images and quantized to . The 93 non-overlapping satellite tiles are supplemented with negative tiles to form a 100-candidate gallery. On WideUAV, we report the 13-city macro R@1 (from Table 15, lines 927–943) alongside paired-tile oracle mIoU. All grounding baselines and UniSAG receive the same heading and altitude inputs.
| Model | WideUAV R@1 (%) | WideUAV mIoU (%) | SUES-200 R@1 (%) | SUES-200 mIoU (%) |
|---|---|---|---|---|
| CLIP | 11.45 | – | 6.45 | – |
| SigLIP2 | 9.02 | – | 5.38 | – |
| Sample4Geo (Retrieval) | 10.88 | – | 5.38 | – |
| DetGeo | – | 4.78 | – | 6.00 |
| TROGeo | – | 4.31 | – | 3.17 |
| Sample4Geo (Grounding) | – | 6.71 | – | 9.56 |
| TransGeo | 15.42 | 3.91 | 8.60 | 3.00 |
| UnifyGeo | 8.60 | 3.26 | 4.30 | 5.50 |
| UniSAG (full) | 24.55 | 19.36 | 30.11 | 17.52 |
As shown above, UniSAG achieves 30.11% R@1 and 17.52% mIoU on real SUES-200 UAV queries, outperforming the strongest corresponding baselines by 21.51 and 7.96 percentage points, respectively. These results demonstrate that UniSAG retains its retrieval and grounding advantages on real UAV imagery without adaptation, rather than relying exclusively on Google Earth-generated UAV queries. We have clarified the acquisition settings in Appendix A.1 (lines 729–735) and added the zero-shot transfer experiment in Appendix C.3 (lines 959–1006; Table 17 at lines 981–994) of the revised manuscript.
Thank you for your detailed response. My concerns have been addressed, and I will maintain my current positive rating.
We sincerely thank you for the positive follow-up and are delighted that our response and revisions have fully addressed your concerns. We truly appreciate your recognition of the application value of our work, as well as your continued support and constructive feedback throughout the review process.
We thank the reviewer for the constructive feedback and thoughtful suggestions. The revised manuscript has been uploaded, with all revisions highlighted in blue for ease of reference. Below, we provide point-by-point responses to each comment.
Q1: The rationale for the altitude-dependent box sizes needs further clarification. Appendix A.4 maps UAV altitudes of 150, 200, 250, and 300 m to nominal box side lengths of 330, 414, 528, and 678 pixels, respectively. Could the authors clarify how these specific box sizes were determined?
A1: The bounding-box centers are determined from the target coordinates in the satellite images, while their side lengths are obtained through manual calibration of the common target region observed across UAV views, rather than directly calculated from altitude. Specifically, for each UAV altitude, we first select four UAV views with headings of 0∘, 90∘, 180∘, and 270∘. In each view, we identify a ground reference point near the bottom-center pixel (1920,2160) of the 3840×2160 UAV image and locate its corresponding position in the north-up satellite image. These four reference positions define the boundaries of the target region in the satellite image. We then manually calibrate a square bounding box to enclose this region, obtaining nominal side lengths of 330, 414, 528, and 678 pixels for altitudes of 150, 200, 250, and 300 m, respectively.
Since the camera intrinsics, tilt, and satellite sampling scale are fixed for each altitude, these calibrated sizes can be reused across different target locations. Moreover, Google Earth's
LookAtparameter keeps the camera focused on the same geographic target center across different headings and altitudes, ensuring consistent target-region correspondence across the 32 UAV views. The resulting annotations and coordinate transformations are manually checked for spatial consistency. We have clarified the camera configuration and bounding-box calibration procedure in Appendices A.3 (lines 752–756) and A.4 (lines 766–787) of the revised manuscript.Q2: The practical assumptions behind gallery construction need further clarification. The main evaluation provides each query with 100 candidate tiles, including its paired tile. In practical use, how would the geographic coverage of the satellite gallery be determined before localizing the query? Would this require prior knowledge of the operating area or an approximate UAV location? Does the method assume that the target is always within the predefined gallery?
A2: Thank you for these questions. First, regarding gallery coverage, the satellite gallery is defined based on the UAV's planned operating area, following the area-of-interest formulation of VIGOR. For example, if a UAV is deployed in a particular urban region, satellite tiles covering that region can be prepared in advance and used for all UAV queries. Second, regarding prior location information, the 100-tile main setting is a controlled sampling evaluation (covering ∼78,km2), whereas in practical deployment our method requires knowledge of the general operating area, but does not require the approximate location of each UAV query. All queries search the same satellite gallery without query-specific location information. If approximate location information is available, it can optionally narrow the search. Third, regarding whether the target is within the gallery, our current evaluation assumes that the satellite gallery contains the correct tile for each UAV query. If the target lies outside the gallery coverage, the current method does not explicitly identify such cases.
To further clarify the distinction between controlled evaluation and practical gallery construction, we evaluate UniSAG on 13 fixed neighboring-city galleries (Appendix C.2, lines 911–943; 37,248 queries across 1,165 tiles) and on the complete 2,804-tile test gallery (Section 5.3, lines 472–479; Table 10, lines 498–505), without query-specific gallery filtering. UniSAG (full) achieves 24.55% macro R@1 (24.12% micro R@1) on the 13-city benchmark and 34.83% R@1 (14.65% uIoU) on the complete 2,804-tile gallery. We have clarified gallery construction and evaluation assumptions in Section 5 (lines 288–290) and Appendix C.2 (lines 912–916) of the revised manuscript.