<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 5/8/2019 2:17 PM, Mateusz Konieczny
wrote:<br>
</div>
<blockquote type="cite" cite="mid:LeNeUGQ--3-1@tutanota.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div style="16px" text-align="left">opening_date works well for
road under construction, it is not fitting for road<br>
</div>
<div style="16px" text-align="left">that is not closed but some
things like oneway status, lanes are modified<br>
</div>
<div style="16px" text-align="left"><br>
</div>
</blockquote>
<p>The wiki for conditional restrictions gives the following
examples:</p>
<p> - oneway:conditional=yes @ Su described as "Street is oneway on
Sundays"<br>
- motor_vehicle:conditional=no @ (2018 May 22-2018 Oct 7)
described as "Section of road is closed for motor vehicles for a
few months (for construction). Navigation after the end date
should work even for maps created in the meantime."<br>
</p>
<p>In my own mapping I have a street that's normally twoway but has
been oneway due to construction for over a year, with no firm end
date. Following the wiki's examples I could tag it as
"oneway:conditional=yes @ (2019 Jan 1-2020 Jan 1)" and monitor the
situation, updating the date range as necessary and eventually
removing the tag. But my understanding of best practices for
conditional tagging is to tag the most restrictive value first,
and add the less restrictive value to the conditional clause.</p>
<p>For now, because I don't actually expect any data consumers to
parse the conditional, I simply have it tagged as oneway=yes with
a fixme. I suppose there'd be no harm in adding a
"oneway:conditional=no @ (2020 Jan 1-2999 Jan 1)" and updating the
start of that date range as new info is available... but it seems
a little silly.<br>
</p>
<p>Jason<br>
</p>
</body>
</html>