<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta name="x_Generator" content="Microsoft Exchange Server">
<style>
<!--
.x_EmailQuote
{margin-left:1pt;
padding-left:4pt;
border-left:#800000 2px solid}
-->
</style>
<div>
<div style="font-size:12pt; font-family:Calibri,sans-serif">
<div>Are you sure segments are connected at the noded?</div>
<div><br>
</div>
<div>Sendt fra min HTC-telefon</div>
<br>
<div id="x_htc_header">----- Reply message -----<br>
Fra: "Matthias Loeks" <matthias@loeks.net><br>
Til: "osrm-talk@openstreetmap.org" <osrm-talk@openstreetmap.org><br>
Emne: [OSRM-talk] Using custom data<br>
Dato: tor, okt. 15, 2015 13:19</div>
</div>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi list,<br>
<br>
I'm running a little experiment with using custom geo data for OSRM.<br>
Following the advice of [1], I converted my data to OSM XML format, for <br>
now neglecting all kinds of tags/attributes etc. (this could be done later).<br>
You can find the resulting OSM file here: <br>
<a href="https://dl.dropboxusercontent.com/u/56544580/extract.osm">https://dl.dropboxusercontent.com/u/56544580/extract.osm</a><br>
The file can be viewed correctly using JOSM.<br>
<br>
I also created a very basic profile: <br>
<a href="https://dl.dropboxusercontent.com/u/56544580/custom.lua">https://dl.dropboxusercontent.com/u/56544580/custom.lua</a><br>
This profile should just contain the necessary variables read by <br>
osrm-extract. It should not exclude any of the OSM nodes or ways, just <br>
let them all pass through to the routing graph. Also, there should be no <br>
turn restrictions.<br>
<br>
The processing chain (extract, prepare) runs successfully and I can also <br>
start the osrm-routed server.<br>
The locate and nearest services are working fine. However, the viaroute <br>
service returns only a valid route, if just one segment is involved. As <br>
soon as there are junctions, no route can be calculated (code 207).<br>
<br>
Can this be related to the turn restrictions? I had hoped they would be <br>
entirely ignored if switched off in the profile.<br>
Or am I missing something else important in my profile or data?<br>
Are there maybe any OSM tags which are absolutely required by OSRM <br>
directly, even if a fully customised profile is being used?<br>
<br>
Any help or suggestions on this are greatly appreciated!<br>
<br>
Many thanks and best regards,<br>
Matthias<br>
<br>
--<br>
[1] - <br>
<a href="https://lists.openstreetmap.org/pipermail/osrm-talk/2015-May/000844.html">https://lists.openstreetmap.org/pipermail/osrm-talk/2015-May/000844.html</a><br>
<br>
<br>
_______________________________________________<br>
OSRM-talk mailing list<br>
OSRM-talk@openstreetmap.org<br>
<a href="https://lists.openstreetmap.org/listinfo/osrm-talk">https://lists.openstreetmap.org/listinfo/osrm-talk</a><br>
</div>
</span></font>
</body>
</html>