opening_hours is ignored for way about graphhopper HOT 5 CLOSED

I'm not a fan of "tagging for the router" but in this case I think opening "hours" is the wrong way to tag something like this and instead conditional restrictions should be used, which we support.

(Soon we'll ignore this for foot too, but will show this in the path details for GH Maps)

from graphhopper.

@karussell Thank you for pointing this out. Would access:conditional=no @ (Nov-Mar) be the correct way to tag a seasonal temporary pontoon bridge?

from graphhopper.

Or would bicycle=designated and foot=designated overwrite access:conditional=no?

In that case, would the following be correct?

access=no
foot:conditional=designated @ (Apr-Oct)
bicycle:conditional=designated @ (Apr-Oct)

from graphhopper.

The tagging would then look good IMO, yes ... now I just looked in the rather complex definition of opening_hours it seems that the current tagging Apr-Oct is not wrong and the evaluation tool just says "Please add a time selector to this rule". So not sure.

Now regarding conditional restrictions: for GraphHopper we currently only support yes or no (and not designated) but this is something that we can fix. Still, as I indicated before, even when we fix this, the road will always stay accessible and we'd only show a warning in GH Maps and you could block it via using a special custom model. The reasoning behind this behaviour is discussed in this issue.

Furthermore this would mean e.g. for openstreetmap.org:

1. there would be no warning (they do not show path details) and
2. there is no possibility to block the way (they do not have custom model support).

from graphhopper.

For now I close this issue as we do not plan to add opening_hours support.

from graphhopper.