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

Recognize conditional restrictions #374

Closed
karussell opened this issue Mar 18, 2015 · 9 comments
Closed

Recognize conditional restrictions #374

karussell opened this issue Mar 18, 2015 · 9 comments
Labels

Comments

@karussell
Copy link
Member

karussell commented Mar 18, 2015

Constructions should be avoided and assuming a daily re-import we should recognize the conditional tag including the date format defined in opening_hours.

First major part is implemented already in #621. Still missing:

@karussell karussell added the osm label Mar 18, 2015
@karussell karussell changed the title Recognize conditional dates Recognize conditional restrictions Mar 18, 2015
@karussell karussell added this to the 0.5 milestone Mar 25, 2015
@karussell karussell self-assigned this Jul 28, 2015
@karussell
Copy link
Member Author

@matkoniecz do you have a real world example for conditional restrictions used for constructions?

@karussell
Copy link
Member Author

So tagging the access with the 'conditional' trick seems to be done not that often. Only maxspeed:conditional is rather often (44K), access:conditional and vehicle:conditional combined is only 10K. So I vote to implement only these 3 schemes for now and only if they contain dates, not only times. Hourly imports are possible but not often done in practise, at least not now.

@karussell karussell removed this from the 0.5 milestone Jul 28, 2015
@karussell
Copy link
Member Author

I've created the date parsing logic in a separate branch but still will postpone this. Also see this project for a more generic opening hours parser

@ghost
Copy link

ghost commented Oct 11, 2015

@karussell
Copy link
Member Author

The PR by @boldtrn will be soon merged.

Should we support 'pure' opening hours too? Is this tagging schema kind of official for nodes? http://www.openstreetmap.org/node/2519644036

@karussell karussell removed their assignment Jan 19, 2016
@karussell karussell removed this from the 0.6 milestone Jan 19, 2016
@boldtrn
Copy link
Member

boldtrn commented May 20, 2016

We should definitely add the conditional access check for barriers. Here is a great example: https://graphhopper.com/maps/?point=46.491848%2C10.362371&point=46.49173%2C10.362607&locale=de-DE&vehicle=car&weighting=fastest&elevation=true&layer=Omniscale

The gate can be found here: http://www.openstreetmap.org/node/2689473341

´access:conditional no @ (Oct-Apr)´

@boldtrn
Copy link
Member

boldtrn commented Jan 10, 2018

Another case that would be nice to support is parsing of weeks like:

no @ week 1-5

An example way that uses this tagging scheme can be found here.

@mmuelder
Copy link

mmuelder commented Mar 2, 2018

are time (not date) based conditional restrictions supported yet?
access:conditional=no @ (09:00-17:00);
would be nice

@boldtrn
Copy link
Member

boldtrn commented Mar 4, 2018

are time (not date) based conditional restrictions supported yet?

No, this is not possible yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants