<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Roadscape-based Route Recommender System using Coarse-to-fine Route Search</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Koji Kawamata</string-name>
          <email>t18m057@mail.ryukoku.ac.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kenta Oku</string-name>
          <email>okukenta@rins.ryukoku.ac.jp</email>
          <email>t18m057@mail.ryukoku.ac.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ryukoku University</institution>
          ,
          <addr-line>Otsu, Shiga</addr-line>
          ,
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2018</year>
      </pub-date>
      <fpage>23</fpage>
      <lpage>27</lpage>
      <abstract>
        <p>We propose the Roadscape-based Route Recommender System (R3), which provides diversified roadscape-based routes. Given starting and destination points, R3 provides four types of roadscapebased routes: rural-, mountainous-, waterside-, and urban-prior routes. To reduce the computational cost, we propose a coarse-toifne route search approach that consists of a roadscape-based clustering method, a roadscape cluster graph, a coarse-grained route search, and a fine-grained route search. We evaluated the performance of R3 using network data for a real road. The experimental results show that using coarse-grained route search can significantly reduce route search time.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>CCS CONCEPTS</title>
      <p>• Information systems → Social recommendation;</p>
    </sec>
    <sec id="sec-2">
      <title>INTRODUCTION</title>
      <p>Cars are driven not only for transportation but also for the
pleasure of it. Some people want to drive along the seaside or on rural
roads while enjoying their favorite landscape. We call such
roadside landscapes “roadscapes.” In such situations, it is not always
the best solution to provide the shortest or the fastest route. An
alternative solution is to provide routes with favored roadscapes
even if they involve a detour.</p>
      <p>Given starting and destination points, a route recommender
system provides routes from the starting point to the destination point.
The majority of traditional route recommender systems provide
the shortest routes [3, 7], the fastest routes [4, 5, 9, 11, 12], or
popular routes [1, 6, 8, 10]. As mentioned above, the shortest and the
fastest routes do not always satisfy the user’s demands. Systems
that recommend popular routes provide routes many people are
interested in. Wei et al. [8] extract popular routes by mining road
links many people are interested in from their trajectories. Such
route recommender systems consider the attractiveness of routes
based on the wisdom of crowds, without considering the content
features of routes.</p>
      <p>In this paper, we focus on the roadscape as a route feature and
propose the Roadscape-based Route Recommender System (R3),
which provides diversified routes on the basis of roadscapes. Given
starting and destination points, R3 provides four types of
roadscapebased routes: rural-, mountainous-, waterside-, and urban-prior
routes. For example, a user who likes waterside views can select
waterside-prior routes from the four types of routes provided. To
develop such a route recommender system, we have proposed a
method for estimating roadscapes of given road links. In
particular, we defined rural, mountainous, waterside, and urban elements
as the roadscape elements, which are basic elements that compose
a roadscape, through preliminary experiments. We defined a
roadscape vector each of whose elements corresponds to a roadscape
element and proposed a method for estimating such roadscape
vectors for given road links. We presuppose that R3 is to be used on
road network data with roadscape vectors.</p>
      <p>Traditional route searching algorithms, such as the Dijkstra
algorithm [2], are given the costs of road links and find a route that
minimizes the sum of their costs. The simplest approach is to
apply the traditional method and reduce the costs of the road links
having the targeted roadscape elements. However, there is a high
computational cost in applying such a method to a very large road
network.</p>
      <p>To reduce the computational cost, we propose a coarse-to-fine
route search approach. We focus on the concept that similar
roadscapes do not exist as fragments but in clusters. For example, there
are some areas composed of similar roadscape elements, such as
rural areas, mountainous areas, waterside areas, and urban areas.
Based on this characteristic, we expect that we can reduce the
computational cost by clustering similar roadscape areas in advance.</p>
      <p>In this approach, we firstly extract areas—roadscape clusters—
composed of similar roadscape elements by using a
roadscapebased clustering method. Secondly, we create a roadscape
cluster graph whose nodes correspond to the roadscape clusters and
whose links correspond to the links between roadscape clusters.
In the route searching process, given the roadscape cluster graph
and starting and destination points, we roughly find four types
of roadscape-based routes, which are the roadscape cluster sets
passed through, one for each roadscape element; we call this the
coarse-grained route search. Then, we find specific routes that
connect the roadscape clusters in each type of route; we call this the
ifne-grained route search.</p>
      <p>The contributions of this paper are as follows:</p>
      <p>We propose the Roadscape-based Route Recommender
