<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Ballontekst Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.E-mailStijl17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BallontekstChar
{mso-style-name:"Ballontekst Char";
mso-style-priority:99;
mso-style-link:Ballontekst;
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:619335502;
mso-list-template-ids:1100002446;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:788014461;
mso-list-template-ids:-1430486964;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=NL link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Graag jullie mening over onderstaand funding request<o:p></o:p></p>
<p class=MsoNormal>voor iets van de resterende 15K.<o:p></o:p></p>
<p class=MsoNormal>In dat geval kunnen we 8-16 uur betaalbaar stellen.<o:p></o:p></p>
<p class=MsoNormal>Ervan uitgaande dat buitenlandse bijdragen geen probleem
vormen.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Let wel, het gaat om de uitbreiding in de 2<sup>e</sup>
lijst met aandachtspunten.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-US>I've been following the proposal for
funding OSM software development during the last months. As I understand from
the last news [1] the project is now open for funding small projects which
provide other functionalities than the ones that were considered as most
important (mobile editor, compatibility with GEO protocols, etc.).<br>
<br>
Our proposal is for a new routing plugin for JOSM (there was an older one which
is no longer functional). We've almost finished a first version of this plugin
with the following basic funcionality:<o:p></o:p></span></p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo1'><span lang=EN-US>Create and remove routing
layers. Each routing layer is associated with a data layer.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo1'><span lang=EN-US>Add, remove and move routing
nodes to a routing layer. When more than 2 nodes are added, a route is
computed and displayed. Adding, removing and moving route nodes triggers
route calculation again, and refreshes the routing layer.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo1'><span lang=EN-US>Compute reverse route.<o:p></o:p></span></li>
</ul>
<p class=MsoNormal><span lang=EN-US>This plugin will be soon published. We
think it provides some benefits to the OSM community, like enabling the testing
of connectivity between 2 given nodes, to make sure a certain area is suitable
for routing for other applications, and fixing connectivity problems, since
detected errors can be directly fixed by means of JOSM editing capabilities.<br>
<br>
We have ideas to add further functionalities in newer versions, but this is an
spare-time project for us, and our resources are limited. These functionalities
would include:<o:p></o:p></span></p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo2'><span lang=EN-US>Create and remove connectivity
layers. This kind of layer would show a shortest path tree on a given
area, given an origin point (and optionally a search radius), so you can
actually see the full connectivity from an origin node in an area, and
detect separate areas (like footpaths in parks not being connected with
streets).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo2'><span lang=EN-US>Considering speed limits and
turn restrictions in routing.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo2'><span lang=EN-US>Define different routing
profiles. User defined routing profiles would allow to define a bicycle
profile, car profile, foot profile, disabled profile, and so on, with
different use of oneway tags, turn restrictions, speed limits and
different speed for each highway type, for each kind of user.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo2'><span lang=EN-US>Create and remove traveling
salesman layers. This kind of layer may be useful for mapping parties. A
shortest path traversing all desired nodes would be computed. For areas
without any osm data, you would sketch the streets with and WMS overlay
and select nodes to be traversed in the most efficient way. We still
haven't made provisions about which computation requirements and
limitations would present this functionality.<o:p></o:p></span></li>
</ul>
<p class=MsoNormal><span lang=EN-US>To sum up, we are thinking in both final
user functionalities and mapping user functionalities. I was wondering if the
funding project would be interested in such an application. Also, if you are
interested in testing the first version when it's finally released, just keep
in touch.<br>
<br>
<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal>Gert Gremmen<o:p></o:p></p>
<p class=MsoNormal>-----------------------------------------------------<o:p></o:p></p>
<p class=MsoNormal><img width=150 height=50 id="Afbeelding_x0020_1"
src="cid:image001.gif@01C9934B.FC127C70" alt=Osm><o:p></o:p></p>
<p class=MsoNormal><span lang=EN-US>Openstreetmap.nl (alias: cetest)<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:13.5pt;font-family:Webdings;color:green'>P</span><b><span
lang=EN-US style='font-size:9.0pt;color:green'> Before printing, think about
the environment.</span></b><span lang=EN-US style='font-size:9.0pt'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
</body>
</html>