Talk:Conditional restrictions/Archive 1

Wrong time format

Resolved

The Key:opening_hours page specifies time as HH:MM, however, some examples on the page are using H:MM, this is probably not a good idea. -- Eckhart 16:52, 15 October 2012 (BST)

Fixed. Sloppiness from my side. Thanks for informing me. --polderrunner 19:27, 15 October 2012 (BST)

One-Time Conditional Restriction or Restriction Change?

The opening_hours syntax doesn't seem to provide a way to specify a year. This means it doesn't appear possible to specify a one-time closure period, or a feature that will permanently gain or lose restriction(s) on a given date. I think on_date and related tags could do that, though I can't seem to find the documentation for those. Will this be addressed? Vid the Kid 23:19, 2 November 2012 (UTC)

Key:opening_hours indeed does not mention how to tag a year or a one-time closure, it is intended for repeated events. I have no clear answers to your question. Start_date and end_date are probably not suitable as they indicate the begin or end of a feature such as construction or demolition dates of a building (not just a changed property). For a restriction that changes permanently on a specific date I would wait until that date and then map the new situation. For a temporary closure of less than a couple of months I prefer not to map it at all as many users don't update their data that frequently. Thus they may never see that closure in their map or they may use the wrong data long time after the closure has ended. A longer lasting closure (several months) should be mapped but remember to 'reopen' it when finished. --polderrunner 09:04, 3 November 2012 (UTC)

The proper solution would be to add years to the "specification", or even better write a formal "time domain" specification. Deducing rules from opening_hours examples is quite hard. -- Eckhart 12:37, 4 November 2012 (UTC)

Btw, I'm currently trying to formalize time domains, feedback welcome. -- Eckhart 14:00, 4 November 2012 (UTC)

Resolved: Opening hours now specify how one restrict it to a specific year Mateusz Konieczny (talk) 05:26, 23 September 2020 (UTC)

Weather conditions: distinct or not?

Resolved: "wet" and "snow" do not refer to weather, just the road surface.

We currently document road conditions on the main page (Conditional restrictions#Condition), but not weather-based conditions. Do we need them, or are keywords like "wet" to read as "wet roads, significantly affecting traction" as well as "when monsoon downpours significantly affect visibility"?

Tabulating precisely what is meant by each current condition keyword would be a good idea.

--achadwick (talk) 12:30, 18 June 2013 (UTC)

The "wet" condition clearly refers to wet road surface affecting traction, at least in western European countries. I think weather conditions like poor visibility are not relevant to OSM tagging as they don't normally concern individual roads but are globally defined in the traffic code of the particular country. --polderrunner (talk) 19:25, 18 June 2013 (UTC)

They might be signposted in some places; we cannot rule that out. For now, let's agree that "wet" and "snow" do not refer to weather, just the road surface.

If anyone needs to add weather conditions as distinct tests, I'd suggest keywords of raining, snowing, fog etc., and to discuss it here.

--achadwick (talk) 09:57, 20 June 2013 (UTC)

Mode of transport

I recently found some that some ways are tagged with conditional restrictions based on the mode of transport - somewhat like xxx:conditional=yyy@(bus). However, using modes of transport as a condition is not documented and is also unnecessarily complicated. In my opinion, it would be better to use the format xxx:bus=yyy. Any comments? --Biff (talk) 18:58, 28 June 2016 (UTC)

Using xxx:bus=yyy is indeed the documented way to do it, see Conditional_restrictions#Transportation_mode. Keep in mind that it's a special case for mode of transport, though, everything else needs to go into the value. --Tordanik 07:12, 29 June 2016 (UTC)

Resolved: Mateusz Konieczny (talk) 05:23, 23 September 2020 (UTC)

Use of parenthesis

I see a lot of parenthesis used in the examples, yet the documentation does not mention them even once. When are they required? When not? What should they contain? --Pbb (talk) 22:37, 6 November 2016 (UTC)

Hi Pbb, the documentation does mention them:

• Time and date: Use the standard syntax of the value * of the opening_hours=* tag. If that value includes semicolons (";"), that condition must be enclosed by brackets, e.g. (Mo-Fr 07:00-19:00), (sunrise-sunset) or (Jan-Mar). (The examples don't contain a semicolon???)
• Except for very simple conditions like "wet" or "Su" it is recommended to enclose the condition in brackets. (Does "recommended" mean that they are optional?)

So the paranthesis are only needed around a condition which contains one or more semicolons because otherwise each semicolon would indicate the start of a new condition. The text should be improved to provide a clear requirement for this, the fuzzy recommendation is not helpful. It would also be better to use the precise terms for brackets "[ ]" and paranthesis "( )". --Biff (talk) 23:06, 6 November 2016 (UTC)

Thanks, I didn't realize brackets could also mean parenteses! --Pbb (talk) 22:09, 8 November 2016 (UTC)

Resolved: Mateusz Konieczny (talk) 05:23, 23 September 2020 (UTC)