[Tagging] improve tagging of traffic_calming

[John Willis]

> On Nov 21, 2015, at 3:31 AM, Philip Barnes <phil at trigpoint.me.uk> wrote:
> 
> Most traffic calming features are not pedestrian crossings.
> 
> Where traffic_calming is not a pedestrian crossing then
> highway=traffic_calming is the prefered way of tagging.

+1

If I read this discussion correctly, 
We're stuck on two issues:

1) the lack of highway=traffic calming on nodes where traffic_calming=* exists. 

- let's add highway=traffic calming. 

2) on nodes which are some form of ped crossing, what should take priority? 

- A footway marked as a crosswalk(zebra) is inherently a "traffic calming" feature - but it is first and foremost a crossing. Apparently a highway=node is preferred where the footway shares a node with the road's way. 

Highway=traffic_calming is for physical features that cannot be ignored. Paint can easily be ignored (ask any Californian about stop sign limit lines!) - so if it is just a crosswalk, then don't add the traffic_calming tag. If the crosswalk also has another feature (table, pinch point), then add those to a segment of the way that crosses the crosswalk (table) or a node immediately in front of the crosswalk node (for pinch point bollards) as the pinch affects the road but not the crosswalk. 

Barrier=* has several features that can be considered a barrier to some modes of transportation and has a traffic calming affect to others - bollards stop cars and slow cyclists, cycle barriers stop motor cycles and slow cyclists, etc - but traffic calming seems to be very centered on motorized vehicle traffic on roads, not sidewalks. 

Javbw