Compressive Acquisition and Trajectory Quality in Connected Vehicle Data

01/10/2025

4 min de lecture

The penetration of connected vehicles (CV) and large‑scale GNSS/IMU telemetry makes trajectory data a cornerstone for mobility analytics, safety applications, eco‑driving, and infrastructure monitoring. Yet, such data often suffer from low sampling rates, GNSS outages, asynchronous IMU/GNSS timestamps, and vendor‑specific compression artifacts.

This paper proposes a unified and reproducible framework to evaluate and improve trajectory quality in connected vehicle datasets. We focus on compressed acquisition, physics‑aware reconstruction, and quality scoring, building bridges between three domains:

  • inertial simulation (RS3),
  • road‑network‑aware reconstruction (Huang et al., 2023),
  • sparse/compressive sampling in CV datasets (CompressiveCV*).

The contribution is threefold:

  1. A problem formulation linking sampling, compression, and spatial‑temporal consistency.
  2. A reconstruction framework combining compressive sensing (CS), inertial constraints, and topological priors.
  3. A standard‑compliant quality assessment pipeline integrated in Telemachus 0.2.

2. Related Work

2.1 GNSS/IMU fusion and trajectory estimation

Placeholder for citations and discussion (e.g., Kalman, invariant filtering, GNSS outages, IMU drift, SmartphoneIMUSpeed2025, DVSE).

2.2 Compressive sensing for mobility datasets

Placeholder for CompressiveCVData2018, CompressiveCVRecovery2018, sparse dictionaries, sampling theory.

2.3 Network‑constrained trajectory reconstruction

Summary of Huang2023-TransitTrajectoryReconstruction: passenger‑vehicle trajectories, hybrid GNSS/opportunistic sensing, graph‑based inference.

2.4 Data quality frameworks

Telemachus 0.2, event consistency, timestamp coherence, signal completeness.

3. Problem Formulation

Define the observed trajectory ( \mathbf{y}(t) ), true trajectory ( \mathbf{x}(t) ), sampling operator ( \Phi ), and reconstruction operator ( \Psi ).

Include placeholders:

  • Equation (1): sampling model
  • Equation (2): noise decomposition
  • Equation (3): regularization (sparsity + inertial + topology)

Introduce the notion of trajectory quality ( Q(\mathbf{x},\hat{\mathbf{x}}) ).

4. Proposed Framework

4.0 Compressive Pipeline Architecture (Reformulated)

The full end‑to‑end chain for connected‑vehicle compressive processing can be expressed as:

  1. Compressive acquisition — subsampling (uniform, random, burst), rate reduction, opportunistic GNSS/IMU availability.
  2. Inertial reconstruction — sparse dictionaries, IMU constraints, temporal smoothness priors.
  3. Network‑aware refinement — Huang2023 graph continuity, topology enforcement.
  4. Event extraction — braking/acceleration/turn events derived from reconstructed signals.
  5. Quality scoring — Telemachus‑compliant metrics integrating spatial, temporal and event consistency.

4.1 Overview

Pipeline diagram placeholder: RS3 simulation → Subsampling → CS reconstruction → Network‑aware refinement → Quality scoring → Telemachus export.

4.2 RS3 synthetic trajectories

Description placeholder: 10 Hz, realistic IMU noise, ground‑truth curvature, speed profiles.

4.3 Compressive acquisition

Define subsampling strategies (uniform, random, burst‑based).
Placeholder for Algorithm 1: Compressive Acquisition Strategy.

4.4 Reconstruction core

Sparse recovery using dictionaries + inertial constraints.
Network‑aware refinement following Huang et al. (graph continuity).
Placeholder for Algorithm 2: CS‑Network Reconstruction.

4.5 Integration with Telemachus

Describe pivot schema 0.2, GNSS/IMU alignment, metadata fields (telemetry_quality, sensor_alignment, sampling_strategy).

Représentation compressive dans Telemachus 0.2 (Ajout)

Telemachus 0.2 expose désormais des champs normalisés permettant de transporter les métadonnées compressives :

  • sampling_strategy : uniform / random / burst
  • compression_ratio : rapport d’échantillonnage effectif
  • reconstruction_confidence : indice de fiabilité post‑CS
  • event_consistency : cohérence des événements reconstruits

Ces attributs permettent d’aligner sources, pipelines compressifs et évaluations qualité dans un même format pivot.

5. Experimental Setup

