In many transportation data platforms, road network information is stored in relational or spatial databases, while time-series vehicle operation records are managed separately in distributed stores such as HBase. In this separated architecture, queri...
In many transportation data platforms, road network information is stored in relational or spatial databases, while time-series vehicle operation records are managed separately in distributed stores such as HBase. In this separated architecture, queries that trace trips through specific nodes or links must repeatedly perform joins or additional mapping, and the associated overhead becomes a major bottleneck as data volume grows. To alleviate these limitations, this study designs a three-tier graph data model (node–link–record) that represents the national standard node–link road network and time-series operation logs within a single graph, and empirically evaluates its practicality from the perspective of large-scale data ingestion.
The proposed model organizes road nodes, road links, and vehicle operation records as separate vertex tiers and directly connects inter-tier continuity using edges, enabling path-based exploration without relational joins. It is implemented on the distributed graph database JanusGraph, where real vehicle operation logs are transformed into graph structures through an integrated pipeline of preprocessing, map matching, and storage. On this basis, the study quantitatively analyzes how internal index configuration, insertion-related parameter tuning, multi-threading, and backend storage selection (HBase, Cassandra, ScyllaDB) affect ingestion throughput and latency.
Experimental results show that, without even minimal internal composite indexes on key identifier attributes used for inter-tier connections, repeated full scans during edge construction make ingestion practically infeasible, whereas indexing these essential ID attributes enables stable insertion. Tuning core parameter combinations, including batch loading, yields throughput improvements of several times over the default settings, and applying multi-threading achieves approximately 1.5× additional speedup compared to single-threaded insertion. In backend storage comparisons, ScyllaDB exhibits clearly higher ingestion throughput than HBase and Cassandra, particularly in the record tier. These findings indicate that the proposed three-tier graph model is practically applicable to large-scale time-series vehicle operation data, and that index design, internal parameter combinations, and backend storage choice jointly act as key design knobs governing ingestion performance.