- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper proposes ARHR, a trajectory representation for route clustering. ARHR adds a few angular statistics, describing where a trajectory moves around a chosen landmark, to an existing harmonic embedding. Experiments on four traffic datasets and a few same-endpoint settings show clear gains over the harmonic embedding alone and results comparable to adding endpoint coordinates.
Critical strengths
- The paper identifies a clear weakness of harmonic trajectory embeddings and addresses it with a simple, training-free addition that greatly improves clustering over that baseline on several evaluated datasets.
Critical weaknesses
-
Incremental technical contribution. The new component appears to be an angular Fourier statistic concatenated with an existing harmonic representations. The idea is straightforward, and the current evaluation does not demonstrate clear advantages (Table 1 shows nearly identical average ARI for ARHR and endpoint-augmented harmonics, while Frechet achieves the best result).
-
Unclear added value of the angular features. Eq. (4) shows that when a path's angle around the landmark changes in only one direction, these features depend only on its start and end angles and net angular change. On rdb5, adding endpoint angles to the harmonic embedding already matches ARHR's 0.999 ARI. The paper does not compare these simpler features across the main benchmark or report how often and how much paths reverse their angular direction.
Questions for authors
- What is the Lyon benchmark? Please describe how the trajectories are generated and how the tasks and route classes are specified.
- On the museum data, h+P1 (0.920) clearly beats h+a (0.691). On Lyon, adding h to a lowers ARI from 0.734 to 0.536. Please explain this.
- Would ARHR apply to city-scale road networks (e.g., Porto or T-Drive, the kind of data t2vec and TrajCL target), where there is no natural central landmark? If not, the claims should be narrowed to local intersection-scale/landmark-centric clustering.
- Table 13 lists ARHR feature extraction at 2.3 s, much longer than some other baselines. Please explain this and clarify the "low per-trajectory feature-extraction cost" claim.