Open-Harbor/osrm-backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Describe options for trunk access in bicycle and foot profiles

Browse Source
This commit is contained in:
tombay 2024-10-05 15:43:55 +10:00 committed by GitHub
parent becfd8a56d
commit cbc129080b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/profiles.md
View File

@ -375,3 +375,20 @@ There are a few helper functions defined in the global scope that profiles can u
- `trimLaneString`
- `applyAccessTokens`
- `canonicalizeStringList`
### osrm-extract location dependent data
The creation of the dataset for routing use requires preprocessing of the osm data source.
The first preprocessing step is via osrm-extract.
Certain data (like driving-side or vehicle height) may be different between areas.
The "--location-dependent-data" command option can be used to pass geojson polygon data to support this differentiation.
### Highway support for Trunk Roads
The default routing profiles foot.lua and bicycle.lua do not allow access on ways with highway="trunk" or highway="trunk_link".
The wiki page outlining access restrictions ("https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access_restrictions") outlines seven countries that do not allow such access.
If the setup option uselocationtags includes 'trunk' then access is changed to yes for all countries.
To support routing data that honours different trunk access
- confirm uselocationtags = 'trunk' is set
- osrm-extract --location-dependent-data data/notrunk.geojson ...
This geojson sets the notrunk option for the seven countries (Austria, Belgium, Denmark, France, Hungary, Slovakia and Switzerland).