[Tagging] kerb regulations: moving towards a tagging schema?

Emily Eros emily.eros at gmail.com
Fri Jun 21 16:38:20 UTC 2019

Hi Graeme,

Good question. So cities generally post what is restricted, rather than
what is explicitly allowed. For example, a "paid parking" rule is there to
tell you that you *can't* park unless you pay, and a "parking 2-4pm" zone
is there to tell you that you *can't* park outside of those hours. Some
restrictions are easier to map in the affirmative (e.g. parking zone, but
only for motorcycles), and this implies that no other vehicle or user class
can park there. Other restrictions are easier to map in the negative (e.g.
no parking, applies to everyone if unspecified). Either way, there is an
underlying understanding that curbspace has a "default" status, and signs
denote exceptions to that status. I suppose you could map all allowed uses
of every street segment, but it would be far simpler to just map the
exceptions. In the same way, I've never seen a city signpost something to
the effect of "parking allowed for everyone at all hours". I'm sure there
is probably the odd edge case, but signs and paint are expensive to
create/maintain, so there are good reasons why cities don't do this.

In cities in Canada and the US where I've lived, the default is open;
parking, standing, or loading of all modes and vehicles is permitted unless
posted otherwise. But I wouldn't be surprised if other jurisdictions are
closed by default. To handle those, a polygon could be created around these
areas (or an existing boundary could be used) and a relation could be
created to establish them as exceptions with a different default. The asset
tagging scheme would still work the same way, though - the same tags (e.g.
parking zone, applies to everyone) can be used to denote exceptions where
certain activities are allowed.

To answer questions like, "Where can I park/load/stand my vehicle?", a
rules engine is necessary to consider the default, the time period in
question, and the user/mode/vehicle in question. That's not specific to the
curb - you'd need the same sort of thing to use OSM to answer questions
like, "Where is the nearest open pharmacy at 9pm?"

For for on what tagging could look like, specific examples of how we handle
activity rules in the CurbLR spec are available on GitHub:
(I haven't written up what this would look like in OSM yet since it seems
premature - I wanted to first share the general approach and see what the
community thinks about point-based asset mapping.)

On Thu, Jun 20, 2019 at 10:04 PM Graeme Fitzpatrick <graemefitz1 at gmail.com>

> On Fri, 21 Jun 2019 at 12:43, Emily Eros <emily.eros at gmail.com> wrote:
>> I'd love to hear from people about what they think about this as a
>> general approach.
> Wow Emily, that's a mighty task you've set yourself!
> How will it work when there are no signposts - eg residential streets
> where parking is allowed but nothing to indicate it?
> Thanks
> Graeme
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20190621/52660008/attachment-0001.html>

More information about the Tagging mailing list