<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div><div>Hi Stephen,</div><div><br></div><div>Back in April I wrote a wiki page detailing the internal processing flow and data structures, did you see it?</div><div> </div><div><a href="https://github.com/DennisOSRM/Project-OSRM/wiki/Processing-Flow">https://github.com/DennisOSRM/Project-OSRM/wiki/Processing-Flow</a></div><div><br></div><div>Maybe there is some useful info there.</div><div><br></div><div>Dennis can probably tell you what has changed since April.</div><div><br></div><div><br></div><div>Best regards,</div><div>Emil</div><div><br></div><div><br></div><div><br></div><br><div><div>On 09 Nov 2013, at 17:38 , Stephen Woodbridge <<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi all,<br><br>I'm currently the lead developer for pgRouting and I'm interested in being able to create a local instance of OSRM that can be accessed via pgRouting. This all seems pretty straight forward to prototype up.<br><br>At the moment, I have a few questions on OSRM normalized file format. I want to be able to write a utility program for postgresql to prep and dump a pgRouting topology to an OSRM normalized file.<br><br>Looking at the edge section:<br><br>It appears that edges can be entered as undirected (ie: twoway with same costs in both directions) or directed in the case of oneway streets.<br><br>1. if I have a edge with different to-from and from-to costs am I correct in assuming that the way to enter this is to split the edge and enter it as two oneway edges with the appropriate costs?<br><br>2. oneway edges must be entered where from->to is the direction of the edge, ie: the direction must be to the target node?<br><br>3. Can you expound on the "rank of the speed profile"? Is this still used? in the Speedprofile page it says that this is now handled as LUA scripts.<br><br>Looking at the turn restrictions section:<br><br>Is there a graphic that explains this better. It is a little bit hard to follow where the various items come into play. There are references to via-node, from-node, to-node, from-way, and to-way.<br><br>Here is a common use case that I need to model. It is a majow road digitized as separated north and south bound lanes and intersected by a two way street digitized as a single line.<br><br> e h<br> | |<br> | |<br> | |<br>a---------b-----c---------d<br> | |<br> | |<br> | |<br> f g<br><br>Traffic is allowed:<br>ab-bc-cd - east bound cross traffic<br>dc-cb-ba - west bound cross traffic<br>eb-bf - one way south bound traffic<br>gc-ch - one way north bound traffic<br>ab-bc-ch - east bound onto north bound<br>ab-bf - east bound onto south bound<br>dc-ch - west bound onto north bound<br>dc-cb-bf - west bound onto south bound<br>eb-ba - south bound onto west bound<br>gc-cd - north bound onto east bound<br><br>U-Turns are not allowed:<br>eb-bc-ch - south bound u-turn to north bound<br>gc-cb-bf - north bound u-turn to south bound<br><br>and more obviously any turn the wrong way down a oneway edge.<br><br>Any help in understanding this would be greatly appreciated.<br><br>Thanks,<br> -Steve<br><br>_______________________________________________<br>OSRM-talk mailing list<br><a href="mailto:OSRM-talk@openstreetmap.org">OSRM-talk@openstreetmap.org</a><br>https://lists.openstreetmap.org/listinfo/osrm-talk<br></blockquote></div><br></body></html>