Ways tagged with hgv:destination seems to not being taken into consideration when routing for HGV, below is an example. The alternative route (gray) should be the correct route as it is tagged with hgv:designated. Is there any reason why the engine prefers this route over the gray one? There was a closed issue on Github that was supposed to fix this issue but seems like it’s still happening.
ORS Maps
Hey,
I am a bit unsure about what seems to be the issue here.
The access tag hgv:destination is meant to state that HGVs may only use a way when travelling to or from a location, not when just driving through. In the US, this would be “local traffic only”.
The access tag hgv:designated is meant to state that a way is designated to HGV usage and no other traffic is allowed on the route.
Could you please specify what tag you are talking about?
If there is a dedicated OSM way that is tagged in a certain way where you think the openrouteservice should behave differently, would you please link the OSM way directly?
From a large overview-screenshot, it is rather hard to deduct what way is being talked about.
Could you, for reference, also link the closed issue?
Thanks a lot 
Sorry for the confusion. What I meant was that ORS is taking a route that does not allow through traffic (or like you said, only allows local traffic), which is being tagged with hgv:destination pretty much the whole way through i.e. Way: Larry McDonald Memorial Highway (359612958) | OpenStreetMap. The alternative route (gray one) is the correct route in this case, since it’s tagged with hgv:designated.
This is the closed issue I was referencing Hgv routing does not respect `destination` access restriction · Issue #525 · GIScience/openrouteservice