Hey,
I think there are three things in play here:
- profile: recommended in the routing settings
sac_scale=demanding_alpine_hiking(and above), e.g. on this wayaccess:conditional=no@(Nov 01-Jun 14), e.g. on this way
Firstly, the hiking profile is by default using recommended settings. Have a look at this post that explains a bit about the differences.
Secondly, the hiking profile excludes the sac_scale= tags above T4. This is documented in our backend docs.
Thirdly, the seasonal access restrictions (here, some ways being closed from November onwards) are being respected at graph building time. This is a bit unclear and indeed not documented properly. I opened an issue regarding the documentation.
We are working on correctly parsing access:conditional-tags, so in the near future you could for example start sometime in August and get the route you’d expect.
I would guess that these factors lead to the road going completely around the area. If you manage to find a route that has none of the mentioned tags and is still not routed, please do report on that and we’ll help you find out why it happens.
Best regards