<!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>Optimization of Digital Elevation Models for Routing</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Doris Silbernagl</string-name>
          <email>doris.silbernagl@uibk.ac.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Martin Malfertheiner</string-name>
          <email>martin.malfertheiner@student.uibk.ac.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nikolaus Krismer</string-name>
          <email>nikolaus.krismer@uibk.ac.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Günther Specht</string-name>
          <email>guenther.specht@uibk.ac.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer</institution>
          ,
          <addr-line>Science</addr-line>
          ,
          <institution>University of</institution>
          ,
          <addr-line>Innsbruck</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2016</year>
      </pub-date>
      <fpage>103</fpage>
      <lpage>108</lpage>
      <abstract>
        <p>Routing is a common task when using digital maps, but most engines offer only travel routes for automobiles. However, a more interesting aspect in this topic arises when being a cyclist. For this target audience especially elevation information is relevant. Such data is available from different sources, but is not perfectly usable for cycling routing. Those digital elevation models may include voids and outliers that falsify the elevation profile. Thus, a pre-processing step is necessary before using them. Therefore noise reduction steps and the Mean and Kalman filters are applied and evaluated in this work. They successfully eliminate erroneous and noisy information and smooth the elevation profiles. This enables a elevation aware routing engine to find and calculate more suitable paths for a cyclist, thereby allowing a more accurate route planning.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Categories and Subject Descriptors</title>
      <p>F.2.0 [ANALYSIS OF ALGORITHMS AND
PROBLEM COMPLEXITY]: General; H.0 [Information
Systems]: General; H.2.8 [DATABASE MANAGEMENT]:
Database Applications—Spatial databases and GIS</p>
    </sec>
    <sec id="sec-2">
      <title>1. INTRODUCTION</title>
      <p>
        A common use-case in today’s society is traveling and
exploring new locations. To fulfill this tasks easily, many online
services exist that propose best paths to the desired
destination. For motorists these suggestions deliver mostly very
accurate travel time estimations. In contrast, a cyclist never
could rely on the outcome of today’s standard online routers
as they ignore some essential factors. One of these is
elevation information. While cars mostly have enough power to
drive close to the speed limit regardless of the slope of the
street, cyclists come to their limits when going uphill. Many
of the currently available online routers do not consider the
altitude profile at all and thus suggest non-realistic values.
For example, for a 10 km long path with average incline
slope of 8 % a standard online router estimates a travel time of
approximately 30 minutes. Taking the elevation information
into account, GraphHopper [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], an elevation aware routing
engine for cyclists, estimates for the same path
approximately two hours of cycling time. So it becomes obvious that
elevation plays an important role for routing engines tailored
to cyclists. Existing bicycle routers and other related work
and research in this area are therefore shortly presented in
Section 2.
      </p>
      <p>The data used for elevation aware routing is available via
digital elevation models. For usage within the final routing
engine, the datasets should be prepared first. This
preparation task includes a previous analysis of the elevation data
and will be presented in Section 3. Different versions of the
digital elevation model will be investigated to find the best
one that meets the required properties. After the evaluation
of the datasets a possible improvement of those is examined
in Section 4. Presumably, the models need to be cleaned
for proper usage as they may include noisy altitude values,
possibly causing unrealistic steep slopes. To get rid of these
noises and outliers it is necessary to apply smoothing
algorithms before the elevation profiles are projected on an
edge of the routing graph. Hence, in this paper, the Mean
and Kalman filters are applied to investigate the possible
improvement of elevation profiles.</p>
      <p>
        These processing steps allow to optimize the elevation
