Take stop signs into account during routing
This commit is contained in:
@@ -11,14 +11,8 @@ namespace osrm
|
||||
namespace extractor
|
||||
{
|
||||
|
||||
// Stop Signs tagged on nodes can be present or not. In addition Stop Signs have
|
||||
// an optional way direction they apply to. If the direction is unknown from the
|
||||
// data we have to compute by checking the distance to the next intersection.
|
||||
//
|
||||
// Impl. detail: namespace + enum instead of enum class to make Luabind happy
|
||||
|
||||
// The traffic light annotation is extracted from node tags.
|
||||
// The directions in which the traffic light applies are relative to the way containing the node.
|
||||
// The direction annotation is extracted from node tags.
|
||||
// The directions in which traffic flow object applies are relative to the way containing the node.
|
||||
enum class TrafficFlowControlNodeDirection : std::uint8_t
|
||||
{
|
||||
NONE = 0,
|
||||
|
||||
Reference in New Issue
Block a user