GIScience / GIScience/openrouteservice

Certain OSM access tag combinations are not correctly resolved

Open
#704 1 comment 0 reactions 1 assignee Claimed by @aoles View on GitHub
easy-fix 😎 osm routing network 🚧
Dominant language
Java
Stars
2k
Forks
481
Avg merge
1d 15h
Merged PRs (30d)
45

Description

Some transportation mode-specific access restrictions are currently not correctly interpreted. In particular, this is the case for hgv profiles. The main problem is that a more general restriction such as `access=no` overrides a more specific one such as `hgv=yes`. In particular, [there are ways open to agricultural and forestry traffic but closed for cars ](https://overpass-turbo.eu/s/TxD). If these are not taken into account certain routes might not be found. As a specific [example](https://maps.openrouteservice.org/directions?n1=49.363717&n2=8.881444&n3=17&a=49.373697,8.884356,49.361002,8.87484&b=4d&c=0&k1=en-US&k2=km) consider the [Verbindungsweg](https://www.openstreetmap.org/way/24036332).

Resolving access restrictions for subprofiles was problematic when routing with CH. Now with CALT these can be put into the core as resolved at query time, so the routing graph should include the transportation mode-specific ways too.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.