profiles for cycling purposes. However, additional information
about a track itself, like type of road or surface, can lead
to even better route calculations. For this and as a routing
engine needs maps and street information for path finding,
the OpenStreetMap (OSM) [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] project is used as a data
source. OSM is an open source project that has an active
community and in many areas a high level of detail, as well
as good data quality [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Moreover, the dataset is
frequently updated by many contributors and institutions.
Hence, OSM is a highly suitable information source for route
finding.
Especially when it comes to routing for cyclists, OSM
provides the necessary additional data about a path which is
stored via tags. Tags can deliver track information like high
and low traffic roads, paved and unpaved tracks, paths and
ways and many more. As all these different conditions
matter, as well as the type of bicycle or the physiology of the
cyclist himself, a user profile aware routing system is sensible.
This system should include as much reasonable information
as possible to propose appropriate paths for each individual
and estimate very accurate travel times. It even may learn
from a users cycling history and thus becomes capable for
profile aware routing. It is described in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. In the end, the
resulting routing engine can deal with (all kinds of) cyclists,
makes use of user profiles and especially includes smooth and
homogeneous elevation profiles, unlike other routers which
only have specific graphs for motorists.
      </p>
    </sec>
    <sec id="sec-3">
      <title>RELATED WORK</title>
      <p>
        For routing many commercial and open source systems
exist. When it comes to route engines for bicycles, the list
of available systems is shortened drastically. Examples for
regional bicycle routers are Cyclopath (USA) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] and
cycle.travel (UK) [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Other bicycle maps exist, e.g. bikemap
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], biketastic [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ] or the regional ”Radlkarte Salzburg”[
        <xref ref-type="bibr" rid="ref17">17</xref>
        ].
