- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduces LANDER-Nav, a modular framework for multi-granularity open-vocabulary navigation. The method decomposes language instructions into components such as target, anchor, context, and relation, and divides the navigation process into three stages: "Evidence Grounding" for selecting semantic frontiers; "Entity Grounding" for disambiguating target instances via multi-query retrieval and spatial voting; and "Endpoint Grounding" for selecting reachable viewpoints with visible targets.
The method was evaluated on the LangMap and HM3D-OVON datasets. Results demonstrate performance improvements across various settings; notably, LANDER-Nav outperforms MTU3D in fine-grained multi-target navigation tasks. Additionally, the paper presents component ablation studies and a comparative analysis based on different Vision-Language Model (VLM) backbones.
Critical strengths
- A navigation problem of practical significance driven by application needs.
This paper addresses a key challenge in language-conditioned navigation: how to leverage contextual landmarks and spatial relationships to identify the correct target instance, rather than relying solely on object categories. The distinctions drawn between exploration, instance disambiguation, and endpoint selection are sound, and the overall framework is clearly articulated.
- Improvements for multi-target navigation tasks involving detailed descriptions.
On the LangMap benchmark, LANDER-Nav outperformed MTU3D; notably, in multi-target navigation scenarios featuring detailed descriptions, the Success Rate (SR) rose from 41.8% to 45.5%, and the Success weighted by Path Length (SPL) increased from 25.1% to 28.6%. Although the magnitude of improvement varied across other evaluation settings, these results provide empirical support for the proposed method.
Critical weaknesses
- Limited technical novelty and insufficient support for progressive grounding.
The framework primarily combines VLM-based frontier reranking, multi-query object retrieval with spatial voting, and geometry-based endpoint selection, all of which build on established techniques. More importantly, the claimed explicit spatial relationship grounding is not clearly demonstrated. The spatial voting mechanism mainly relies on object proximity, without showing how directional relationships such as "left of," "right of," or "above" are explicitly modeled. Similarly, endpoint selection considers visibility, clearance, and reachability, but does not clearly verify target-anchor relationships. Consequently, the technical distinction between LANDER-Nav and existing structured or scene-graph-based navigation methods remains unclear.
- Limited performance gains and insufficient evidence for the full framework.
While LANDER-Nav improves performance on detailed multi-goal tasks, gains elsewhere are modest or inconsistent. Its SR on Single-goal Concise (28.6%) is below PlaNaVid (31.4%), and its improvements on Single-goal Detailed and HM3D-OVON are limited. Moreover, multi-goal experiments compare only against MTU3D. The ablation results also raise concerns about the contribution of the complete framework: Entity Grounding alone achieves 44.4% overall SR and 33.2% Instance SR, compared with 45.5% and 33.3% for the full method. Without leave-one-out ablations, the additional benefits of Evidence and Endpoint Grounding remain insufficiently established.
Questions for authors
- How are spatial relationships explicitly modeled and verified?
Spatial voting mechanisms rely primarily on geometric proximity, whereas endpoint grounding focuses on the visibility and reachability of the target. Could the authors clarify how different target-anchor spatial relationships are explicitly distinguished and constrained? In particular, how does the framework handle relationships such as "to the left of," "to the right of," or "above," which cannot be adequately characterized by proximity alone?
- What are the additional benefits of integrating all three grounding modules?
According to Table 3, when using only entity grounding, the overall Success Rate (SR) and Instance SR are 44.4% and 33.2%, respectively; for the complete framework, the corresponding figures are 45.5% and 33.3%. These differences are relatively small, particularly regarding instance targets. Could the authors clarify the complementary contributions of evidence grounding and endpoint grounding, and explain whether their integration yields significant benefits beyond using entity grounding alone?
Given that the authors have not responded, I will maintain my original score.