System (R3), which provides diversified roadscape-based routes,
namely, rural-, mountainous-, waterside-, and urban-prior
routes.</p>
      <p>To reduce the computational cost, we propose a
coarse-toifne route search approach that consists of a roadscape-based
clustering method, a roadscape cluster graph, a coarse-grained
route search, and a fine-grained route search.</p>
      <p>We evaluate the performance of R3 using network data for a
real road. The results show that using coarse-grained route
search can significantly reduce route search time.
Definition 1: Road network. A road network is a directed
weighted graph G = ¹V ; Eº, where V is a set of road nodes
and E V V is a set of road links. A road node vi 2 V
represents an intersection or an endpoint of a road. A road
link ek = ¹vi ; vj º 2 E is a directed link from the starting
node vi to the ending node vj . A road link ek is assigned a
cost wk according to the length of the link.</p>
      <sec id="sec-2-1">
        <title>Definition 2: Roadscape element. Roadscape elements are</title>
        <p>basic elements that compose a roadscape. We define four
roadscape elements: rural, mountainous, waterside, and
urban elements. These elements were selected by preliminary
experimentation.1
Definition 3: Roadscape vector. A roadscape vector is
deifned as a four-dimensional probability vector each of whose
elements corresponds to one of the respective roadscape
elements. We define a roadscape vector of a road link ei
as s¹ei º = ¹sir ; sim ; siw ; siu º. Each element of the vector
denotes the probability of how strongly ei includes the
corresponding roadscape element. Therefore, the sum of the
values over all elements is 1.</p>
        <p>Definition 4: Roadscape cluster. A roadscape cluster Cj 2
C is represented by a set of road links having similar
roadscape vectors. A roadscape vector s¹Cj º of roadscape cluster
Cj is represented by the mean vector of the roadscape
vectors of the road links included in cluster Cj . Therefore, we
define s¹Cj º as follows:
s¹Cj º =
1</p>
        <p>
          ∑
jCj j i 2Cj
s¹ei º:
(
          <xref ref-type="bibr" rid="ref1">1</xref>
          )
Here, jCj j denotes the number of road links included in the
roadscape cluster Cj .
        </p>
        <p>Definition 5: Roadscape cluster graph. A roadscape cluster
graph is a directed weighted graph G = ¹V; Eº, where V
is a set of roadscape clusters Ci and E V V is a set of
links between roadscape clusters. A link lk = ¹Ci ; Cj º 2 E
is a directed link from the starting node Ci to the ending
node Cj . The road link lk is assigned a cost vector ωk =
¹ωkr ; ωm ; ωw ; ωku º based on the roadscape vector Cj of
endk k
ing roadscape cluster Cj . Each element of ωk denotes a cost
for the corresponding roadscape; these are used for
roadscapebased route searching. For example, ωkr is the cost
referenced when searching for rural-prior routes.</p>
      </sec>
      <sec id="sec-2-2">
        <title>Definition 6: Intra-cluster similarity of roadscape vector.</title>
        <p>
          The intra-cluster similarity is the mean similarity between
all pairs of road links included in the cluster. We denote the
intra-cluster similarity of roadscape cluster Cj as intra_sim¹Cj º.
The value of intra_sim¹Cj º is calculated as follows:
intra_sim¹Cj º =
cos¹s¹ei º; s¹ek ºº:
(
          <xref ref-type="bibr" rid="ref2">2</xref>
          )
1
        </p>
        <p>
          ∑ ∑
njCj j i 2Cj k 2Cj
Here, ei and ek are road links included in cluster Cj , and n
denotes the total number of links in the road network. The
1The preliminary experimentation to select the roadscape elements was done via
crowdsourcing. These four elements are specific to Japanese road network data.
Details are outside the scope of this paper.
value of cos¹s¹ei º; s¹ek ºº is calculated as follows:
cos¹s¹ei º; s¹ek ºº = s¹ei º s¹ek º :
js¹ei ºjjs¹ek ºj
(
          <xref ref-type="bibr" rid="ref3">3</xref>
          )
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>ROADSCAPE-BASED ROUTE</title>
    </sec>
    <sec id="sec-4">
      <title>RECOMMENDER SYSTEM</title>
    </sec>
    <sec id="sec-5">
      <title>System Overview 3.1</title>
      <p>Our proposed Roadscape-based Route Recommender System (R3)
