In my part of the world we have traffic zones called "School Zones" where all the streets in close proximity to a school are speed limited (usually to 40km/h) on School Days between hours of 0800-0930 and 1430-1600.

There appears to be a proposal underway to handle such situations Extended conditions for access tags

According to the proposal I would tag along the lines of: maxspeed = 60 (or whatever the "normal" speed limit is) maxspeed:(Mo-Fr 08:00-09:30, 14:30-16:00; PH off; SH off) = 40

When I've tried this, JOSM throws up a warning about whitespace in the key... and it makes me wonder about whether I should even be using it. I understand it's just a proposal and there seems to be some sensible objection to using values to make up a part of the key in such a way - which makes me reluctant to use it.

Is there a better way in which I should tag these restrictions for now?

Should I just tag with the default speed, and use a restriction=school_zone tag just for now, so that I might come back at some later date and retag these when there is an established syntax?

Thanks in advance.

asked 22 Aug '12, 18:57

wolftracker's gravatar image

accept rate: 33%

I have been using maxspeed:conditional=40 @ (Mo-Fr 08:00-09:30, 14:30-16:00;PH off;SH off) for tagging school zones in my area (QLD, Australia).

permanent link

answered 20 Sep '17, 07:34

David%20Dean's gravatar image

David Dean
accept rate: 22%

Yes, this is currently the best solution. Conditional restrictions are more and more common.

(20 Sep '17, 07:56) scai ♦

Updated answer:

Meanwhile conditional restrictions are widely in use. They are very flexible and allow to specify various access restrictions based on time (based on the opening_hours syntax), transportation mode, purpose of access and many more.

See David Dean's answer for a good example.

Old, outdated answer:

First, JOSM and other editors never know all tags in use and especially not every proposal because you can use any tags you like. Whitespaces are unusual for most keys but they can still be valid.

And you are right, these extended access conditions are just a proposal. Yet it seems that there is no better way of specifying such conditions at the moment. The access wiki page also lists date_on, date_off etc. which aren't much easier to use and which can't handle such complex conditions at all, especially when having multiple time ranges.

Furthermore, most current tools won't be able to parse any of those tags as they aren't widely in use and require a rather complex parser. Also most end devices like sat navs don't support such complex conditions anyway.

Still there is a valid reason to include them in OSM as they probably will become more important in the future. Even if the syntax changes, conditions like Mo-Fr 08:00-09:30, 14:30-16:00 can be converted to other formats with only little work. They are also easy to read for humans so that a simple tool can at least just display them without parsing.

So if you like, use this proposal to tag these conditions. Even if no current tool can handle them or even if some tools complain, it isn't wrong to enter them into the database as long as they provide useful information.

permanent link

answered 23 Aug '12, 07:40

scai's gravatar image

scai ♦
accept rate: 23%

edited 22 Sep '17, 10:12


Thank you very much. Your answer raises many good points. Given the uncertainty of the proposal, and the likely need to tweak the syntax, I'm now thinking the best interim solution is to use restriction=school_zone, and place the extra information about days and times either as a note= or a description=

(23 Aug '12, 18:24) wolftracker

The "Extended conditions for access tags" proposal is now obsolete and has been replaced with Conditional restrictions. Perhaps the accepted answer can be updated a bit?

(20 Sep '17, 15:17) Tordanik

@Tordanik I updated the answer, thanks for the hint.

(22 Sep '17, 10:13) scai ♦

I've taken the liberty of changing the accepted answer to the other one since everyone's now agreed on it - hope this is OK!

(22 Sep '17, 12:04) SomeoneElse ♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 22 Aug '12, 18:57

question was seen: 3,827 times

last updated: 22 Sep '17, 12:04

powered by OSQA