5.1 Datasets

  • RS3 synthetic dataset (placeholder).
  • Telemachus‑Datasets real trajectories.

5.2 Baselines

  • Linear interpolation
  • Kalman smoothing
  • Huang‑style graph‑based reconstruction
  • Deep inertial models (DVSE)

5.3 Metrics

  • RMSE positionnel

  • vitesse cumulative drift

  • geometric fidelity (curvature error, radius deviation)

  • topology adherence score

  • coût énergétique smartphone (proxy basé sur la fréquence d’échantillonnage)

  • coût data (volume transmis / compression_ratio)

  • ratio qualité/coût (métrique composite normalisée Telemachus)

5.4 Experimental protocol

Parameters, sampling rates, noise models — placeholders.

6. Results (Placeholders)

6.1 Quantitative tables

Placeholder for Table 1, Table 2.

6.2 Reconstruction visuals

Placeholder for Figures 1–4: maps, speed profiles, error envelopes.

6.3 Sensitivity analysis

Placeholder text about robustness to subsampling factors 2×–10×.

7. Discussion

Critical analysis placeholder: trade‑offs, generalization limits, network effects, IMU bias sensitivity.

8. Conclusion and Future Work

Summarize benefits of compressive acquisition, integration with Telemachus, roadmap for full paper:

  • full experiments,
  • ablation studies,
  • network‑scale evaluations,
  • release of public RS3 dataset + code.

References

Placeholders retained for the main references:

  • SmartphoneIMUSpeed2025
  • Huang2023-TransitTrajectoryReconstruction
  • CompressiveCVData2018
  • CompressiveCVRecovery2018
Réseau 0 sortants 12 entrants 13 références

Sources · Liens sortants

Références bibliographiques

  • CompressiveCVData (2018) mobility
    Efficient Collection of Connected Vehicle Data with Precision Guarantees
  • CompressiveCVRecovery (2018) mobility
    Capture and Recovery of Connected Vehicle Data: A Compressive Sensing Approach
  • DrivingVolatility (2018) detection
    Extracting Useful Information from Connected Vehicle Data: Driving Volatility Measures
  • SmartphoneIMUSpeed (2025) mobility
    Inertial Sequence Learning for Vehicle Speed Estimation via Smartphone IMU
  • Huang (2023) mobility
    Reconstructing Transit Vehicle Trajectory Using High-Resolution GPS Data
  • Newson (2009) mobility
    Hidden Markov Map Matching Through Noise and Sparseness Newson, P., Krumm, J.
  • Raymond (2012) mobility
    Map Matching with Hidden Markov Model on Sampled Road Network Raymond, R., et al.
  • Podevijn (2020) mobility
    LoRaWAN Geo-Tracking Using Map Matching and Compass Heading Podevijn, G., et al.
  • Stolsmark (2021) mobility
    Collection and Use of Uncertain Data in a Mobile GNSS Context Stølsmark, R., et al.
  • Vasconcelos (2017) detection
    Smartphone-Based Outlier Detection: A Complex Event Processing Approach Vasconcelos, A., et al.
  • Cojocaru (2022) detection
    In-Vehicle Smartphone Sensing for Driving Behaviour Analysis (Part I) Cojocaru, I., et al.
  • Cojocaru (2022) detection
    In-Vehicle Smartphone Sensing for Driving Behaviour Analysis (Part II) Cojocaru, I., et al.
  • Sensors (2020) fusion
    An Evaluation of Smartphone Sensor Accuracy and Precision for Low-Cost Applications Anonymous, et al.

Cité par · Liens entrants

  • A016 — Hidden Markov Map Matching Through Noise and Sparseness
  • A038 — Smartphone Sensor Accuracy — Survey
  • A039 — HMM Map Matching on Sparse/Noisy GPS
  • A040 — Uncertain Mobile GNSS — Confidence Representation
  • A041 — LoRaWAN Geo-Tracking with Compass Fusion
  • A046 — Inertial Sequence Vehicle Speed Estimation
  • A060 — GNSS Measurement-Based Context Recognition for Vehicle Navigation using GRU
  • A061 — Compressive Sensing for Large-Scale Connected Vehicle Data
  • A062 — Capture and Recovery of Connected Vehicle Data via Compressive Sensing
  • B034 — Réduire par 5 la donnée télématique : l’acquisition compressive appliquée à la mobilité
  • L018 — 🚦 La télématique parle trop de dialectes différents.
  • L034 — Réduire par 5 les données télématiques… sans perdre la trajectoire