Takes a stricter aproach for whitelisting / blacklisting restrictions: - uses `restriction=` - uses more specific `restriction:<type>=` - uses `except=<type>` to invert Where `type` is the type of transportation to restrict, e.g. `motorcar`. https://github.com/Project-OSRM/osrm-backend/issues/2833
57 lines
1.5 KiB
C++
57 lines
1.5 KiB
C++
#ifndef RESTRICTION_PARSER_HPP
|
|
#define RESTRICTION_PARSER_HPP
|
|
|
|
#include "extractor/restriction.hpp"
|
|
|
|
#include <boost/optional/optional.hpp>
|
|
|
|
#include <string>
|
|
#include <vector>
|
|
|
|
namespace osmium
|
|
{
|
|
class Relation;
|
|
}
|
|
|
|
namespace osrm
|
|
{
|
|
namespace extractor
|
|
{
|
|
|
|
class ScriptingEnvironment;
|
|
|
|
/**
|
|
* Parses the relations that represents turn restrictions.
|
|
*
|
|
* Currently only restrictions where the via objects is a node are supported.
|
|
* from via to
|
|
* ------->(x)-------->
|
|
*
|
|
* While this class does not directly invoke any lua code _per relation_ it does
|
|
* load configuration values from the profile, that are saved in variables.
|
|
* Namely ```use_turn_restrictions``` and ```get_restrictions```.
|
|
*
|
|
* The restriction is represented by the osm id of the from way, the osm id of the
|
|
* to way and the osm id of the via node. This representation must be post-processed
|
|
* in the extractor to work with the edge-based data-model of OSRM:
|
|
* Since the from and to way share the via-node a turn will have the following form:
|
|
* ...----(a)-----(via)------(b)----...
|
|
* So it can be represented by the tripe (a, via, b).
|
|
*/
|
|
class RestrictionParser
|
|
{
|
|
public:
|
|
RestrictionParser(ScriptingEnvironment &scripting_environment);
|
|
boost::optional<InputRestrictionContainer> TryParse(const osmium::Relation &relation) const;
|
|
|
|
private:
|
|
bool ShouldIgnoreRestriction(const std::string &except_tag_string) const;
|
|
|
|
std::vector<std::string> restrictions;
|
|
bool use_turn_restrictions;
|
|
};
|
|
}
|
|
}
|
|
|
|
#endif /* RESTRICTION_PARSER_HPP */
|