[OSRM-talk] Using custom data

[Daniel Patterson]

Hi Matthias,

  Emil is right, your ways are not connected.  The connection needs to happen like this:

  <way id="1">
    <nd ref="1"/>
    <nd ref="2"/>
  </way>

  <way id="2">
    <nd ref="2"/>       <----- same node as in way 1
    <nd ref="3"/>
  </way>

  It is not enough to just have nodes at the same lat/lon, you actually have to refer to the same <node> for ways to be joined.
  If you fix that in your file, you should be able to route on it.

daniel

> On Oct 15, 2015, at 8:28 AM, Matthias Loeks <matthias at loeks.net> wrote:
> 
> Hi Emil,
> 
> thanks for your answer.
> Well, they look correct in JOSM and I paid attention to add the nodes and then the node relations in the ways properly when assembling the OSM XML.
> 
> Does OSRM rely on any additional OSM nodes at the junctions? Doesn't it node the graph itself anyway?
> 
> Cheers,
> Matthias
> 
> On 15.10.2015 14:20, Emil Tin wrote:
>> Are you sure segments are connected at the noded?
>> 
>> Sendt fra min HTC-telefon
>> 
>> ----- Reply message -----
>> Fra: "Matthias Loeks" <matthias at loeks.net> <mailto:matthias at loeks.net>
>> Til: "osrm-talk at openstreetmap.org" <mailto:osrm-talk at openstreetmap.org> <osrm-talk at openstreetmap.org> <mailto:osrm-talk at openstreetmap.org>
>> Emne: [OSRM-talk] Using custom data
>> Dato: tor, okt. 15, 2015 13:19
>> 
>> Hi list,
>> 
>> I'm running a little experiment with using custom geo data for OSRM.
>> Following the advice of [1], I converted my data to OSM XML format, for 
>> now neglecting all kinds of tags/attributes etc. (this could be done later).
>> You can find the resulting OSM file here: 
>> https://dl.dropboxusercontent.com/u/56544580/extract.osm <https://dl.dropboxusercontent.com/u/56544580/extract.osm>
>> The file can be viewed correctly using JOSM.
>> 
>> I also created a very basic profile: 
>> https://dl.dropboxusercontent.com/u/56544580/custom.lua <https://dl.dropboxusercontent.com/u/56544580/custom.lua>
>> This profile should just contain the necessary variables read by 
>> osrm-extract. It should not exclude any of the OSM nodes or ways, just 
>> let them all pass through to the routing graph. Also, there should be no 
>> turn restrictions.
>> 
>> The processing chain (extract, prepare) runs successfully and I can also 
>> start the osrm-routed server.
>> The locate and nearest services are working fine. However, the viaroute 
>> service returns only a valid route, if just one segment is involved. As 
>> soon as there are junctions, no route can be calculated (code 207).
>> 
>> Can this be related to the turn restrictions? I had hoped they would be 
>> entirely ignored if switched off in the profile.
>> Or am I missing something else important in my profile or data?
>> Are there maybe any OSM tags which are absolutely required by OSRM 
>> directly, even if a fully customised profile is being used?
>> 
>> Any help or suggestions on this are greatly appreciated!
>> 
>> Many thanks and best regards,
>> Matthias
>> 
>> --
>> [1] - 
>> https://lists.openstreetmap.org/pipermail/osrm-talk/2015-May/000844.html <https://lists.openstreetmap.org/pipermail/osrm-talk/2015-May/000844.html>
>> 
>> 
>> _______________________________________________
>> OSRM-talk mailing list
>> OSRM-talk at openstreetmap.org <mailto:OSRM-talk at openstreetmap.org>
>> https://lists.openstreetmap.org/listinfo/osrm-talk <https://lists.openstreetmap.org/listinfo/osrm-talk>
>> 
>> 
>> _______________________________________________
>> OSRM-talk mailing list
>> OSRM-talk at openstreetmap.org <mailto:OSRM-talk at openstreetmap.org>
>> https://lists.openstreetmap.org/listinfo/osrm-talk <https://lists.openstreetmap.org/listinfo/osrm-talk>
> _______________________________________________
> OSRM-talk mailing list
> OSRM-talk at openstreetmap.org <mailto:OSRM-talk at openstreetmap.org>
> https://lists.openstreetmap.org/listinfo/osrm-talk <https://lists.openstreetmap.org/listinfo/osrm-talk>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osrm-talk/attachments/20151015/06c952b5/attachment-0001.html>