On Sun, Aug 10, 2014 at 06:14:24PM +0200, Colin Smale wrote: > > > It is neither constructed with the intention of calming traffic, nor is > it intended as any kind of barrier (a bridge is usually exactly the > opposite!) Let us not be afraid of using a different tag for what is > clearly a different attribute.
without clear speed limits or hazzard signs it is just a very abstract danger of which plenty are more evil than a humpback bridge but not tagged in any way.. generations of drivers did drive there. We don't tag narrow winding mountain roads with special attributes, nor do we expect routing software to deduce that wisdom from road geometry? Sometimes I wish we would have something like key:reasonable_max_speed but we don't. So either bridge=humpback is a substitute for key:reasonable_max_speed - than we should think about that - or it is more an optical thing which could be handled within bridge:structure? On Sun, Aug 10, 2014 at 08:24:05PM +0400, Никита wrote: > Yeah, traffic_calming was bad idea too, we use it for artificial objects > with purpose of calming traffic. > > Back to the topic: "a bridge requiring driving speed to be reduced due to > the vertical profile (i.e. not because it is narrow, or some other > attribute)". very similar danger situation like hazard=dip, some railway crossings and any number of similar situations. Would it be worth to have an abstraction for that? Richard _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
