osrm-backend/include/extractor/extraction_node.hpp

#ifndef EXTRACTION_NODE_HPP
#define EXTRACTION_NODE_HPP

#include "traffic_lights.hpp"

namespace osrm::extractor
{

struct ExtractionNode
{
    ExtractionNode() : traffic_lights(TrafficLightClass::NONE), barrier(false) {}
    void clear()
    {
        traffic_lights = TrafficLightClass::NONE;
        barrier = false;
    }
    TrafficLightClass::Direction traffic_lights;
    bool barrier;
};
} // namespace osrm::extractor

#endif // EXTRACTION_NODE_HPP
renamed: extractor.cpp -> extract.cpp renamed: Extractor/* -> extractor/ 2014-11-28 09:00:48 -05:00			`#ifndef EXTRACTION_NODE_HPP`
			`#define EXTRACTION_NODE_HPP`
implement ExtractionWay and -Node 2014-08-26 11:02:05 -04:00
Support OSM traffic signal directions (#6153) Currently OSRM parses traffic signal nodes without consideration for the direction in which the signal applies. This can lead to duplicated routing penalties, especially when a forward and backward signal are in close proximity on a way. This commit adds support for directed signals to the extraction and graph creation. Signal penalties are only applied in the direction specified by the OSM tag. We add the assignment of traffic directions to the lua scripts, maintaining backwards compatibility with the existing boolean traffic states. As part of the changes to the internal structures used for tracking traffic signals during extraction, we stop serialising/deserialising signals to the `.osrm` file. The traffic signals are only used by `osrm-extract` so whilst this is a data format change, it will not break any existing user processes. 2022-08-30 05:36:49 -04:00			`#include "traffic_lights.hpp"`

Use nested namespace It's a mechanical change to modernize the code base 2022-12-11 04:10:26 -05:00			`namespace osrm::extractor`
Add namespace around all files 2016-01-05 10:51:13 -05:00			`{`

implement ExtractionWay and -Node 2014-08-26 11:02:05 -04:00			`struct ExtractionNode`
			`{`
Support OSM traffic signal directions (#6153) Currently OSRM parses traffic signal nodes without consideration for the direction in which the signal applies. This can lead to duplicated routing penalties, especially when a forward and backward signal are in close proximity on a way. This commit adds support for directed signals to the extraction and graph creation. Signal penalties are only applied in the direction specified by the OSM tag. We add the assignment of traffic directions to the lua scripts, maintaining backwards compatibility with the existing boolean traffic states. As part of the changes to the internal structures used for tracking traffic signals during extraction, we stop serialising/deserialising signals to the `.osrm` file. The traffic signals are only used by `osrm-extract` so whilst this is a data format change, it will not break any existing user processes. 2022-08-30 05:36:49 -04:00			`ExtractionNode() : traffic_lights(TrafficLightClass::NONE), barrier(false) {}`
			`void clear()`
			`{`
			`traffic_lights = TrafficLightClass::NONE;`
			`barrier = false;`
			`}`
			`TrafficLightClass::Direction traffic_lights;`
implement ExtractionWay and -Node 2014-08-26 11:02:05 -04:00			`bool barrier;`
			`};`
Fix formatting 2022-12-20 12:00:11 -05:00			`} // namespace osrm::extractor`
Add namespace around all files 2016-01-05 10:51:13 -05:00
renamed: extractor.cpp -> extract.cpp renamed: Extractor/* -> extractor/ 2014-11-28 09:00:48 -05:00			`#endif // EXTRACTION_NODE_HPP`