[GraphHopper] Maneuvers implementation

[Nicolas Gillet]

Hello,

We had a discussion with a partner this morning about maneuvers' integration in GraphHopper.
I know that there is a pull request from khuebner about it on github but I'd like to know which approach was chosen to implements these restrictions.

Basically, I see two options :

1.       Substitute a restricted node by 3 or 4 node, and create edges between theses nodes (with à cost/infinite) to represent the turn cost or restriction.

2.       Add a direction to each node while routing and check if the move is allowed according to some restriction data stored somewhere.

The first solution creates more nodes and edges in the graph but does not require any changes in routing algorithm.
The second solution requires to create separate storage for the restrictions and forces every algorithm to be updated to take it into account.

We are preferring the first solution as our own algorithm would not need to be modified and thus thinking about further update makes me expect potentially hard rework.

So my question is, which solution was chosen in the pr/55 ?


Kind regards,

Nicolas GILLET


Market-IP - Creating Mobile Intelligence
Phone : +32 81 33 11 11
Fax : +32 81 33 11 10
www.market-ip.com<http://www.market-ip.com/> - www.telefleet.com<http://www.telefleet.com/> - www.geoplanning.net<http://www.geoplanning.net/> - www.drivexpert.net<http://www.drivexpert.net/>
[Description : cid:image003.png at 01CD5521.849F3340]<http://www.linkedin.com/groups/MarketIP-4289716?gid=4289716&trk=hb_side_g>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20130911/420b6240/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1263 bytes
Desc: image001.png
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20130911/420b6240/attachment.png>