Make conditional access restrictions configurable #2863
Conversation
…er those tags for e.g. car (constructions)
karussell
changed the title
|
Hello, is there any timeline when this will be released? I supposed this will be included in 9.0, I just hoped to know when will 9.0 be available. |
|
There is no timeline for this PR and it might or might not included in 9.0 but you can always try this development branch out and give feedback :) (However, 9.0 will be released in March or April.) |
|
I do not see the conditional here, all the way "Type: null" - https://graphhopper.com/maps/?point=47.307968%2C11.519214&point=47.338586%2C11.507562&profile=hike&layer=TF+Outdoors - It routes over a via ferrata that is closed in winter. C.f. #1326 |
|
We need to make this information better accessible in the UI: graphhopper/graphhopper-maps#378 and maybe provide a way to easily exclude them with |
|
It is now shown (refresh necessary). Multiple clicks on the icon will loop through all the conditional restrictions.
The next step would be to add a button to exclude these obstacles but this is not that simple but will try to find a way. |
|
I read "refresh necessary" and did not see a change. Then I read "click on the icon" and now I see. It would have never appeared to me that the icons can be clicked. From A user PoV I would be fine with being told, a bit more immediately visible than now - perhaps the section pre-clicked? I would not expect a magic button to solve the issue. Some routers offer alternatives in all cases, maybe suggest to tune by placing a via close by - What do I know? PS - In this very case: I think, graphhopper should just drop any "highway=via_ferrata" when ingesting OSM data. Much as OSM-Carto does or thunderforest does. These highways are of no use neither for the foot not the hike profile. |
Will think about how to improve this. I would prefer to avoid "pre-clicked" due to the "clutter" it might add.
Ok, will skip via_ferrata and then also close #1326. |
This PR removes the conditional blocking access from the vehicle parsers. I.e. after this change you need to add e.g. car_road_access_conditional == NO into a custom model to still consider temporary restrictions due to constructions.
This PR also:
access_conditional. (see also Implementation for issue2477 seasonal restrictions #2860)I added some more path details to the Measurement so the response time is expected to be a bit slower for this single test.
Here is an OSM way with
vehicle:conditional=no @ (Nov 1-Mar 31)for testing purposes. GH Maps link.On GraphHopper Maps we now show a route hint for outdoor profiles and in the details widget the exact values are shown: