Improve Support for Multiple Turn Restrictions

[woodbri]

The current methodology for defining turn restrictions basically limits you to one restriction per record using the rule column. If you want to add multiple restrictions for a given edge you have to duplication the edge for each additional restriction and then add a single restriction to each new edge. This also requires that you then order by gid to group the restrictions together when you fetch the edges.

A better methodology is needed for describing this restrictions. For example, rule could be:

rule 1           rule 2          rule N
--------------   --------------  ...
<edge>[,<edge>][;<edge>[,<edge>]]*

this would allow any of the following rows

4
14,4
4;12
14,4;12
etc

[ja3n]

Is anyone interested in working on this? This would be a great feature.

[woodbri]

I have thought a lot about this and would be willing to add some additional thoughts on how to structure the data and why I think it might be useful to do so. I do not know C++, but I have a reasonable understanding of the Boost Graph concepts and can relate the restrictions tables to how these might be used in Boost Graph using a visitor method while traversing the graph.

Basically this would take a developer and I'm not sure we have any developers with time to work on additional development.