Maneuvers and Turn Restriction Definitions
In general, there are various ways that turn restrictions can be defined in various data sets. In fact in a more abstract definition we might think of a vehicle and define what maneuvers that vehicle is restricted from. These maneuvers can be restricted by time of day, class of vehicle, and via legal or physical restrictions. There may be restrictions based on tool booth, closed due to construction, gates or bollards, direction of travel, carpool, turn restriction, access restriction, or others.
Since pgRouting does not currently support time of day based routing, I will only mention these restrictions in passing to give some context for future design consideration. Also, we are primarily looking at turn restrictions since the other restrictions are handled in other ways within pgRouting.
TRSP definitions are edge based restrictions.
- target_id - edge id of a target edge that we are arriving at
- cost - cost to follow this restriction (-1 should mean the maneuver is prohibited)
- from_id_list - comma separated list of edge ids where the 1st is the parent of the target, the 2nd is the parent of the 1st, and so on.
This definition is also edge based restrictions.
The following structure can easily be extract form a few commercial data sets I have worked with.
- restriction_id - unique id for this restriction
- restriction_type - type of restriction: normal, time, class
- class_list - list of vehicle classes this applies to
- seq_numbers - used to order edges when multiple edges are involved in restriction
- edge_id - edge id for in this restriction
OSM supports both edge-node-edge and edge[-node-edge]+ restrictions. (correct?)
TODO
The open source data does not include turn restrictions
- https://www.ordnancesurvey.co.uk/opendatadownload/products.html Documentation is here:
- https://www.ordnancesurvey.co.uk/business-and-government/help-and-support/products/os-open-roads.html
- https://www.ordnancesurvey.co.uk/docs/technical-specifications/os-mastermap-highways-network-roads-technical-specification.pdf
See a feature comparison between "Roads" and "Routing and Asset Management" products here:
-
https://www.ordnancesurvey.co.uk/business-and-government/products/os-mastermap-highways-network.html Documentation is here:
-
https://www.ordnancesurvey.co.uk/docs/technical-specifications/os-mastermap-highways-network-routing-and-asset-management-technical-specification.pdf (see chap. 4, Rights and Restrictions)
-
Add turn restrictions from OS Highways (paid data) - https://github.com/mixedbredie/highways-for-pgrouting#6-adding-in-turn-restrictions
TODO
TODO
- Note: Spanish language used
- Website: http://www.inegi.org.mx/
- Download service: TODO
- id - unique manoeuvre id
- kohd_id - object link id (dest link id?)
- kuntakoodi - the municipality code
- lahd_id - source link id
- lisatiedot - additional information
- moukkauspv - mod date
- poikkeus - exception
- voim_aika - end of time
- Note: Digital road map data of Finland. is available as Open Data and it's supposed to contain turn restriction information. The latter is rare with open data, so I thought it might worth to see, how turn restrictions look like in this dataset.
- Website: http://www.liikennevirasto.fi/web/en/open-data/digiroad
- Download Service: https://extranet.liikennevirasto.fi/extranet/web/public/latauspalvelu Spec "Description of Data Objects": http://www.liikennevirasto.fi/documents/20473/236203/Data_Object_Description_1_2017_ENG.pdf/52901604-c8c5-446c-9348-324eeb15a76c Spec "Readme": http://www.liikennevirasto.fi/documents/20473/236203/ReadMe_1_2017.pdf/12dc587a-a9c3-49cb-86a2-0b3664ac3205
TODO
