Routing algorithm / features
← Older revision
Revision as of 20:12, 11 August 2015
Line 54:
Line 54:
== Routing algorithm / features ==
== Routing algorithm / features ==
−
This
is
documented
at
http://www.cyclestreets.net/journey/help/,
although
that
documentation
does
not yet fully reflect the range of optimisations
in
place
.
+
CycleStreets
is
the
original
utility
cycle
journey
planner
for
cyclists,
by
cyclists
.
−
The
data
import
involves
a
set
of
[[http:/
/
www
.
cyclestreets
.
net/journey/help/osmconversion/
transformations
of the
OSM
data]]
,
followed
by
an
extensive
series
of
optimisations
and
pre-processing
to
increase
routing
performance
.
+
The
journey
planner aims to emulate the decision-making decisions of real cyclists,
giving
a
choice
of
routes to suit any ability. A wide variety of on-street factors are taken into account - such as road conditions, cycle infrastructure, partial favouring of Local Authority
/
national signed routes, paths and cut-throughs, directionality, surface quality, barriers, lighting and much more
.
Routing takes into account elevation at all times
.
Even the width
of
cycle lanes is taken into account in
the
determinations
of the best routes
,
where
such
data
exists
in
OpenStreetMap.
Basic
support
for
turn delays is in place and is
being
extended
shortly
.
−
That import results in a
[[http://www.cyclestreets.net/journey/help
/provision
/
simplified
list
of
provision
types
]]
,
against
which
routes
are
planned
. The
provision
types
table
is
the
only
subjective
aspect
in the routing.
+
[[http://www.cyclestreets.net/journey/help/
Various
aspects
of
the
journey planner implementation
]]
are
documented
within
the help
pages
.
(
The
documentation
does
not
yet fully reflect
the
range
of
optimisations
in
place, and will be updated later in 2015.) The data import involves a set of transformations of
the
OSM data, followed by an extensive series of optimisations and pre-processing to increase
routing
performance
.
−
The routing
takes account of
aspects
such
as
one-way
streets,
traffic
light
delays
.
Turn
delays
and turn restrictions
are
not yet implemented but are being actively worked on as high
priority
.
+
Routing
takes account of
hills/contours,
using
a
variety
of
elevation
data
sources
.
[[http://www.cyclestreets.net/blog/2009/10/08/elevation-profiles/
Elevation
profiles]]
are
also
shown
.
−
Routing
takes
account
of
hills/contours,
and
uses
SRTM.
[[http://www.cyclestreets
.
net/blog/2009/10/08/elevation-profiles/
Elevation
profiles]]
are
also
shown
.
+
Routes
are
saved
to
a
user's
profile
if
signed in
.
Export
of
planned routes in KML and GPX
is
provided
.
−
−
Export of planned routes in KML and GPX is provided.
−
−
Routes are saved to a user's profile if signed in.
Photos (see below) geolocated along a planned route are shown on the route ("Photos-en-route"). There is also a Google StreetView integration.
Photos (see below) geolocated along a planned route are shown on the route ("Photos-en-route"). There is also a Google StreetView integration.
−
The developers are keen to encourage feedback, and provide a customised feedback form on each page. Routing feedback is sent to a list which includes a few OSMers. An improved feedback
-
handling system is under development to allow greater OSM community visibility of data issues which are highlighted by problematic routes that users have planned.
+
The developers are keen to encourage feedback, and provide a customised feedback form on each page. Routing feedback is sent to a list which includes a few OSMers. An improved feedback
handling
and triaging
system is
, as of 2015,
under development to allow greater OSM community visibility of data issues which are highlighted by problematic routes that users have planned.
== Photomap ==
== Photomap ==