<!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>PersTour: A Personalized Tour Recommendation and Planning System</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>CCS Concepts</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tour Recommendations</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Trip Planning</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Personalization</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>User Interests</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>City/POI Data</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computing and Information Systems, The University of Melbourne</institution>
          ,
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Figure 1: PersTour System Architecture</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Kwan Hui Lim</institution>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Recommended Tour</institution>
          ,
          <addr-line>Listing</addr-line>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Recommended Tour</institution>
          ,
          <addr-line>Map</addr-line>
        </aff>
        <aff id="aff5">
          <label>5</label>
          <institution>School of Computer Science and Information Technology, RMIT University</institution>
          ,
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff6">
          <label>6</label>
          <institution>Victoria Research Laboratory</institution>
          ,
          <addr-line>NICTA / Data61</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Touring is a popular but time-consuming activity, due to the need to identify interesting attractions or Places-of-Interest (POIs) and structure these POIs in the form of a timeconstrained tour itinerary. To solve this challenge, we propose the Personalized Tour Recommendation and Planning (PersTour) system. The PersTour system is able to plan for a customized tour itinerary where the recommended POIs and visit durations are personalized based on the tourist's interest preferences. In addition, tourists have the option to indicate their trip constraints (e.g., a preferred starting/ending location and a specific tour duration) to further customize their tour itinerary.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>Tourism is a popular leisure activity with the main aim of
visiting interesting attractions in foreign cities. For a tourist
visiting an unfamiliar city, there are numerous challenges
such as: (i) identifying attractions or Places-of-Interest (POIs)
that appeal to his/her interest preferences, rather than
simply visiting popular POIs; (ii) structuring these POIs as
a tour itinerary that considers the tourist’s preferences for
starting/ending locations and time constraints for touring;
and (iii) providing detailed directions on how to get from
one POI to another, including recommendations for POI
visit durations based on the tourist interest preferences.</p>
      <p>To alleviate these challenges faced by tourists, we propose
the Personalized Tour Recommendation and Planning
(PerData Collection/Analysis</p>
      <p>Photo Crawler</p>
      <p>Photo</p>
      <p>Analytics
Tour Recommender</p>
      <p>ACO-based</p>
      <p>Recommender</p>
      <p>
        ReWcoembmSeenrvdiacteion
sTour) System. While there exist various interesting tour
planning applications [
        <xref ref-type="bibr" rid="ref10 ref11 ref13 ref14 ref15 ref2 ref4">14, 4, 13, 11, 2, 10, 15</xref>
        ], our PersTour
system differs from them in one or more of the following
ways: (i) tourists are able to select any starting/ending
location (instead of a specific POI, which the tourist may be
unfamiliar with) and PersTour will recommend an itinerary
that starts/ends at a POI near that selected location; (ii) in
addition to a personalized itinerary recommendation
(comprising POIs of interest to the tourist), PersTour also
personalizes the recommended visit duration at each POI based
on the tourist’s interest preferences; and (iii) PersTour uses
publicly available geo-tagged photos and Wikipedia to
determine POI-related statistics and information.
1.1
      </p>
    </sec>
    <sec id="sec-2">
      <title>Contributions</title>
      <p>Our main contribution is in developing the PersTour
system (Fig. 1) that is able to recommend POIs that are
interesting to the tourist and plan these POIs in the form of a
tour itinerary. The key features of this system are as follows:
• Able to consider tourist trip constraints such as
starting and ending at specific locations (e.g., near the
tourist’s hotel) and having limited time for touring.
• Utilizes geo-tagged photos and Wikipedia to: (i)
determine the popularity of POIs; (ii) derive the
average time tourists spend at each POIs; and (iii) classify
POIs into distinct categories.
• Able to recommend tours based on either POI
popularity or tourist interest preferences. In addition,
recommended POI visit durations are tailored based on
the interest levels of the tourist, i.e., a longer visit
duration for POIs that are interesting to the tourist.
• Adapted the Ant Colony Optimization algorithm for
the purpose of tour recommendation, with
considerations for trip constraints and interest preferences.
• Recommendation results are displayed in an intuitive
graphical and textual form (Fig. 2). The graphical
form allows for a quick overview of the tour itinerary
on a map, while the textual form provides detailed
information about getting from one POI to another.</p>
    </sec>
    <sec id="sec-3">
      <title>SYSTEM ARCHITECTURE</title>
      <p>
        Our PersTour system was developed as a web-based
application with a responsive interface that allows for viewing
on desktops, tablets or mobile phones. The front-end
component was developed using HTML, PHP, jQuery and the
Google Maps API [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], while the back-end was developed
using Python, Java and PHP. Our PersTour system comprises
three main components, namely:
• Data Collection and Analysis Component. This
back-end component is mainly responsible for the
retrieval of geo-tagged photos and analyzing these photos
to infer POI popularity, average POI visit durations
and POI categories.
• Tour Recommendation Component. This
backend component uses the processed POI data (from
the Data Collection and Analysis component) for
recommending and planning personalized tour itineraries
that are then passed to the User Interface component.
• User Interface Component. This front-end
component solicits the trip constraints and interest
preferences from the tourist, then communicates with the
Tour Recommendation component to obtain a
personalized tour itinerary, which is then displayed to the
tourist.
      </p>
      <p>In the following sections, we will describe each component
in greater detail.
2.1</p>
    </sec>
    <sec id="sec-4">
      <title>Data Collection and Analysis Component</title>
      <p>The Data Collection and Analysis component performs
two main tasks, which are: (i) the crawling of geo-tagged
photos from the Flickr photo sharing website; and (ii) the
analysis of these photos to infer the popularity of POIs,
average POI visit duration and the interest categories associated
with each POI.</p>
      <p>
        Data collection. For the first task, we are interested in
all photos taken within a specific city of interest, particularly
the associated meta-data such as the latitude/longitude
coordinates, photo time taken and photo owner/taker.1 The
usefulness of geo-tagged photos for tour recommendation
purposes has also been demonstrated in many recent
research works [
        <xref ref-type="bibr" rid="ref12 ref3 ref8">3, 8, 12</xref>
        ]. A future enhancement would involve
the use of computer vision techniques to analyze the
photos themselves to determine the number of humans in each
photos (i.e., travelling alone, in pairs or larger groups) and
demographic details (e.g., age group, gender, etc).
1While we use Flickr geo-tagged photos for the purpose of
this system demonstration, our PersTour system can be
easily generalized to other photo sharing sites (e.g., Instagram)
or any social media that is tagged with geo-location
information (e.g., geo-tagged tweets).
      </p>
      <p>Data analysis. For the second task, we analyze the
meta-information of each photo to determine the popularity
of each POI based on the number of photos taken at each
POI, i.e., a proxy for real-life POI visits as the user has to
visit the POI to take a photo.2 We are also able to
determine the amount of time spent visiting each POI based on
the time difference between the first and last photo taken
at a POI. Lastly, we utilize Wikipedia to derive the
category (e.g., Shopping, Entertainment, Cultural, Structures,
Sports and Parks) that each POI belongs to, based on the
Wikipedia article describing the POIs in each city.</p>
      <p>These two tasks (data collection and data analysis) can
then be conducted for each city of interest. Upon
completion, the results of the analysis are provided to the Tour
Recommendation component, which utilizes the computed
POI popularity, POI categories, distance between POIs, and
average POI visit duration for recommending and planing
tour itineraries. We next discuss the details of the Tour
Recommendation component.
2.2</p>
    </sec>
    <sec id="sec-5">
      <title>Tour Recommendation Component</title>
      <p>Using the POI-related information provided by the Data
Collection and Analysis component, the Tour
Recommendation component recommends and plans a tour itinerary
according to the interest preferences and trip constraints of
the tourist. The interest preferences corresponds to the POI
categories in the city, while trip constraints are in terms of
the tourist’s preferred starting/ending location and available
touring time.</p>
      <p>
        The back-end tour recommendation algorithm is based