provides four types of roadscape-based routes: rural-,
mountainous, waterside-, and urban-prior routes. Figure 1 shows a result
provided by R3. When a user inputs starting and destination points on
the map, the four types of roadscape-based routes are provided in
diferent colors.</p>
      <p>
        It is assumed that R3 will be used with a road network with
roadscape vectors. The steps of R3 are as follows:
(
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) Generate roadscape cluster graph based on road network
with roadscape vectors.
(
        <xref ref-type="bibr" rid="ref2">2</xref>
        ) Roughly find four types of roadscape-based routes in the
roadscape cluster graph based on the starting and
destination points that are input (coarse-grained route search).
(
        <xref ref-type="bibr" rid="ref3">3</xref>
        ) Find a detailed route that connects roadscape clusters in
each type (fine-grained route search).
(
        <xref ref-type="bibr" rid="ref4">4</xref>
        ) Recommend four types of routes in diferent colors on the
map.
      </p>
      <p>
        Here, step (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) can be performed ofline because this process does
not depend on the inputs. In the next sections, we describe steps
(
        <xref ref-type="bibr" rid="ref1">1</xref>
        )–(
        <xref ref-type="bibr" rid="ref3">3</xref>
        ) in detail.
3.2
      </p>
      <p>Generating Roadscape Cluster Graph
3.2.1 Roadscape-based Clustering. Given a road network, we
form roadscape clusters based on proximities of pairs of road links
and similarities between their roadscape vectors. Adjacent road
links belong to the same cluster if their similarity is greater than
or equal to a given threshold value. Figure 2 shows the result of
applying roadscape-based clustering to the road network of Awaji</p>
      <p>Island, Japan. Here, area A corresponds to a rural area, area B
corresponds to a mountainous area, area C corresponds to a waterside
area, and area D corresponds to an urban area.</p>
      <p>Algorithm 1 shows the pseudocode for roadscape-based
clustering. We explain the clustering process as performed by Algorithm 1
as follows:
Algorithm 1 Roadscape-based clustering.</p>
      <p>Require: Target link ei , Cluster ID k
