<!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>A Framework for Comparing Interactive Route Planning Apps in Tourism</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sergejs Pugacs</string-name>
          <email>Sergejs.Pugacs@stud-inf.unibz.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sven Helmer</string-name>
          <email>shelmer@inf.unibz.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Markus Zanker</string-name>
          <email>mzanker@unibz.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Free University of Bozen-Bolzano Bolzano</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <fpage>18</fpage>
      <lpage>25</lpage>
      <abstract>
        <p>Route planning applications are digital companions of many travelers, enabling them to experience di erent locations in a self-determined way. This work surveys the variety of commercial applications and research prototypes for itinerary planning with the goal of evaluating the interactivity aspect of these tools. For this purpose a framework to classify the interaction mechanisms and usage features of route planning applications has been developed that di erentiates between the point-ofinterest and the aggregate tour layer. This proposed framework is applied to classify existing apps and points to opportunities for further research.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Instead of relying on printed guide books and preplanned tours, more and more
tourists are switching to applications to help them plan trips in a more
selfdetermined and interactive way [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. While there is a substantial body of work on
the e cient route generation part of tourist trip planning [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], especially in the
area of orienteering, we believe that the usability and interactivity of a system
is a more crucial aspect. Interactivity plays a key role when it comes to user
acceptance: users who have the feeling that they actively contributed to creating
the trips, rather than just following the instructions of the application, will feel
a sense of achievement and keep using this system.
      </p>
      <p>Our goal is to compare di erent route planning applications in terms of
their level of interactivity. In order to be able to do so, we develop a comparison
framework custom-tailored to the speci c aspects of route planning. In particular
we make the following contributions:
{ we investigate a set of guidelines developed for the usability of recommender
systems in general and use it as a basis for our framework to evaluate the
interactivity of route planning systems;
{ we apply our framework to state-of-the-art route planning applications,
evaluating the support of interactivity according to our de ned framework.</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        In their survey Vansteenwegen and Sou riau [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] provide a detailed overview of
the functionalities and features that users expect from a trip planning app. They
range from personal interest estimation, automatic route generation, mandatory
POIs, dynamic recalculation, multiple day decision support, opening hours,
budget limitations, maximal type constraints, mandatory type constraints, weather
dependency, scenic routes, hotel selection, public transportation, all the way to
group pro les. While this is a comprehensive list, there is no clear description of
how these preferences are actually elicited from users.
      </p>
      <p>By looking at the sheer number of the potential constraints listed above,
it becomes clear that users could quickly be overwhelmed by having to supply
all their preferences regarding these aspects to an app. The e ort required for
expressing preferences has to be balanced with the quality of a tour
recommendation: it may be more e ective to ask fewer but more speci c questions in order
to provide a better overall user experience. On top of this, a user should be able
to state their preferences as intuitively as possible.</p>
      <p>
        Pu et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] have investigated decision support studies in recommender
systems in the context of usability and interactivity. They came up with a set
of eleven guidelines or best practices for designing the preference elicitation
process in recommender systems. Pu et al. divided the guidelines into three
categories: initial preference elicitation, preference revision, and presentation of
results which can in turn be assessed based on accuracy, con dence, and e ort
(ACE). However, the guidelines refer to recommender systems in general and
lack some speci c aspects of trip planners that represent composite
recommendations. Thus, the quality of a tour recommendation has to be judged on two
distinct levels. On the one hand, we want to make sure that each individual
POI (i.e. on the item level) clearly ts a user's preference. On the other hand,
there are aspects relating to the overall composition of a tour. Even if a tour
contains only high-quality POIs, a user could still be unhappy, because the POIs
are ordered in a suboptimal way or might not represent a good balance, leading
to long traveling times or sensory overload.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Framework</title>
      <p>
        Our goal is to adapt the guidelines in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] to interactive tour planning by building a
framework for comparing the user interaction of di erent trip planning systems.
In a rst step, we de ne the two-level distinction into tour-related and
POIrelated preferences in more detail. On the tour level, we have criteria such as the
total time and money spent on a trip and the preferred modes of transportation.
On the POI level, a user might want to specify mandatory POIs or veto certain
POIs because they have already visited them or dislike certain features (e.g. long
waiting times). Some preferences may even be found on both levels: we have time
constraints for the overall tour, but there may also be temporal restrictions for
visiting individual POIs.
      </p>
      <p>
        We focus on the most important functionalities identi ed by Vansteenwegen
and Sou riau [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], disregarding advanced criteria, such as weather conditions,
hotel selection, and group pro les for the moment. Table 1 summarizes the
preferences we investigate and maps them to both levels (POIs and composite tours).
      </p>
      <p>
        Taking the guidelines by Pu et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] as a starting point, we de ne seven
criteria for preference elicitation in interactive tour planning, which are discussed
in the following.
3.1
      </p>
      <sec id="sec-3-1">
        <title>C1 { Flexible Expression of Preferences</title>
        <p>
          The rst three criteria in the guidelines by Pu et al. [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] are on avoiding very rigid
schemes for preference elicitation, e.g. that a user has to enter all preferences
in a strict order before getting any feedback. A user should be allowed to enter
preferences on any attribute they choose and in any order. Di erent users also
have di erent levels of expertise and uency, so an incremental process adapted
to their knowledge and experience would be appropriate. For trip planning we
therefore have to consider the following.
        </p>
        <p>{ POI-Level Preferences: mandatory POIs and category preferences can be
incrementally elicited instead of requiring all of them up-front.
{ Tour-Level Preferences: up-front the system does not require any
tourrelated preferences apart from the destination itself.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>C2 { Example-Based Preference Elicitation</title>
        <p>The next criterion is about using examples during preference elicitation. This
helps novice users to gain uency in expressing preferences or stimulates users
who are still uncertain about them.</p>
        <p>{ POI-Level Preferences: the system should suggest potential POIs to
include in the tour.
{ Tour-Level Preferences: the system should show several examples of
prebuilt tours.</p>
      </sec>
      <sec id="sec-3-3">
        <title>C3 { Preference Lookahead</title>
        <p>
          The criterion C3 is about going beyond the current state of expressed
preferences and proposes to users possible additional preferences that would extend a
tour. This can also be mapped to one criterion in the guidelines by [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ], allowing
suggestions to the user that may not be optimal yet, but will very likely become
so when adding more preferences.
        </p>
        <p>{ POI-Level Preferences: consider showing the user POIs from categories
the user did not consider to evaluate.
{ Tour-Level Preferences: suggest a sequence of POIs that represents a
partial tour, to which a user could add more POIs to complete it.
3.4</p>
      </sec>
      <sec id="sec-3-4">
        <title>C4 { Con ict resolution</title>
        <p>If the preferences of a user are contradictory, it may not be possible to come up
with a recommendation that satis es all the constraints. In this case the system
should clearly explain how the con icts can be resolved and what compromises
would be entailed.</p>
        <p>{ POI-Level Preferences: when displaying/recommending a POI show how
this POI matches and/or violates speci c constraints.
{ Tour-Level Preferences: in case the user has expressed preferences for an
infeasible tour, still give him a tour suggestion with an explanation how this
suggestion violates their preferences.
3.5</p>
      </sec>
      <sec id="sec-3-5">
        <title>C5 { Trade-o</title>
      </sec>
      <sec id="sec-3-6">
        <title>Transparency</title>
        <p>In case of con icting preferences the system needs to be transparent about them,
for instance, clearly explain a trade-o between quality and costs to the user.
{ POI-Level Preferences: show budget, quality trade-o s between di erent</p>
        <p>POIs.
{ Tour-Level Preferences: show how di erent tours share the same POIs
and which POIs are di erent between them. Show di erences for
transportation, budget, and categories.
3.6</p>
      </sec>
      <sec id="sec-3-7">
        <title>C6 { Result Presentation</title>
        <p>A user should not be overwhelmed by the amount of information displayed on a
single page (this is especially true for small hand-held devices) and items should
be displayed and ranked in a natural order.</p>
        <p>{ POI-Level Preferences: for mobile displays show only a few individual</p>
        <p>POIs, but for desktop clients show a large ranked list of POIs.
{ Tour-Level Preferences: for mobile displays show only one tour at a time
as a recommendation, but for desktop clients show several tour
recommendations at the same time.</p>
      </sec>
      <sec id="sec-3-8">
        <title>C7 { Explanations</title>
        <p>
          The nal criterion is about providing information on how the system derived a
result [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
        </p>
        <p>{ POI-Level Preferences: explain how the POIs match preferences. Show</p>
        <p>POI scores and highlight mandatory POIs.</p>
        <p>{ Tour-Level Preferences: explain how the tour matches preferences.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Evaluation</title>
      <p>Based on our conceptual framework to classify the interactivity of tour planning
systems we assessed existing systems in order to identify opportunities for future
research and development. To be objective in our existing system review process
we formulated a search query (see Listing 1.1) that we evaluated over the Scopus
database 1. We reviewed the rst 200 highest cited papers for inclusion in our
work. The inclusion criteria were the following: 1) the paper should describe an
itinerary planning system; 2) the paper should have a description of the user
interface of this system.</p>
      <p>Listing 1.1. Scopus query string
( TITLE ABS KEY(
( i t i n e r a r i e s OR r o u t e s OR t o u r s )
AND ( p e r s o n a l i s e d OR r e c o m m e n d a t i o n s</p>
      <p>OR p l a n n i n g )
AND ( t o u r i s m OR t o u r i s t OR t r a v e l ) ) )
AND ( LIMIT TO ( SUBJAREA, "COMP " )</p>
      <p>OR LIMIT TO ( SUBJAREA, " DECI " )</p>
      <p>
        OR LIMIT TO ( SUBJAREA, " BUSI " )
Only 6 papers were selected by these criteria. In addition we included one more
paper [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] that was not in the Scopus database, that we feel is essential in the
eld of interactive tour planning.
      </p>
      <p>In addition to the academic systems we also wanted to include commercial
systems in our evaluation. To select the commercial systems we used a single
Google search with the query string tourism itinerary planner and
considering the rst 20 results. We included those results that pointed to a system
which allowed a user to automatically generate a travel itinerary. Five such
systems were selected by us. In total 12 systems were included in our evaluation.</p>
      <p>The results of our evaluation are presented in Table 2 where we indicate for
each system the support of the di erent categories of interactive trip planning
according to our framework. The rows of the table correspond to the evaluated
systems and the columns to the categories of our framework. For every criterion
we evaluate systems on both the POI level (P) and tour level (T).
1 https://www.scopus.com
After reviewing these 12 systems we conclude that a majority of them follows
an identical planning strategy. First, a user is faced with the initial query where
they must specify the destination city/region/country and optionally indicate
the travel dates or travel category preferences. They are then presented with an
itinerary plan that can be modi ed manually. Modi cations can happen in two
ways: users remove a POI from the itinerary or insert an additional new one.
When inserting a new POIs the user is supported with a large list of POIs with
pictures and textual descriptions as well as potential category classi cations.</p>
      <p>Two systems out of 12 follow a di erent planning strategy, namely
Routeperfect and CT-Planner. In these systems users can interactively indicate their
preference degrees for di erent categories and the system would automatically
recompute the tour based on these preferences. For an example see Figure 1.</p>
      <p>This alternative approach allows us to achieve two things: it provides an
interactive environment where the user can explore many possible itineraries
with little e ort. It provides an explanation of the properties of the tour, since
the tour is automatically generated based on preferences indicated by the user</p>
      <p>Another alternative is o ered by Inspirock's automatic tour rescheduling.
When a user tries to add a POI causing a con ict, the system promptly suggests
to reschedule the tour.</p>
      <p>For those criteria that are barely or not supported at all, we sketch exemplary
user stories in the following.</p>
      <p>Criterion C3 { Preference Lookahead: we think it should be possible for a
system to recommend whole sub-tours for inclusion into a tour. These sub-tours
could be created either by domain experts or by mining previous interaction
histories.</p>
      <p>Criterion C5 { Trade-o Transparency: on the POI level this would mean not
only displaying POIs, but also pointing out the implications of adding a POI to a
tour, e.g., longer visiting times and higher attractiveness. On the tour level, this
would involve presenting a user with several alternative routes and highlighting
their qualitative and quantitative di erences.</p>
      <p>Criterion C6 { Result Presentation: we hypothesize that systems could use
feedback approaches enabling a user to critique speci c criteria such as the length
of a tour, the means of transportation, and the number of breaks.</p>
      <p>Category C7 { Explanations: we believe this criterion to be one of the most
important aspects of the interaction between users and the system. It is much
easier for a user to compare two options if they are explained in terms of user
preferences.
6</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusions</title>
      <p>In this paper we de ned a framework for evaluating di erent interactivity aspects
of tour planning systems that is based on existing guidelines for recommender
systems in general. However, given the dual nature of preferences in the trip
planning scenarios, we need to distinguish between the POI level and the
composite tour level. The contribution of this research lies not only in the framework
but also in its exemplary evaluation by classifying existing tour planning systems
in order to demonstrate potential opportunities for future work.</p>
      <p>In particular we identi ed trade-o analysis and tour explanations as
unexplored areas and their potential in improving the user experience in the area of
tour planning.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>J. L.</given-names>
            <surname>Ambite</surname>
          </string-name>
          , G. Barish,
          <string-name>
            <given-names>C. A.</given-names>
            <surname>Knoblock</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Muslea</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Oh</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Minton</surname>
          </string-name>
          .
          <article-title>Getting from here to there: Interactive planning and agent execution for optimizing travel</article-title>
          .
          <source>In Proceedings of the 14th Conference on Innovative Applications of Articial Intelligence - Volume 1, IAAI'02</source>
          , pages
          <fpage>862</fpage>
          {
          <fpage>869</fpage>
          . AAAI Press,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>L.</given-names>
            <surname>Ardissono</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Goy</surname>
          </string-name>
          , G. Petrone,
          <string-name>
            <given-names>M.</given-names>
            <surname>Segnan</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Torasso</surname>
          </string-name>
          . Intrigue:
          <article-title>Personalized recommendation of tourist attractions for desktop and hand held devices</article-title>
          .
          <source>Applied Arti cial Intelligence</source>
          ,
          <volume>17</volume>
          (
          <issue>8-9</issue>
          ):
          <volume>687</volume>
          {
          <fpage>714</fpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>G.</given-names>
            <surname>Friedrich</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Zanker</surname>
          </string-name>
          .
          <article-title>A taxonomy for generating explanations in recommender systems</article-title>
          .
          <source>AI Magazine</source>
          ,
          <volume>3</volume>
          (
          <issue>3</issue>
          ):
          <volume>90</volume>
          {
          <fpage>98</fpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>A.</given-names>
            <surname>Gunawan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. C.</given-names>
            <surname>Lau</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Vansteenwegen</surname>
          </string-name>
          .
          <article-title>Orienteering problem: A survey of recent variants, solution approaches and applications</article-title>
          .
          <source>European Journal of Operational Research</source>
          ,
          <volume>255</volume>
          (
          <issue>2</issue>
          ):
          <volume>315</volume>
          {
          <fpage>332</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>M.</given-names>
            <surname>Houda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Khemaja</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Oliveira</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Abed</surname>
          </string-name>
          .
          <article-title>A public transportation ontology to support user travel planning</article-title>
          .
          <source>In 2010 Fourth International Conference on Research Challenges in Information Science (RCIS)</source>
          , pages
          <fpage>127</fpage>
          {
          <fpage>136</fpage>
          , May
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>K. F.</given-names>
            <surname>Hyde</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>Lawson</surname>
          </string-name>
          .
          <article-title>The nature of independent travel</article-title>
          .
          <source>Journal of Travel Research</source>
          ,
          <volume>42</volume>
          (
          <issue>1</issue>
          ):
          <volume>13</volume>
          {
          <fpage>23</fpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>Y.</given-names>
            <surname>Kurata</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Hara.</surname>
          </string-name>
          CT-Planner4:
          <article-title>Toward a More User-Friendly Interactive Day-Tour Planner</article-title>
          , pages
          <volume>73</volume>
          {
          <fpage>86</fpage>
          . Springer International Publishing, Cham,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>C.-S. Lee</surname>
            ,
            <given-names>Y.-C.</given-names>
          </string-name>
          <string-name>
            <surname>Chang</surname>
            , and
            <given-names>M.-H.</given-names>
          </string-name>
          <string-name>
            <surname>Wang</surname>
          </string-name>
          .
          <article-title>Ontological recommendation multiagent for tainan city travel</article-title>
          .
          <source>Expert Systems with Applications</source>
          ,
          <volume>36</volume>
          (
          <issue>3</issue>
          , Part 2):
          <volume>6740</volume>
          {
          <fpage>6753</fpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>P.</given-names>
            <surname>Pu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Faltings</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Viappiani</surname>
          </string-name>
          .
          <source>Usability Guidelines for Product Recommenders Based on Example Critiquing Research</source>
          , pages
          <volume>511</volume>
          {
          <fpage>545</fpage>
          .
          <string-name>
            <surname>Springer</surname>
            <given-names>US</given-names>
          </string-name>
          , Boston, MA,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. B. Rodr guez, J.
          <string-name>
            <surname>Molina</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Perez</surname>
            , and
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Caballero</surname>
          </string-name>
          .
          <article-title>Interactive design of personalised tourism routes</article-title>
          .
          <source>Tourism Management</source>
          ,
          <volume>33</volume>
          (
          <issue>4</issue>
          ):
          <volume>926</volume>
          {
          <fpage>940</fpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>P.</given-names>
            <surname>Vansteenwegen</surname>
          </string-name>
          and
          <string-name>
            <surname>W.</surname>
          </string-name>
          <article-title>Sou riau. Trip planning functionalities: State of the art and future</article-title>
          .
          <source>Information Technology &amp; Tourism</source>
          ,
          <volume>12</volume>
          (
          <issue>4</issue>
          ):
          <volume>305</volume>
          {
          <fpage>315</fpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>P.</given-names>
            <surname>Vansteenwegen</surname>
          </string-name>
          , W. Sou riau,
          <string-name>
            <given-names>G. V.</given-names>
            <surname>Berghe</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D. V.</given-names>
            <surname>Oudheusden</surname>
          </string-name>
          .
          <article-title>The city trip planner: An expert system for tourists</article-title>
          .
          <source>Expert Systems with Applications</source>
          ,
          <volume>38</volume>
          (
          <issue>6</issue>
          ):
          <volume>6540</volume>
          {
          <fpage>6546</fpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>