on a modified version of the Ant Colony Optimization
algorithm [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. We first discuss the basic Ant Colony
Optimization algorithm before describing our proposed modifications
to adapt it for our purpose of personalized tour
recommendation and planning. The basic Ant Colony Optimization
algorithm utilizes a number of agents (ants) that start from
a specific POI with the aim to finding the best path to a
desired destination. This algorithm works in the following
main steps:
1. At the start of the algorithm, all agents initially select
the next POI to visit (based on the utility of visiting
that POI), until they reach the destination.
2. At the end of Step 1, the best path taken among all
agents is selected and remembered for a period of time,
before being gradually forgotten.
3. Steps 1 and 2 are then repeated for a fixed number
of iterations. The main difference is that the selection
of the next POI to visit (i.e., Step 1) will be biased
towards paths that have been taken recently.
      </p>
      <p>
        The intuition behind the Ant Colony Optimization
algorithm is that agents are more likely to follow a path that is
“better” and has been taken recently. This preference
subsequently leads to the positive reinforcement of choosing a
single path over time, resulting in that path being selected as
the best solution. Our modifications to the Ant Colony
Optimization algorithm are largely based on our earlier work [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]
and include the following: (i) the utility of each POI is based
on a combined POI popularity score and tourist interest
2We only use publicly available data and do not release any
personal information in our subsequent recommendations.
alignment; and (ii) the cost of travelling from one POI to
another is based on a fixed travelling cost and dynamic POI
visit duration (personalized based on tourist interest levels).
As we currently focus on city tours, we compute travelling
costs based on the transport mode of walking but this can
be extended to other transport modes such as cycling and
cars by changing the appropriate travelling speeds. In most
cases, this algorithm takes less than 0.5 seconds to
recommend and plan a personalized tour.
2.3
      </p>
    </sec>
    <sec id="sec-6">
      <title>User Interface Component</title>
      <p>The User Interface component serves three main
responsibilities, namely: (i) obtaining user inputs in the form of
the tourist’s trip constraints (starting/ending location and
available touring time) and their interest preferences; (ii)
communicating with the Tour Recommendation component
by providing the tourist’s trip constraints and interest
preferences, and retrieving the recommended tour itinerary; (iii)
displaying the recommended tour itinerary in an easy to
understand visual and textual format.</p>
      <p>Obtaining user input. For the first task, a tourist can
pick a preferred starting and ending location by simply
clicking on any point on the map. Similarly, the tourist can enter
a desired tour start time and select a preferred tour duration.
For a more personalized tour, the tourist is also able to
indicate their interest preferences via slider bars that represent
their interest level in the six POI categories (Shopping,
Entertainment, Cultural, Structures, Sports and Parks). The
slider bars allow tourists to state their interest level at
varying levels, ranging from “not interested” to “very interested”,
which is represented by values of 1 and 100, respectively. By
default, all interest levels are set to a neutral “neither
interested nor uninterested”, i.e., a value of 50.</p>
      <p>Communication between components. The second
task commences when the tourist clicks on the “Plan Tour
Itinerary” button. Upon clicking, the User Interface
component makes a web service call to the Tour Recommendation
component, along with the various trip constraints and
interest preferences provided. In turn, the Tour
Recommendation component invokes its recommendation algorithm to
plan a personalized tour based on the provided parameters.
This personalized tour is then returned to the User Interface
component in the form of a JSON response, containing the
recommended POIs and the time to spend at each POI.</p>
      <p>Displaying recommendation results. For the third
task, the User Interface component parses the returned JSON
response for display in a visual and textual format.
Utilizing the Google Maps API, the visual representation is in
the form of waypoints (POIs) that are plotted on a map
and connected lines that indicate the route to take between
POIs. The textual representation provides more
information on the recommended tour, indicating the time to arrive
at and depart each POI, along with the name and category
of each POI. In addition, the tourist is also able to click on
the “information” icon to the right of each POI for more
detailed step-by-step directions, i.e., which road to take, how
far to travel and which road junctions to turn at.</p>
    </sec>
    <sec id="sec-7">
      <title>USE CASE SCENARIOS</title>
      <p>As part of our system demonstration, we highlight two
scenarios where a tourist might use PersTour to obtain a
popularity-based and interest-based tour recommendations.</p>
      <p>Consider a tourist Alice who is staying at The Sebel
Melbourne Flinders Lane and is planning for a tour that starts
near her hotel. Using our PersTour system, she can simply
click on the location of her hotel (or anywhere on the map)
as her desired starting/ending point. Furthermore, Alice
selects a starting time of 10am, a tour duration of 3 hours
and then clicks on the “Plan Tour Itinerary” button to get
a customized tour itinerary recommendation. Based on the
selected starting/ending location, tour start time and
preferred tour duration, PersTour recommends a set of popular
POIs to visit within Alice’s preferred tour duration. This
recommendation is displayed as a graphical tour itinerary
on the map as well as in textual form with detailed
information about the POI visit sequence with the appropriate time
to arrive at and depart from each POI. If Alice requires more
detailed directions, clicking on the “information” icon beside
each POI listing will display a set of detailed instructions
for directions.
3.2</p>
    </sec>
    <sec id="sec-8">
      <title>Interest-based Tours</title>
      <p>Consider another tourist Bob who prefers a more
personalized tour based on his specific interest preferences.
Similar to what Alice has done, Bob also selects his preferred
starting/ending point, tour start time and preferred tour
duration. In addition, Bob can indicate his interested
preferences via a set of slider bars that correspond to each POI
interest categories. For example, Bob is very interested in
Sports and Parks, moderately interested in Shopping and
Entertainment, and less interested in Structures and
Cultural. As such, Bob adjusts the slider bars for each POI
interest category accordingly before clicking on the “Plan
Tour Itinerary” button. In this case, PersTour takes into
account Bob’s interest preferences and recommends a
personalized tour itinerary comprising POIs that are more likely
to include POIs of the Sports and Parks categories and less
of the Structures and Cultural categories. Similarly,
PersTour recommends a longer duration to spend at POIs of
the Sports and Parks categories and a shorter duration at
POIs of the Structures and Cultural categories, given Bob’s
interest preferences.</p>
    </sec>
    <sec id="sec-9">
      <title>CONCLUSION AND FUTURE WORK</title>
      <p>In this paper, we proposed the PersTour system for
recommending and planning personalized tour itineraries. This
system comprises three main components that perform the
following functions, namely: (i) a Data Collection and
Analysis component that uses geo-tagged photos and Wikipedia
to derive POI-related statistics and information; (ii) a Tour
Recommendation component that uses a modified Ant Colony
Optimization algorithm to recommend tour itineraries, which
adhere to trip constraints and consider interest preferences;
and (iii) a User Interface component that uses an intuitive
graphical and textual interface to solicit user input and
display recommendation results. In addition, the PersTour
system is able to recommend a suitable starting/ending POI
based on a tourist-selected location and also personalizes
the recommended POI and visit duration based on tourist
interest preferences.</p>
      <p>
        Some future work to enhance the PersTour system
includes the following: (i) incorporate restaurant visits (e.g.,
breakfast, lunch and dinner) and consider POI visiting costs
(e.g., entrance fees) as part of tour recommendation; (ii)
cater for tour recommendations to groups of tourists with
diverse interest preferences, in the same spirit as that of [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ];
(iii) automatically build a tourist interest profile, possibly by
analyzing a tourist’s social media posts such as in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]; and
(iv) apart from POI popularity and tourist interest, also
consider the beauty, peacefulness and enjoyability of routes
taken in a tour [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>Acknowledgments. NICTA is funded by the Australian
Government through the Department of Communications and the
Australian Research Council through the ICT Centre of
Excellence Program. The authors thank the anonymous reviewers
for their useful comments and the support of Google Australia
through a Google Australia PhD Travel Scholarship.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>N.</given-names>
            <surname>Banerjee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Chakraborty</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Dasgupta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mittal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Joshi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Nagar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rai</surname>
          </string-name>
          , and
          <string-name>
            <surname>S. Madan.</surname>
          </string-name>
          <article-title>User interests in social media sites: an exploration with micro-blogs</article-title>
          .
          <source>In Proc. of CIKM'09</source>
          , pages
          <fpage>1823</fpage>
          -
          <lpage>1826</lpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>I.</given-names>
            <surname>Brilhante</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Macedo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Nardini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Perego</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Renso</surname>
          </string-name>
          .
          <article-title>TripBuilder: A tool for recommending sightseeing tours</article-title>
          .
          <source>In Proc. of ECIR'14</source>
          , pages
          <fpage>771</fpage>
          -
          <lpage>774</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>I. R.</given-names>
            <surname>Brilhante</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Macedo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Nardini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Perego</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Renso</surname>
          </string-name>
          .
          <article-title>On planning sightseeing tours with TripBuilder</article-title>
          .
          <source>Information Processing &amp; Management</source>
          ,
          <volume>51</volume>
          (
          <issue>2</issue>
          ):
          <fpage>1</fpage>
          -
          <lpage>15</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L.</given-names>
            <surname>Castillo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Armengol</surname>
          </string-name>
          , E. Onaind´ıa, L. Sebastia´,
          <string-name>
            <surname>J.</surname>
          </string-name>
          <article-title>Gonz´alez-</article-title>
          <string-name>
            <surname>Boticario</surname>
            ,
            <given-names>A</given-names>
          </string-name>
          . Rodr´ıguez, S. Ferna´ndez,
          <string-name>
            <given-names>J. D.</given-names>
            <surname>Arias</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Borrajo</surname>
          </string-name>
          . SAMAP:
          <article-title>An user-oriented adaptive system for planning tourist visits</article-title>
          .
          <source>Expert Systems with Applications</source>
          ,
          <volume>34</volume>
          (
          <issue>2</issue>
          ):
          <fpage>1318</fpage>
          -
          <lpage>1332</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Dorigo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Birattari</surname>
          </string-name>
          , and
          <string-name>
            <given-names>T.</given-names>
            <surname>Stu</surname>
          </string-name>
          <article-title>¨tzle. Ant colony optimization</article-title>
          .
          <source>IEEE Computational Intelligence Magazine</source>
          ,
          <volume>1</volume>
          (
          <issue>4</issue>
          ):
          <fpage>28</fpage>
          -
          <lpage>39</lpage>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Google. Google maps API</surname>
          </string-name>
          ,
          <year>2016</year>
          . https://developers.google.com/maps/.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>K. H.</given-names>
            <surname>Lim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Leckie</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Karunasekera</surname>
          </string-name>
          .
          <article-title>Personalized tour recommendation based on user interests and points of interest visit durations</article-title>
          .
          <source>In Proc. of IJCAI'15</source>
          , pages
          <fpage>1778</fpage>
          -
          <lpage>1784</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>K. H.</given-names>
            <surname>Lim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Leckie</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Karunasekera</surname>
          </string-name>
          .
          <article-title>Towards next generation touring: Personalized group tours</article-title>
          .
          <source>In Proc. of ICAPS'16</source>
          , pages
          <fpage>412</fpage>
          -
          <lpage>420</lpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>D.</given-names>
            <surname>Quercia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Schifanella</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L. M.</given-names>
            <surname>Aiello</surname>
          </string-name>
          .
          <article-title>The shortest path to happiness: Recommending beautiful, quiet, and happy routes in the city</article-title>
          .
          <source>In Proc. of HT'14</source>
          , pages
          <fpage>116</fpage>
          -
          <lpage>125</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>I.</given-names>
            <surname>Refanidis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Emmanouilidis</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Sakellariou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Alexiadis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.-A.</given-names>
            <surname>Koutsiamanis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Agnantis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Tasidou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Kokkoras</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P. S.</given-names>
            <surname>Efraimidis</surname>
          </string-name>
          . myVisitPlanner GR:
          <article-title>Personalized itinerary planning system for tourism</article-title>
          .
          <source>In Proc. of SETN'14</source>
          , pages
          <fpage>615</fpage>
          -
          <lpage>629</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>R.</given-names>
            <surname>Schaller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Harvey</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Elsweiler</surname>
          </string-name>
          .
          <article-title>Recsys for distributed events: investigating the influence of recommendations on visitor plans</article-title>
          .
          <source>In Proc. of SIGIR'13</source>
          , pages
          <fpage>953</fpage>
          -
          <lpage>956</lpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>E.</given-names>
            <surname>Spyrou</surname>
          </string-name>
          and
          <string-name>
            <given-names>P.</given-names>
            <surname>Mylonas</surname>
          </string-name>
          .
          <article-title>A survey on flickr multimedia research challenges</article-title>
          .
          <source>Engineering Applications of Artificial Intelligence</source>
          ,
          <volume>51</volume>
          :
          <fpage>71</fpage>
          -
          <lpage>91</lpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>G.</given-names>
            <surname>Tumas</surname>
          </string-name>
          and
          <string-name>
            <given-names>F.</given-names>
            <surname>Ricci</surname>
          </string-name>
          .
          <article-title>Personalized mobile city transport advisory system</article-title>
          .
          <source>In Information and Communication Technologies in Tourism</source>
          , pages
          <fpage>173</fpage>
          -
          <lpage>183</lpage>
          . Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>P.</given-names>
            <surname>Vansteenwegen</surname>
          </string-name>
          and
          <string-name>
            <given-names>D. V.</given-names>
            <surname>Oudheusden</surname>
          </string-name>
          .
          <article-title>The mobile tourist guide: An OR opportunity</article-title>
          .
          <source>OR Insight</source>
          ,
          <volume>20</volume>
          (
          <issue>3</issue>
          ):
          <fpage>21</fpage>
          -
          <lpage>27</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>A.</given-names>
            <surname>Yahi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Chassang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Raynaud</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Duthil</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D. H. P.</given-names>
            <surname>Chau. Aurigo</surname>
          </string-name>
          :
          <article-title>An interactive tour planner for personalized itineraries</article-title>
          .
          <source>In Proc. of IUI'15</source>
          , pages
          <fpage>275</fpage>
          -
          <lpage>285</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>