However, these are no routing engines that allow an
individual search for paths from point A to B, but present
predefined, static routes that are entered by users or include
official routes (thematic routes with POIs) by touristic
centers. Some tools for route creation or planing can also be
found, especially of the producers of GPS trackers, like
Garmin with its bikeroutetoaster [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], but do not make use of
routing algorithms, too. Opencyclemap [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] is also a map
tailored to cyclists and displays available routes in almost
any region of the world, however without the possibility of
explicit route finding and elevation data for the paths.
Another bicycle router that even regards elevation data is
cycleroute [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. However, this tool is solely build on Google Maps
and its API and is currently out of service. Moreover, no
documentation could be found that describes the functioning
of the tool.
      </p>
      <p>
        In numerous of the open source products, also in the ones
listed above, OpenStreetMap is often deployed as a base map
for routing. Well-known routers explicitly using OSM data
are OSRM [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ], MapQuest [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ], GraphHopper[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], BRouter
[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], just to name a few. These routing engines share a vast
amount of similar characteristics, but most of them have
their focus on car routing and less on bicycle routing[
        <xref ref-type="bibr" rid="ref22">22</xref>
        ].
Limiting these representatives to elevation aware routing,
the only two left are GraphHopper and BRouter[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
However, the elevation information needed by these routers often
lacks in OSM. Therefore, other sources become relevant.
      </p>
      <p>
        Digital elevation models are such an alternative source for
elevation information and thus form important datasets for
many different research areas. Regarding the quality of these
datasets, Rexer et al. [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ] compared the accuracy of the
global freely available models, such as Advanced Spaceborne
Thermal Emission Reflectometer DEM (ASTER GDEM2)
and the two DEMs based on the Shuttle Radar
Topography Mission (SRTM). The investigation shows that the two
SRTM datasets have a higher accuracy and thus will be
discussed in the upcoming sections.
3.
      </p>
    </sec>
    <sec id="sec-4">
      <title>DIGITAL ELEVATION MODELS</title>
      <p>
        In order to calculate the optimum path for a cyclist, many
aspects have to be taken into account. Next to criteria such
as way type, way surface, etc., elevation data becomes the
most significant one. The first elements can be retrieved from
OSM, presuming these tags are filled with values.
Elevation information is basically also available in OSM through a
tag that can be set on all types of OSM elements. However,
currently it is rarely used: only 2.6 million elements out of
possible 3.6 billion elements (of those only 1.3 billion are
tagged) include this tag. According to the taginfo website [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ],
a statistical site that analyzes OSM tags, this is only 0.07%
usage in total (statistic from 24/03/2016). So it is obvious
that although OSM offers this information, it is practically
not reliable that it is available for every region. So, other
data sources that may deliver a more accurate and global
dataset become relevant, such as SRTM. Therefore, in this
paper some digital elevation models (DEM) are presented
and examined.
      </p>
      <p>
        There exist many accurate digital elevation models with
very low error rates, but they are usually only available for
small areas, e.g. DEM data of South Tyrol. Other globally
available solutions like the dataset of the WorldDEM (TM)
of the Airbus defense and space organization have a high
accuracy, but are only available for a fee1. Open source projects
like GraphHopper and BRouter therefore use the data from
Shuttle Radar Topography Mission (SRTM) or the CGIAR
[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] datasets to feed their graphs with elevation information.
These datasets are presented in the following sections.
3.1
      </p>
    </sec>
    <sec id="sec-5">
      <title>SRTM</title>
      <p>The Shuttle Radar Topography Mission (SRTM)
mission was a joint operation between the NASA, the National
Geospatial-Intelligence Agency (NGA) and the German and
Italian Space Agencies. Approximately 80 % of the worlds
land surface was scanned during the first flight in year 2000
and at least 94.59% twice from different angles. After
processing the radar information, the organizations exposed the
first near global-elevation dataset. This first version,
however, is quite noisy and has missing data. The reasons for this
can be heavy shadows and water reflections. So refinement
work was initiated which reduced spikes and wells, leveled
water and defined coastlines.</p>
      <p>Originally the dataset SRTM1 contained one arc-sec
(approx. 30 meters) times one arc-sec resolution data only for
the US. For the rest of the world SRTM3 exists which has
three arc-sec times three arc-sec (approx. 90 meters)
resolution. The resolutions are indicated in the number extension
of the SRTM name (1 and 3). However, the SRTM dataset
still has many voids, making it not well usable for routing in
any area. This issue is addressed in the third version of the
SRTM dataset. The NGA filled the voids using interpolation
algorithms and thus produced the SRTM version 3. Again,
the resolution of this void filled dataset is currently globally
available in three arc-seconds and called SRTM3 v3. Only
for some regions, including the US, the 30 meters dataset
is released, called SRTM1 v3, but will be available for more
regions in the future.</p>
      <p>But SRTM is not the only nearly globally available DEM
and therefore the following section will introduce the CGIAR
dataset.
1http://www.geo-airbusds.com/worlddem/, 29.07.2015</p>
      <p>
        The Consultative Group for International Agriculture
Research CGIAR provides a void-filled dataset of the SRTM3
v2 for 90 meters resolution quality. The resolution stayed
the same as the SRTM3s one: three arc-sec times three
arcsec. However, CGIAR additionally used external resources
to fill the voids and also transformed the data into the
widely adapted filetype GeoTiff [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and simple ASCII, which is
supported by many GIS tools out of the box. According to
Goronkhovich et.al. [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] the absolute vertical accuracy of the
newly compiled dataset is four times higher in the
investigated areas than the value of 16m presented in the original
SRTM requirement specification. This is because CGIAR
takes slope and aspect values into account, which
considerably improved the accuracy of the CGIAR DEM product for
terrain with slope values greater than 10 degrees.
      </p>
      <p>Although this DEM is already quite good, more detailed
ones are available for specific regions. Thus, in the following
paragraph, the South Tyrol DEM is presented.
3.3</p>
    </sec>
    <sec id="sec-6">
      <title>South Tyrol DEM</title>
      <p>
        In contrast to the datasets presented before, a regional
elevation model is more precise. Thanks to the government of
South Tyrol (Autonome Provinz Bozen – Amt fu¨r
u¨bero¨rtliche Raumordnung [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ]) very accurate elevation information
for the small province in the north of Italy can be accessed.
      </p>
      <p>The data was gained with the help of laser scanners and
covers the entire area of the province of South Tyrol. It has
a resolution of 2.5 meters times 2.5 meters and an absolute
vertical error of 40 cm below 2.000 MASL (Meters Above
Sea Level) and 55 cm above 2.000 MASL. The high
resolution and accuracy make this product suitable for the ground
truth source.</p>
      <p>Having discussed three DEMs, a short comparison should
allow an overview of the quality of those datasets. The
following section includes an evaluation of the models.</p>
    </sec>
    <sec id="sec-7">
      <title>DEM EVALUATION AND</title>
    </sec>
    <sec id="sec-8">
      <title>IMPROVEMENT</title>
      <p>Regarding routing for a cyclist it is more interesting to
evaluate how well the datasets perform when they are
mapped to the street network. This section will show an
evaluation based on the South Tyrol ground truth.</p>
      <p>
        The absolute vertical error of post-processed SRTMs
(voidfilled SRTM1 v3 and SRTM3 v2.1) and CGIAR with respect
to the South Tyrol as ground truth DEM is observed. The
experiment calculates the corresponding RMSE (Root Mean
Squared Error) for each nearly globally available dataset.
RMSE is a commonly used to measure the accuracy of
values in different models. In geo-information systems, RMSE
is “a measure of the difference between location that are
known and locations that have been interpolated or
digitized“[
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. This means, by comparing particular predicted
values to actual values, it is possible to match the function
curves of the models and thus the average deviation. The
higher the RMSE factor is, the worse is the adaption of the
model. Compared to the similar MEA (Mean Absolute
Error), the RMSE amplifies and punishes large errors and thus
is more applicable in the present case.
      </p>
      <p>For the evaluation, seven different tracks were recorded
with a GARMINTMOregon 550t GPS tracker during bicycle
trips. The tracks cover different environments such as valley,
plateau or mountain. Figure 1 is an example of a recorded
track in an alpine plateau (“Ritsch-Kompatsch“). The y-axis
shows the meters above sea level, the x-axis the distance
cycled in meters. Here the visual comparison of the available
DEMs to the recorded GPS track are of interest. Looking at
the regional SouthTyrol DEM (dark grey line with points),
it can be seen that its shape is quite similar to the one of
the GPS recorded elevation (black line on bottom). The
discrepancy of about 20 meters from the GPS record to the
other profiles is due to the barometric altimeter in the
device. Comparing the GPS record to the globally available
DEMs, it can be clearly stated that SRTM1 v3 (blue line
with rectangles) matches best with the GPS track. CGIAR
(light grey line with triangles), however, performs worst for
this specific track.</p>
      <p>Table 1 strengthens the previously made observations.
With the South Tyrol DEM being the ground truth, the
SRTM1 v3 DEM outperforms the other two datasets on each
track. The RMSE for each evaluated track is the lowest for
SRTM1 v3. The differences in the RMSE for the ways in
one direction and backwards are due to the different point
records of the GPS device, thus influencing the whole
calculation. As SRTM1 v3 delivers the best result, this elevation
model is used to feed the routing graph with elevation
information. Although the results are already very promising,
Section 4.2 shows with which algorithms the quality of a
tracks elevation profile can be further improved.
The digital elevation models have already undergone
several post-processing steps, but peaks and troughs are still
present in the elevation profile. Therefore, in the remaining
part of this section algorithms for DEM improvement are
suggested that should smooth the profile.
4.1</p>
    </sec>
    <sec id="sec-9">
      <title>DEM noise reduction</title>
      <p>The DEM models are stored as rasterized data where each
geographic region can be found in a tile of the raster. If the
system extracts the elevation value for a specific geographic
point, it would normally consider only a single tile. Due to
the noisy elevation models it might withdraw a wrong value,
that messes up the elevation profile. A simple approach to
solve this problem is to not only use the value from a single
tile, but also from the enclosing neighbors. Thus, the first
goal is to remove noise by considering surrounding tiles on
elevation extraction and secondly, to smooth the elevation
values once they have been mapped on the way.</p>
      <p>GraphHopper has already an implementation of the mean
method in place. The algorithm takes the four adjacent tiles
and averages the five extracted values. This approach has
been extended to support also the neighboring eight tiles
and the possibility to define the behavior of the filter with a
kernel. The kernel is used to set the weight on each element.
This makes it simple to test different combinations.</p>
      <p>The second approach was to use a median filter on the
eight surrounding tiles and the center tile.</p>
      <p>These simple noise reduction algorithms were not able to
improve the elevation profile of a way, because the
datasets are already averaged. Therefore, another approach will
be evaluated, which smooths the elevation profile after the
extraction from the original DEM.
4.2</p>
    </sec>
    <sec id="sec-10">
      <title>Elevation profile smoothing</title>
      <p>
        Slope is one of the main criteria for cyclists when they
choose their route [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Thus, a router has to calculate the
slope of each part of the path. As the DEM data have hills
and valleys and are quite noisy, the elevation profile is often
not very accurate and therefore needs to be smoothed. For
this operation, two approaches seem to be appropriate: the
Mean and the Kalman filter.
4.2.1
      </p>
      <sec id="sec-10-1">
        <title>Mean filter</title>
        <p>The arithmetic Mean filter is a well known method to
smooth datasets. In signal theory it is also referenced as low
pass filter, because it removes high frequencies.</p>
        <p>In this particular context the filter is used on a list of
points with elevation information. In its simplest form it
takes the actual value at position t, adds the value at position
t-1 and t+1 and divides by three. The problem of this
approach is that it ignores the distance between two points.
The frequency of points within a certain distance differs
depending on the shape of the street. A straight line needs
only few points to be defined, but a curvy street has
plenty of points. If the algorithm considers only a fixed number
of adjacent points, it might lookup only in the same tile or
considers points that should have no influence anymore,
because they are too far away. This problem can be solved by
selecting only those points, which are within a certain
radius. The final version of the implemented Mean filter takes a
number that defines the radius in meters and averages over
all reachable points.</p>
        <p>Table 2 gives a detailed overview of the evaluated tracks
where the Mean filter has been applied with 50, 100 and 200
as distance parameter. This parameter defines the
smoothness of the curve: a higher distance value causes a higher
cutoff rate. The last row in Table 2 includes the average
RMSE and it can be seen that the mean filtered elevation
profile with distance equal to 50 meters performs best. The
difference to the original dataset although is only about a
maximum of 30 cm, which is a small improvement.</p>
        <p>The smoothing algorithm flattened altitude peaks and
lows. This influences the calculation of the slope for each
edge in the route. For example, the original dataset has at
one point of the route a very steep incline: 10m / 40m * 100
% = 25 % incline. The Mean filter 50m reduced this value
to 6m / 40m * 100 % = 15% incline.</p>
        <p>The observations show that the Mean filter is a great tool
to smooth the elevation profile of a track, but the
improvement of only 30 cm in absolute vertical accuracy is only
marginal. Another well known smoothing algorithm might
perform even better and is already frequently used in GPS
signal smoothing: the Kalman filter.
4.2.2</p>
      </sec>
      <sec id="sec-10-2">
        <title>Kalman filter</title>
        <p>
          Knowing that the DEM data of SRTM and CGIAR
have noisy data, it becomes necessary to apply a filter that is
useful to eliminate such noise. This is why the Kalman filter
[
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] is chosen as a second approach in this topic. The filter
can be used in any system where uncertain information is
present and an educated guess is needed to estimate what
happens next. Having interpolated data and outliers in the
elevation profiles the Kalman filter can help with the
prediction of the approximate location of uncertain points in the
profile.
        </p>
        <p>For routing purposes it is necessary to adjust the filter
to be influenced by the distance between each point of the
path. If two points are very distant then the filter should
trust the measurement more than the estimation, on the
other hand if two points are very close the filter should trust
the estimation more than the measurement. The Kalman
filter assumes that a cyclist drives in one direction, but the
algorithm should also consider that usually a street can be
cycled also from the opposite site. The best results have
been generated, when applying the filter for both directions
and then merging the two smoothed datasets by taking the
average. This fact can be observed in Table 2 for tracks that
were cycled in both directions.
Track
Brixen – Klausen
Klausen – Brixen
Konstantin – Seis</p>
        <p>Seis – Konstantin
Ritsch – Kompatsch</p>
        <p>Kastelruth – Seis
Seis – Kastelruth
Average RSME</p>
        <p>Figure 2 shows how the Kalman filter removes peaks and
lows in the elevation profile (track “Ritsch-Kompatsch“).
The y-axis shows the meters above sea level, the x-axis the
distance cycled in meters. The ground truth data of the
South Tyrol DEM is represented with the black line with
squares. The GPS data is not visible in this figure. The
noisy SRTM1 v3 profile is the dark grey line with points. The
other lines are the applied Kalman filter with different
distances of 30, 60 and 100m. These profiles are very similar
and perform better that the SRTM1 v3. To get a closer
impression of the actual values of the filtered profiles, Table 2
includes the list of the RMSE results.</p>
        <p>From Table 2 it can be seen that the Mean filter performs
best with a distance value of 50. However, the improvement
is small and not equally suitable for different tracks. In
contrast, the Kalman filter delivers even better results for
almost all tracks with a fixed distance of 30. However, in total
there is not much difference between the Mean filtered, the
Kalman filtered and the original dataset. Nevertheless, the
major important aspect of filter application is to
eliminate outliers and reduce or even remove high peaks and lows.
By this, the profiles are smoothed, allowing a more realistic
routing for cyclists.</p>
        <p>In this section it has been shown how well smoothing
algorithms perform on noisy elevation data. Without these
algorithms it would not make any sense to extract the
slope between each location pair, because the calculated slopes
would have unrealistic inclines as well as declines. With the
help of the filters it is now possible to have access to a
more accurate shape of a street, which influences not only the
travel time, but also the route selection and thus is relevant
for profile based routing.
5.</p>
      </sec>
    </sec>
    <sec id="sec-11">
      <title>CONCLUSIONS</title>
      <p>Online routers become more and more important for
people when planning their trips. For motorists, these route
engines deliver good results, but for cyclists they often are
quite useless. Having specific requirements for route finding,
like different bicycles, physical condition or specific
geographical location, more aspects have to be regarded by the
routing algorithm. The most critical factor for a cyclist is
the incline and decline of a path. For this, it is necessary
to include elevation information when routing, as well as
additional information about the ways. In this work,
OpenStreetMap is the source for data about ways and geography.
Coming to elevation information, the two digital elevation
models SRTM and CGIAR are presented, as well as the
regional South-Tyrolean DEM. These DEMs are compared,
coming to the conclusion that data voids and interpolated
datasets constitute a problem when finding routes for
cyclists.</p>
      <p>Therefore, methods for DEM improvement were
discussed, like noise reduction and the application of smoothing
algorithms. In the noise reduction approach the idea is to
include more neighboring tiles in order to get a more
correct interpolation value for the void in the elevation profile.
Since this method did not achieve the desired improvement,
different filter algorithms were applied. The Mean and the
Kalman filter are two well-known instruments for noise
removal in data samples. Especially with the help of the
Kalman filter it is possible to reduce the mean average error
rate and to flatten the noisy peeks and lows. Taking
different distance values as a constant between two way points,
the outcome of the algorithms varied, depending also on the
basis of the chosen test tracks. These tracks were selected in
the test region of South Tyrol as the DEM of this region is
of good quality. A comparison of the applied filters to this
original ground truth showed that out of all investigated
distances applied in the experiment the Mean filter operates
best with a distance factor of 50m and the Kalman filter
with a distance of 30m. The filtered ways have very smooth
slopes and thus, these results are taken into account for the
prototypical implementation of the profile aware router.</p>
      <p>Having information about the track type and its
smoothed elevation profile, as well as the input of preferences of
a user profile, which is very flexible and includes many
critical factors for bicycle optimized routing, enable the router
to calculate accurate travel times, weigh the possible paths
according to the profile and thus in the end present the best
options for the cyclist.</p>
      <p>Future work in this area can be seen in a re-evaluation
using the recently available and updated SRTM1 data set
that was released in high resolution of one arc-second for
Europe in April 2015.
6.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>C.</given-names>
            <surname>Barron</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Neis</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Zipf</surname>
          </string-name>
          .
          <article-title>A comprehensive framework for intrinsic openstreetmap quality analysis</article-title>
          .
          <source>Transactions in GIS</source>
          ,
          <volume>18</volume>
          (
          <issue>6</issue>
          ):
          <fpage>877</fpage>
          -
          <lpage>895</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Bikemap</surname>
          </string-name>
          .
          <article-title>Bikemap - your bike routes online</article-title>
          . http://www.bikemap.net/en, (
          <year>2016</year>
          ).
          <volume>22</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Bikeroutetoaster</surname>
          </string-name>
          .
          <article-title>Bike route toaster</article-title>
          . http://bikeroutetoaster.com, (
          <year>2016</year>
          ).
          <volume>22</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Brenschede</surname>
          </string-name>
          . Brouter. http://brouter.de/brouter/, (
          <year>2015</year>
          ).
          <volume>10</volume>
          /02/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J.</given-names>
            <surname>Broach</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dill</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Gliebe</surname>
          </string-name>
          .
          <article-title>Where do cyclists ride? A route choice model developed with revealed preference GPS data</article-title>
          .
          <source>Transportation Research Part A: Policy and Practice</source>
          ,
          <volume>46</volume>
          (
          <issue>10</issue>
          ):
          <fpage>1730</fpage>
          -
          <lpage>1740</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>CGIAR</given-names>
            <surname>Consortium</surname>
          </string-name>
          .
          <article-title>CGIAR-CSI SRTM 90m DEM Digital Elevation Database</article-title>
          . http://srtm.csi.cgiar.org, (
          <year>2016</year>
          ).
          <volume>21</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <article-title>[7] cycleroute.org. Cycle route , plan and map your cycle route with elevation profile</article-title>
          . http://www.cycleroute.org, (
          <year>2016</year>
          ).
          <volume>22</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <article-title>[8] cycle.travel. cycle.travel - commuting, bike maps, cycle routes, touring</article-title>
          . http://cycle.travel, (
          <year>2016</year>
          ).
          <volume>22</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Cyclopath</surname>
          </string-name>
          . Cyclopath. http://cyclopath.org, (
          <year>2016</year>
          ).
          <volume>22</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>ESRI. RMS</surname>
          </string-name>
          error - GIS Dictionary. http://support.esri.com/en/knowledgebase/ GISDictionary/term/RMS%20error, (
          <year>2016</year>
          ).
          <volume>21</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <article-title>GeoTIFF</article-title>
          . GeoTIFF. http://trac.osgeo.org/geotiff/, 18/11/
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Gorokhovich</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Voustianiouk</surname>
          </string-name>
          .
          <article-title>Accuracy assessment of the processed SRTM-based elevation data by CGIAR using field data from USA and Thailand and its relation to the terrain characteristics</article-title>
          .
          <source>Remote Sensing of Environment</source>
          ,
          <volume>104</volume>
          :
          <fpage>409</fpage>
          -
          <lpage>415</lpage>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>GraphHopper</surname>
          </string-name>
          .
          <article-title>Graphhopper directions api with route optimization</article-title>
          . https://graphhopper.com/. 16/07/
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>M.</given-names>
            <surname>Haklay</surname>
          </string-name>
          et al.
          <article-title>How good is volunteered geographical information? A comparative study of OpenStreetMap and Ordnance Survey datasets</article-title>
          .
          <source>Environment and planning. B, Planning &amp; design</source>
          ,
          <volume>37</volume>
          (
          <issue>4</issue>
          ):
          <fpage>682</fpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>R. E.</given-names>
            <surname>Kalman</surname>
          </string-name>
          .
          <article-title>A new approach to linear filtering and prediction problems</article-title>
          .
          <source>Journal of Fluids Engineering</source>
          ,
          <volume>82</volume>
          (
          <issue>1</issue>
          ):
          <fpage>35</fpage>
          -
          <lpage>45</lpage>
          ,
          <year>1960</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>N.</given-names>
            <surname>Krismer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Silbernagl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Malfertheiner</surname>
          </string-name>
          , and
          <string-name>
            <given-names>G.</given-names>
            <surname>Specht</surname>
          </string-name>
          .
          <article-title>Elevation enabled bicycle router supporting user-profiles</article-title>
          .
          <source>Tagungsband zum 28</source>
          . GI-Workshop u¨ber
          <source>Grundlagen von Datenbanken (28th GI-Workshop on the Foundations of Databases)</source>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>S. K. M. Loidl</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Zagel</surname>
            and
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Reithofer. Radlkarte Salzburg - Das Radroutingportal</surname>
          </string-name>
          fu
          <article-title>¨r die Stadt Salzburg</article-title>
          .
          <source>In AGIT</source>
          , pages
          <fpage>456</fpage>
          -
          <lpage>461</lpage>
          . AGIT (
          <year>2013</year>
          ),
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18] mapquest.com. Official mapquest
          <article-title>- maps, driving directions, life traffic</article-title>
          . http://www.mapquest.com.
          <volume>16</volume>
          /07/
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>P.</given-names>
            <surname>Neis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Zielstra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Zipf</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Alexander</surname>
          </string-name>
          .
          <article-title>Empirische Untersuchungen zur Datenqualita¨t von OpenStreetMap-Erfahrungen aus zwei Jahren Betrieb mehrerer OSM-Online-Dienste</article-title>
          .
          <source>Angewandte Geoinformatik</source>
          <year>2010</year>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>OSM</given-names>
            <surname>Foundation</surname>
          </string-name>
          .
          <article-title>Opencyclemap.org - the openstreetmap cycle map</article-title>
          . http://www.opencyclemap.org, (
          <year>2016</year>
          ).
          <volume>22</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>OSM</given-names>
            <surname>Foundation</surname>
          </string-name>
          . Openstreetmap. http://www.openstreetmap.org/,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>OSM</given-names>
            <surname>Wiki</surname>
          </string-name>
          .
          <article-title>Routing/online routers - openstreetmap wiki</article-title>
          . http://wiki.openstreetmap.org/w/index.php? title=Routing/online_routers&amp;oldid=1205889,
          <year>2015</year>
          .
          <volume>26</volume>
          /11/
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <article-title>project-osrm.org. Open source routing machine</article-title>
          . http://project-osrm.
          <source>org</source>
          .
          <volume>16</volume>
          /07/
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>S.</given-names>
            <surname>Reddy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Shilton</surname>
          </string-name>
          , G. Denisov,
          <string-name>
            <given-names>C.</given-names>
            <surname>Cenizal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Estrin</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Srivastava</surname>
          </string-name>
          . Biketastic:
          <article-title>Sensing and mapping for better biking</article-title>
          .
          <source>In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, CHI '10</source>
          , pages
          <fpage>1817</fpage>
          -
          <lpage>1820</lpage>
          , New York, NY, USA,
          <year>2010</year>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>M.</given-names>
            <surname>Rexer</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.</given-names>
            <surname>Hirt</surname>
          </string-name>
          .
          <article-title>Comparison of free high resolution digital elevation data sets (ASTER GDEM2, SRTM v2.1/v4.1) and validation against accurate heights from the Australian National Gravity Database</article-title>
          .
          <source>Australian Journal of Earth Sciences</source>
          , pages
          <fpage>1</fpage>
          -
          <lpage>15</lpage>
          ,
          <year>02 2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <surname>A. P. B. Su</surname>
          </string-name>
          <article-title>¨dtirol. Landeskartografie digitales Gela¨ndemodell</article-title>
          . http://www.provinz.bz.it/natur-raum/themen/ landeskartografie-digitales-Gelaendemodell.asp, (
          <year>2016</year>
          ).
          <volume>12</volume>
          /01/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>J.</given-names>
            <surname>Topf</surname>
          </string-name>
          .
          <article-title>Openstreetmap taginfo</article-title>
          . http://taginfo.openstreetmap.org, (
          <year>2016</year>
          ).
          <volume>24</volume>
          /03/
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>