<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/24/2012 12:16 PM, Tom Hughes
wrote:<br>
</div>
<blockquote class=" cite" id="mid_5037C4F4_6050602_compton_nu"
cite="mid:5037C4F4.6050602@compton.nu" type="cite">On 24/08/12
17:29, Kai Krueger wrote:
<br>
<br>
<blockquote class=" cite" id="Cite_45" type="cite">With
<a class="moz-txt-link-freetext" href="http://routing.apis.dev.openstreetmap.org/">http://routing.apis.dev.openstreetmap.org/</a> there is also a
<br>
functional prototype for integrating routing into the osm.org.
It
<br>
currently uses map.project-osrm.org as the default car routing
backend
<br>
and gosmore as the default backend for other modes of transport.
One can
<br>
also select MapQuest and CloudMade as routing engines to compare
them.
<br>
</blockquote>
<br>
Prototype being the operative word - it is not in any way
production ready code.
<br>
</blockquote>
<br>
The code is mostly concentrated in two or three new files. Most of
that is just code that transcodes the output from the routing
backend into kml that openlayers can process as well as creating the
routing sidebar. On top there are a few bits and bobs that interact
with the rest of the code. Overall it is probably only a few hundred
lines of code, i.e. nothing overly substantial substantial.<br>
<br>
So imho there is nothing in it, that couldn't be reviewed, fixed and
improved and deployed in a single hackweekend. It could probably
even be rewritten from scratch in a weekend.<br>
<br>
A wonderful example of what great things (feature wise in the rails
port) we can do if we collectively put our heads together was the
hackweekend in 2009 during which the internationalisation of osm.org
was completed, reviewed and deployed. It was an effective
collaboration with a number of local rails_port developers in a room
together with quite a bunch of other people helping out remotely,
including non-coders, contributing from updated code to translations
and testing (and moral support). At the end of the weekend, an
amazing amount was achieved which lead to its successful deployment.<br>
<br>
If we could get this kind of coordinated collaboration and
enthusiasm going again, I think we could relatively quickly complete
a number of the long outstanding and desired features.<br>
<br>
But this is getting rather off topic for the OSMF board elections.<br>
<br>
Kai<br>
<br>
<br>
<br>
<blockquote class=" cite" id="mid_5037C4F4_6050602_compton_nu"
cite="mid:5037C4F4.6050602@compton.nu" type="cite">
<br>
<blockquote class=" cite" id="Cite_46" type="cite">Therefore I
think that all of the necessary components to integrate
<br>
routing into osm.org are now available. So as soon as OSMF buys
the
<br>
necessary hardware, one could probably integrate routing into
osm.org
<br>
comparatively quickly and easily.
<br>
</blockquote>
<br>
Getting hardware is not a problem, but there's no point doing that
until we have production ready code, or at least expect to have
such code within a few weeks.
<br>
<br>
Tom
<br>
<br>
</blockquote>
<br>
</body>
</html>