[OSRM-talk] Questions on OSRM normalized file format
Hi all, 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. 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. Looking at the edge section: 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. 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? 2. oneway edges must be entered where from-to is the direction of the edge, ie: the direction must be to the target node? 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. Looking at the turn restrictions section: 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. 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. e h | | | | | | a-b-c-d | | | | | | f g Traffic is allowed: ab-bc-cd - east bound cross traffic dc-cb-ba - west bound cross traffic eb-bf - one way south bound traffic gc-ch - one way north bound traffic ab-bc-ch - east bound onto north bound ab-bf - east bound onto south bound dc-ch - west bound onto north bound dc-cb-bf - west bound onto south bound eb-ba - south bound onto west bound gc-cd - north bound onto east bound U-Turns are not allowed: eb-bc-ch - south bound u-turn to north bound gc-cb-bf - north bound u-turn to south bound and more obviously any turn the wrong way down a oneway edge. Any help in understanding this would be greatly appreciated. Thanks, -Steve ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk
Re: [OSRM-talk] Questions on OSRM normalized file format
Hi Stephen, Back in April I wrote a wiki page detailing the internal processing flow and data structures, did you see it? https://github.com/DennisOSRM/Project-OSRM/wiki/Processing-Flow Maybe there is some useful info there. Dennis can probably tell you what has changed since April. Best regards, Emil On 09 Nov 2013, at 17:38 , Stephen Woodbridge wood...@swoodbridge.com wrote: Hi all, 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. 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. Looking at the edge section: 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. 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? 2. oneway edges must be entered where from-to is the direction of the edge, ie: the direction must be to the target node? 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. Looking at the turn restrictions section: 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. 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. e h | | | | | | a-b-c-d | | | | | | f g Traffic is allowed: ab-bc-cd - east bound cross traffic dc-cb-ba - west bound cross traffic eb-bf - one way south bound traffic gc-ch - one way north bound traffic ab-bc-ch - east bound onto north bound ab-bf - east bound onto south bound dc-ch - west bound onto north bound dc-cb-bf - west bound onto south bound eb-ba - south bound onto west bound gc-cd - north bound onto east bound U-Turns are not allowed: eb-bc-ch - south bound u-turn to north bound gc-cb-bf - north bound u-turn to south bound and more obviously any turn the wrong way down a oneway edge. Any help in understanding this would be greatly appreciated. Thanks, -Steve ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk
Re: [OSRM-talk] Questions on OSRM normalized file format
Yes, but I will read it again. I'm still trying to get up to speed on everything. Dennis, if you can answer my questions below that would be appreciated. By the way, I'm extremely pleased that you have redone this under the BSD license. I look forward to workign with you guys and integrating this into pgRouting. Thanks, -Steve On 11/9/2013 12:17 PM, Emil Tin wrote: Hi Stephen, Back in April I wrote a wiki page detailing the internal processing flow and data structures, did you see it? https://github.com/DennisOSRM/Project-OSRM/wiki/Processing-Flow Maybe there is some useful info there. Dennis can probably tell you what has changed since April. Best regards, Emil On 09 Nov 2013, at 17:38 , Stephen Woodbridge wood...@swoodbridge.com mailto:wood...@swoodbridge.com wrote: Hi all, 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. 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. Looking at the edge section: 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. 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? 2. oneway edges must be entered where from-to is the direction of the edge, ie: the direction must be to the target node? 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. Looking at the turn restrictions section: 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. 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. e h | | | | | | a-b-c-d | | | | | | f g Traffic is allowed: ab-bc-cd - east bound cross traffic dc-cb-ba - west bound cross traffic eb-bf - one way south bound traffic gc-ch - one way north bound traffic ab-bc-ch - east bound onto north bound ab-bf - east bound onto south bound dc-ch - west bound onto north bound dc-cb-bf - west bound onto south bound eb-ba - south bound onto west bound gc-cd - north bound onto east bound U-Turns are not allowed: eb-bc-ch - south bound u-turn to north bound gc-cb-bf - north bound u-turn to south bound and more obviously any turn the wrong way down a oneway edge. Any help in understanding this would be greatly appreciated. Thanks, -Steve ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org mailto:OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk
Re: [OSRM-talk] Questions on OSRM normalized file format
OK, I have read most all the wiki pages and I'm not getting how the restrictions are being defined. So a little help getting over the mind block I seem to be having for this. Everything else seems really straight forward, so I can't imagine that the restrictions are all the complicated, but it is not clicking with any confidence in my head yet. If I have the following: ab-c | | d ab, bc, and db are all two way and there is no right turn from db to bc Then is the restriction: b, d, c, forbidden, 7F 00 00 where: b is the via-node d is the from-node c is the to-node and the records should then be sorted by EDGE[via-node, to-node] ref. Is this correct? Thanks, -Steve On 11/9/2013 2:52 PM, Stephen Woodbridge wrote: Yes, but I will read it again. I'm still trying to get up to speed on everything. Dennis, if you can answer my questions below that would be appreciated. By the way, I'm extremely pleased that you have redone this under the BSD license. I look forward to workign with you guys and integrating this into pgRouting. Thanks, -Steve On 11/9/2013 12:17 PM, Emil Tin wrote: Hi Stephen, Back in April I wrote a wiki page detailing the internal processing flow and data structures, did you see it? https://github.com/DennisOSRM/Project-OSRM/wiki/Processing-Flow Maybe there is some useful info there. Dennis can probably tell you what has changed since April. Best regards, Emil On 09 Nov 2013, at 17:38 , Stephen Woodbridge wood...@swoodbridge.com mailto:wood...@swoodbridge.com wrote: Hi all, 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. 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. Looking at the edge section: 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. 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? 2. oneway edges must be entered where from-to is the direction of the edge, ie: the direction must be to the target node? 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. Looking at the turn restrictions section: 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. 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. e h | | | | | | a-b-c-d | | | | | | f g Traffic is allowed: ab-bc-cd - east bound cross traffic dc-cb-ba - west bound cross traffic eb-bf - one way south bound traffic gc-ch - one way north bound traffic ab-bc-ch - east bound onto north bound ab-bf - east bound onto south bound dc-ch - west bound onto north bound dc-cb-bf - west bound onto south bound eb-ba - south bound onto west bound gc-cd - north bound onto east bound U-Turns are not allowed: eb-bc-ch - south bound u-turn to north bound gc-cb-bf - north bound u-turn to south bound and more obviously any turn the wrong way down a oneway edge. Any help in understanding this would be greatly appreciated. Thanks, -Steve ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org mailto:OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk ___ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk
