- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
In this paper, the authors present a trajectory generation framework PathTraj, which decomposes language-conditioned trajectory generation into road-level planning and coordinate-level synthesis. A frozen language model supports endpoint inference and an autoregressive, graph-constrained route decoder. A diffusion model then generates coordinates conditioned on the route, instruction, and motion representations extracted from intermediate noisy trajectories.
Critical strengths
S1: The bridge between language and trajectory generation is well motivated. To be specific, PathTraj converts instructions into an explicit, graph-connected road route before synthesizing coordinates. Such representation is a good attempt to address the challenge of maintaining spatial coherence under language conditioning.
S2: According to the experiment results, the performance of PathTraj is superior in comparison against baselines. The improvements appear in both cities and extend beyond endpoint compliance to speed and acceleration distributions.
Critical weaknesses
W1: The comparison against ControlTraj may not be fair. According to the experiment results, PathTraj outperforms ControlTraj on instruction compliance and spatial fidelity, but the two methods don't have comparable structural conditioning. Appendix C.1 states that ControlTraj's RoadMAE-derived road embeddings are replaced with text embeddings, but PathTraj receives explicit guidance from a planned route. This removes a central component of ControlTraj and leaves unclear how much of the improvement comes from the proposed design.
W2: The motion realism results depend on a temporal setup that is not clearly explained. The reductions in speed and acceleration JSD are substantial and support one of the main claims. However, every trip is resampled to 200 points, and the authors do not clearly explain how timestamps are assigned afterward or how duration is determined for generated trips. Since these choices directly affect both speed and acceleration, it is difficult to tell whether the improvements reflect better motion modeling or the temporal assumptions used in evaluation.
Questions for authors
Q1. Please explain why the road conditioning was removed rather than retained alongside the text. Could you provide a comparison that preserves this conditioning, or supplies both generators with the same predicted route, to help establish where the gains come from?
Q2. How do you handle time when resampling each trip to 200 points and generating new trajectories?
3 comments
We greatly appreciate Reviewer ojF1’s thoughtful feedback and constructive suggestions, which have been instrumental in helping us refine our research and improve the clarity of our presentation. We have made every effort to thoroughly address each of your questions and concerns in our rebuttal.
We would sincerely welcome any additional comments or suggestions from Reviewer ojF1. Your continued feedback is extremely valuable in further strengthening the quality and clarity of our work. Furthermore, if you find that our responses have adequately resolved your concerns, we would be truly grateful if you would consider raising your score based on our detailed responses and additional explanations.
Response by Reviewer
I appreciate the effort made by the authors for addressing my concerns. For Q1, the authors explained why it was infeasible to conduct a comparison in which both models receive routes. For Q2, the authors provide additional details regarding time handling. My concerns are partially addressed.
Rebuttal
Thank you for your review. We have sincerely studied the weaknesses and questions raised, and we address them in detail below
Q1: removal of structured conditions
Thank you for raising the concern about removing structured road conditioning. PathTraj targets prompt-conditioned trajectory generation, where all trip requirements are provided in natural language rather than by directly supplying structured inputs. We therefore use natural language as the common condition for all models.
Regarding the original Controltraj, it is a route-conditioned generator. ControlTraj receives a road-segment route directly and generates GPS points along that route, but it does not predict the next segment or solve the route-generation problem. RoadMAE provides geometric embeddings of these supplied road segments, so the subsequent generation mainly interpolates or refines points along a known route. PathTraj instead first predicts endpoints and a road-segment route from the instruction, then generates GPS points along it. We therefore replace ControlTraj’s RoadMAE embeddings with language embeddings. Feeding the route directly to ControlTraj without requiring it to predict the route, as in its original setting, would give ControlTraj an unfair advantage.
We have not conducted a comparison in which both models receive routes. This would require adding a route-prediction module to ControlTraj or feeding PathTraj’s predicted route into ControlTraj, thereby changing the task scope to trajectory interpolation given a fixed route. The current comparison evaluates complete trajectory generation systems and does not isolate road conditioning from the coordinate generator. The ablation in Appendix D.2, Table 11 evaluates the contributions of the three designed components and supports their effectiveness. Removing route planning, motion guidance, or diffusion degrades the corresponding spatial, semantic, or motion metrics. We will clarify task scope in revised version.
Q2: time handling
Thank you for questioning about time handling. We handle temporal information through two steps: temporal refinement and fixed-length resampling. The time intervals between adjacent GPS observations in the raw data are approximately 1–5 seconds, most commonly about 3 seconds. To reduce the effects of irregular sampling, we interpolate between adjacent observations at 1-second intervals. This retains each trip’s start time, end time, and total duration T, as well as the order of movement.
We then resample each refined trip to N=200 points. The normalized time position of point j is uj=N−1j, j=0,…,N−1, and its timestamp is tjresampled=t0+ujT. If the refined trip has fewer than 200 points, we add points by interpolation; if it has more, we uniformly downsample it. This gives all trips a fixed input length while preserving their endpoints, temporal order, and total duration. During generation, the model outputs 200 trajectory points. Given the generated trip duration T, we assign timestamps using the same mapping: tj=t0+199jT, so adjacent generated points are separated by t=199T.
This preserves trip-level timing information, including each trip’s start and end times and total duration. Upsampling trajectories with 200 or fewer points does not discard observed points, whereas downsampling longer trajectories may smooth short-term timing and speed variation. This smoothing concern primarily affects trajectories with more than 200 points. As shown in Table 1, these trajectories are not majority in both datasets, so the overall effect is limited.
Table1