1: function roadscapeClustering(ei , k )
2: Cluster ID of ei ( k
3: linkList ( getLink¹ei º: Get links adjacent to ei :
4: for each ej in linkList
5: if Cluster ID of ej = 0 then
6: if cos¹s ¹ei º; s ¹ej ºº &gt;= α then
7: roadscapeClustering¹ej; k º
8: end if
9: end if
10: end for
11: return 0
12: end function</p>
      <p>We randomly select a road link from the road network. Let ei
be the target link, and let ej be one of the links adjacent to ei .
Here, if two links are connected to a common node, the links are
considered adjacent. Furthermore, let s¹ei º and s¹ej º be roadscape
vectors of the respective links.</p>
      <p>
        The roadscape-based clustering algorithm is called as
roadscapeClustering¹ei ; kº. First, add k as the cluster ID of ei .
Second, get all links adjacent to ei , and set them into linkList.
For each link ej 2 linkList, perform the following process. If a
cluster ID has not been assigned to ej , cos¹s¹ei º; s¹ej ºº (Equation
(
        <xref ref-type="bibr" rid="ref3">3</xref>
        )) is calculated. If cos¹s¹ei º; s¹ej ºº is greater than or equal to the
threshold α , cluster ID k of ei is added as the cluster ID of ej .
Furthermore, roadscapeClustering¹ej ; k) is recursively called. The
above process is repeated until the cluster ID has been added to all
of the links in the road network.
      </p>
      <p>
        We define the roadscape cluster obtained by the above process
as Ck 2 C, where k corresponds to the cluster ID. In addition,
roadscape vector s¹Ck º of cluster Ck is calculated by Equation (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ).
node = roadscape cluster
link
      </p>
      <p>3.2.2 Generating Roadscape Cluster Graph. After extracting the
roadscape clusters, we create the adjacency matrix for all
roadscape clusters. The adjacency matrix for the roadscape clusters is
represented as the jC j jC j matrix A = »ai j ¼j C j j C j . If ai j = 1,
clusters Ci and Cj have at least one common node; otherwise, they
do not have a common node.</p>
      <p>We then create the roadscape cluster graph based on the
adjacency matrix. Figure 3 gives an example of the roadscape cluster
graph created for Awaji Island’s road network. Here, a node in the
roadscape cluster graph corresponds to a roadscape cluster, and a
link corresponds to the adjacency relationship between clusters.</p>
      <p>3.2.3 Assigning Costs to Roadscape Cluster Graph. In order to
execute the coarse-grained route search described in the next
section, we assign costs to the links of the roadscape cluster graph in
advance. A link cost is calculated based on the roadscape vector
of the roadscape cluster corresponding to the link’s destination. If
the targeted roadscape element of the next roadscape cluster
destination is emphasized, let its link cost be lower; on the other hand,
if it is not emphasized, let its link cost be higher. For example, for
a case in which a rural element is targeted, if the rural element of
the next roadscape cluster destination is emphasized, let its link
cost be lower; otherwise, let its link cost be higher. By assigning
costs in such a way, the route to the roadscape cluster where the
rural element is emphasized is more likely to be chosen in the route
search.</p>
      <p>
        A cost vector ωk of link lk = ¹Ci ; Cj º is calculated as follows:
ωk = dk ¹1
s¹Cj º2º:
(
        <xref ref-type="bibr" rid="ref4">4</xref>
        )
Here, dk is the length of link lk .
3.3
      </p>
    </sec>
    <sec id="sec-6">
      <title>Coarse-grained Route Search</title>
      <p>
        As the first search, we execute the coarse-grained route search
method. This method roughly finds four types of roadscape-based
routes in the roadscape cluster graph. The process is as follows:
(
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) Given starting and destination points, get roadscape
clusters and starting and destination clusters, which include the
starting and destination points, respectively.
      </p>
      <p>Mean route search time[s]
200 300
Without coarse-grained
route search</p>
      <p>α=0.95 **
irr-sgaeedn rch αα==00..9805 ****</p>
      <p>α=0.80 **
itcaohW trsaeeou α=0.75
α=0.70
α=0.65
**
**</p>
      <p>
        **
(
        <xref ref-type="bibr" rid="ref2">2</xref>
        ) For the targeted roadscape element, find a route that
minimizes the sum of the link costs related to the targeted
elements using Dijkstra’s algorithm [2] on the roadscape
cluster graph.
      </p>
      <p>
        (
        <xref ref-type="bibr" rid="ref3">3</xref>
        ) Repeat step (
        <xref ref-type="bibr" rid="ref2">2</xref>
        ) for each roadscape element.
      </p>
      <p>Thus, we obtain four types of coarse-grained routes as the
roadscape cluster sets that are passed through for each roadscape
element.
3.4</p>
    </sec>
    <sec id="sec-7">
      <title>Fine-grained Route Search</title>
      <p>
        As the second search, we execute the fine-grained route search
method for each coarse-grained route. This method finds detailed
routes that connect roadscape clusters. The process for each
targeted element is as follows:
(
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) Find common road nodes of each adjacent cluster in the
roadscape cluster sets captured by the coarse-grained route
search.
(
        <xref ref-type="bibr" rid="ref2">2</xref>
        ) Find the shortest route from the starting point to the first
common road node that is adjacent to the next cluster.
(
        <xref ref-type="bibr" rid="ref3">3</xref>
        ) While there are common road nodes, find the shortest route
from the common road node to the next common node.
(
        <xref ref-type="bibr" rid="ref4">4</xref>
        ) Find the shortest route from the last common node to the
destination point.
      </p>
      <p>
        (
        <xref ref-type="bibr" rid="ref5">5</xref>
        ) Generate a route that connects all the routes obtained.
Here, we again use Dijkstra’s algorithm [2] to find the shortest
routes. Finally, we obtain four types of fine-grained routes.
4
      </p>
    </sec>
    <sec id="sec-8">
      <title>RESULTS</title>
      <p>In this section, we evaluate the performance of the proposed R3
method using network data for a real road in Awaji Island, Japan.
The road network data are derived from OpenStreetMap,2 and they
include 102,506 road nodes and 212,050 road links for the area of
Awaji Island. For this area, roadscape vectors for all road links are
available on the web.3</p>
      <p>R3 introduces a coarse-grained route search as preprocessing to
reduce the route search time instead of performing a route search
on all road links. In this section, we compare the route search times
using coarse-grained route search with those not using it.</p>
      <p>First, we prepare the following five pairs of starting and
destination points.
2https://www.openstreetmap.org/
3https://zenodo.org/record/1405255#.W4Yyb-j7T-g
(a) ¹34:257575; 134:722549º ! ¹34:574902; 134:959632º
(b) ¹34:317774; 134:676412º ! ¹34:348304; 134:896255º
(c) ¹34:499798; 134:938260º ! ¹34:293801; 134:788816º
(d) ¹34:545838; 134:923368º ! ¹34:440009; 134:912038º
(e) ¹34:208185; 134:814500º ! ¹34:430861; 134:830634º
For each pair, we execute the route search algorithm that
emphasizes each roadscape element and measure the route search time.
We regard this execution as one trial. We execute this trial ten
times for each pair and calculate the mean of the route search times
across trials.</p>
      <p>We implemented the route search algorithm using Java and
managed the road network data using PostgreSQL 9.5. We conducted
experiments on a computer equipped with an Intel Core i5-6200U
CPU (2.8 GHz), 8 GB memory, 256 GB SSD, and Linux Mint 18.2.</p>
      <p>Figure 4 shows the mean route search times for methods with
and without coarse-grained route search. For the method with
coarsegrained route search, the figure includes the route search time for
each value of α . indicates that a significant diference ( p &lt;
0:01) could be confirmed when comparing with the method
without coarse-grained route search by the paired t -test (one-sided test).
We can see from Figure 4 that the route search time can be
shortened by using coarse-grained route search. The figure also shows
that the higher the value of α was, the shorter the route search time
was. In particular, when α = 0:95, the search time with
coarsegrained route search was 6:24 s, whereas it was 456 s when
coarsegrained route search was not used. Consequently, we can say that
the use of coarse-grained route search can significantly reduce route
search time.
5</p>
    </sec>
    <sec id="sec-9">
      <title>CONCLUSIONS</title>
      <p>In this paper, we have proposed a Roadscape-based Route
Recommender System (R3) that provides diversified roadscape-based
routes. Given starting and destination points, R3 provides four types
of roadscape-based routes: rural-, mountainous-, waterside-, and
urban-prior routes. To reduce computational costs, we proposed a
coarse-to-fine route search approach that consists of a
roadscapebased clustering method, a roadscape cluster graph, a coarse-grained
route search, and a fine-grained route search.</p>
      <p>We evaluated the performance of R3 using real road network
data with roadscape vectors in the area of Awaji Island. The results
show that using coarse-grained route search can significantly
reduce route search time. In the future, we will conduct user tests to
evaluate our system from the users’ perspective.</p>
    </sec>
    <sec id="sec-10">
      <title>ACKNOWLEDGMENTS</title>
      <p>This work was supported by JSPS KAKENHI Grant Numbers
JP15K12151 and JP16HO593.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Zaiben</given-names>
            <surname>Chen</surname>
          </string-name>
          , Heng Tao Shen, and
          <string-name>
            <given-names>Xiaofang</given-names>
            <surname>Zhou</surname>
          </string-name>
          .
          <year>2011</year>
          .
          <article-title>Discovering Popular Routes from Trajectories</article-title>
          .
          <source>In Proceedings of the 2011 IEEE 27th International Conference on Data</source>
          , Vol.
          <volume>4</volume>
          .
          <fpage>900</fpage>
          -
          <lpage>911</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Edsger</given-names>
            <surname>Wybe Dijkstra</surname>
          </string-name>
          .
          <year>1959</year>
          .
          <article-title>A Note on Two Problems in Connexion with Graphs</article-title>
          .
          <source>Numer. Math. 1</source>
          (
          <issue>1959</issue>
          ),
          <fpage>269</fpage>
          -
          <lpage>271</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Andrew</surname>
            <given-names>V Goldberg</given-names>
          </string-name>
          and
          <string-name>
            <given-names>Chris</given-names>
            <surname>Harrelson</surname>
          </string-name>
          .
          <year>2005</year>
          .
          <article-title>Computing the shortest path: A search meets graph theory</article-title>
          .
          <source>In Proceedings of the sixteenth annual ACM-SIAM symposium on Discrete algorithms</source>
          .
          <fpage>156</fpage>
          -
          <lpage>165</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Hector</given-names>
            <surname>Gonzalez</surname>
          </string-name>
          , Jiawei Han, and
          <string-name>
            <given-names>Xiaolei</given-names>
            <surname>Li</surname>
          </string-name>
          .
          <year>2007</year>
          .
          <article-title>Adaptive fastest path computation on a road network: a trafic mining approach</article-title>
          .
          <source>In Proceedings of the 33rd international conference on Very large data bases</source>
          .
          <volume>794</volume>
          -
          <fpage>805</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Evangelos</surname>
            <given-names>Kanoulas</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
            <given-names>Du</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tian Xia</surname>
            ,
            <given-names>and Donghui</given-names>
          </string-name>
          <string-name>
            <surname>Zhang</surname>
          </string-name>
          .
          <year>2006</year>
          .
          <article-title>Finding fastest paths on a road network with speed patterns</article-title>
          .
          <source>In Proceedings of the 22nd International Conference on Data Engineering</source>
          , Vol.
          <year>2006</year>
          .
          <volume>10</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Wuman</given-names>
            <surname>Luo</surname>
          </string-name>
          , Haoyu Tan, Lei
          <string-name>
            <surname>Chen</surname>
          </string-name>
          , and
          <string-name>
            <surname>Lionel</surname>
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Ni</surname>
          </string-name>
          .
          <year>2013</year>
          .
          <article-title>Finding time periodbased most frequent path in big trajectory data</article-title>
          .
          <source>In Proceedings of the 2013 ACM SIGMOD International Conference on Management of Data</source>
          .
          <volume>713</volume>
          -
          <fpage>724</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Michalis</given-names>
            <surname>Potamias</surname>
          </string-name>
          , Francesco Bonchi, Carlos Castillo, and
          <string-name>
            <given-names>Aristides</given-names>
            <surname>Gionis</surname>
          </string-name>
          .
          <year>2009</year>
          .
          <article-title>Fast shortest path distance estimation in large networks</article-title>
          .
          <source>In Proceedings of the 18th ACM conference on Information and knowledge management</source>
          .
          <volume>867</volume>
          -
          <fpage>876</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Ling-yin Wei</surname>
          </string-name>
          , Wen-chih
          <string-name>
            <surname>Peng</surname>
          </string-name>
          , Bo-chong
          <string-name>
            <surname>Chen</surname>
          </string-name>
          , and
          <string-name>
            <surname>Ting-wei Lin</surname>
          </string-name>
          .
          <year>2010</year>
          . Eleventh International Conference on
          <article-title>Mobile Data Management PATS : A Framework of Pattern-Aware Trajectory Search</article-title>
          .
          <source>In Mobile Data Management</source>
          .
          <fpage>362</fpage>
          -
          <lpage>377</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Ling-yin Wei</surname>
          </string-name>
          , Wen-chih
          <string-name>
            <surname>Peng</surname>
          </string-name>
          , Chun-shuo
          <string-name>
            <surname>Lin</surname>
          </string-name>
          , and
          <string-name>
            <surname>Chen-hen Jung</surname>
          </string-name>
          .
          <year>2009</year>
          .
          <article-title>Exploring Spatio-Temporal Features</article-title>
          .
          <source>In Advances in Spatial and Temporal Databases, Lecture Notes in Computer Science</source>
          .
          <volume>399</volume>
          -
          <fpage>404</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Ling-Yin</surname>
            <given-names>Wei</given-names>
          </string-name>
          , Yu Zheng, and
          <string-name>
            <surname>Wen-Chih Peng</surname>
          </string-name>
          .
          <year>2012</year>
          .
          <article-title>Constructing popular routes from uncertain trajectories</article-title>
          .
          <source>In Proceedings of the 18th ACM SIGKDD international conference on Knowledge discovery and data mining</source>
          .
          <volume>195</volume>
          -
          <fpage>203</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Jing</surname>
            <given-names>Yuan</given-names>
          </string-name>
          , Yu Zheng, Chengyang Zhang, and
          <string-name>
            <given-names>Wenlei</given-names>
            <surname>Xie</surname>
          </string-name>
          .
          <year>2010</year>
          .
          <article-title>T-drive: driving directions based on taxi trajectories</article-title>
          .
          <source>In Proceedings of the 18th SIGSPATIAL International Conference on Advances in Geographic Information Systems</source>
          .
          <volume>99</volume>
          -
          <fpage>108</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Jing</surname>
            <given-names>Yuan</given-names>
          </string-name>
          , Yu Zheng, Liuhang Zhang, XIng Xie, and
          <string-name>
            <given-names>Guangzhong</given-names>
            <surname>Sun</surname>
          </string-name>
          .
          <year>2011</year>
          .
          <article-title>Where to find my next passenger</article-title>
          .
          <source>In Proceedings of the 13th international conference on Ubiquitous computing</source>
          .
          <fpage>109</fpage>
          -
          <lpage>118</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>