Mapping parking Restrictions in VN

Help and support
, ,
1

Hi,
I’ve been seeing theese type of conditional parking restrictions signs in Vietnam and i’m not sure what is the correct value for this.
For the no parking on even days know it is like the one below:
parking:side:restriction:conditional=no_parking @ (Jan 2-30/2, Feb 2-28/2, Mar 2-30/2, Apr 2-30/2, May 2-30/2, Jun 2-30/2, Jul 2-30/2, Aug 2-30/2, Sep 2-30/2, Oct 2-30/2, Nov 2-30/2, Dec 2-30/2)
But for the combination with the time interval, how should the value look like? The time interval adds an extra conditional, like "you are not allowed to park here on even days, from Monday to Sunday between 06:00-21:00)
Many thanks!

image
image344×494 51.7 KB

10.787097974942409, 106.63492589876624

2

This should do the trick Jan 2-30/2: 06:00-21:00; Feb 2-28/2: 06:00-21:00; Mar 2-30/2: 06:00-21:00; Apr 2-30/2: 06:00-21:00; May 2-30/2: 06:00-21:00; Jun 2-30/2: 06:00-21:00; Jul 2-30/2: 06:00-21:00; Aug 2-30/2: 06:00-21:00; Sep 2-30/2: 06:00-21:00; Oct 2-30/2: 06:00-21:00; Nov 2-30/2: 06:00-21:00; Dec 2-30/2: 06:00-21:00. Evaluation tool demo

3

P.S. Not sure but couldn’t parking:<side>:restriction:conditional=no_parking @ not be done as parking:<side>:conditional= no @

4

The maping schema was updated for street parking, this is the new one. Also here the tag is the same in the examples

5

Awesome, thank you, and if the condition is for example from Monday to Friday, this will need to be add it for each month right?

6

As each month will be treated as its "own rule’ all the sub rules like hours or days needs to be repeated yes. I only had a quick look but I’ve not seen a way to combine the months. So it should be something like <month> 2-30/2: Mo-Fr 06:00-21:00

7

Nice, many thanks! Really appreciate it

8

Should be possible to avoid time repetition same way you would do it for week daysMo,Tue 10:00-18:00
Jan 2-30/2, Feb 2-28/2, Mar 2-30/2 06:00-21:00

9

It took me a while to understand it. It was easier for me to understand when written as Jan 02-30/2,Feb 02-28/2,Mar 02-30/2 06:00-21:00[1] (i.e. without the space after the comma).

The evaluation tool shows it as working.

Except there is something fishy going on with Feb and then only when it is not a leap year. But then again, not always; sometimes it works :frowning:

This also happens with the solution I came up with in a previous message.
And when looking at that in the evaluation tool again, I noticed that I have overlooked[2] that that solution is too long to be used in OSM.

  1. I have also added a leading 0 for one digit mont days conform the syntax
    md monthday, always two digits number in the format . See: wiki: opening_hours - Syntax ↩︎

  2. The tool warns for it but I failed to notice the warning :smiling_face: ↩︎