Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HGV access restrictions #235

Closed
aoles opened this issue Aug 2, 2018 · 5 comments
Closed

HGV access restrictions #235

aoles opened this issue Aug 2, 2018 · 5 comments
Assignees
Labels
bug 🐞 Erroneous behavior of the backend
Milestone

Comments

@aoles
Copy link
Member

aoles commented Aug 2, 2018

Access restrictions/permissions doesn't seem to be properly resolved for driving-* profiles. Consider the following example for driving-hgv withvehicle_type=agricultural:

https://maps.openrouteservice.org/directions?n1=49.465&n2=8.658385&n3=15&a=49.469532,8.658686,49.464359,8.660789&b=4d&c=0&k1=en-US&k2=km

image

The direct route is not found even though the way has the OSM tag access=agricultural.

Interestingly, the same route is returned for driving-cardespite that these roads are restricted to agricultural usage: https://overpass-turbo.eu/s/AL3. UPDATE: access=agricultural alone just permits agricultural usage without restricting it for regular traffic unless used in combination with motor_vehicle restrictions such as

image

Things get even more funky when profile restrictions, such as hazmat=true are enabled. Then the route above changes the one below, even though there are no hazmat restrictions in this area! Seems to be related to #209 and #211.

image

@aoles aoles added the bug 🐞 Erroneous behavior of the backend label Aug 2, 2018
@aoles aoles self-assigned this Aug 2, 2018
@aoles aoles changed the title HGV routing Road access restrictions Aug 2, 2018
@aoles
Copy link
Member Author

aoles commented Aug 17, 2018

UPDATE highway=track below tracktype=grade1 are excluded from the road network by HeavyVehicleFlagEncoder based on maxTrackGradeLevel. While this can be specified in the encoder options in app.config, the defaults for CarFlagEncoder and HeavyVehicleFlagEncoder are 3 and 1, respectively.

Consider revising these settings to allow routing of agricultural or forestry vehicles on lower grade tracks.

@aoles
Copy link
Member Author

aoles commented Aug 17, 2018

Roads with access=agricultural are filtered out by both CarFlagEncoder and HeavyVehicleFlagEncoder because of agricultural being in restrictedValues. However, ways tagged with multiple values such as agricultural;forestry are not picked up by this filter which explains why it's still possible to still go around from A to B in the example above.

Consider keeping ways tagged as agricultural for hgv profile because of agricultural and forestry subprofiles.

@rabidllama rabidllama added this to the 4.7 milestone Aug 21, 2018
@aoles aoles removed this from the 4.7 milestone Oct 10, 2018
@rabidllama rabidllama added this to the 4.7.2 milestone Oct 12, 2018
@aoles aoles changed the title Road access restrictions HGV access restrictions Nov 28, 2018
rabidllama pushed a commit that referenced this issue Dec 5, 2018
@rabidllama
Copy link
Contributor

What is the status of this as in the new release it does not go down the direct way?

@aoles
Copy link
Member Author

aoles commented Dec 22, 2018

What is the status of this as in the new release it does not go down the direct way?

It does not route down the direct way because it is of tracktype=grade3 as mentioned previously:

UPDATE highway=track below tracktype=grade1 are excluded from the road network by HeavyVehicleFlagEncoder based on maxTrackGradeLevel. While this can be specified in the encoder options in app.config, the defaults for CarFlagEncoder and HeavyVehicleFlagEncoder are 3 and 1, respectively.

Consider revising these settings to allow routing of agricultural or forestry vehicles on lower grade tracks.

The actual test cases for #366 have been listed in my last post above.

@aoles aoles closed this as completed Dec 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐞 Erroneous behavior of the backend
Projects
None yet
Development

No branches or pull requests

2 participants