If making an u-turn seems allowed and possible I'd draw one road only - cars traveling in opposing direction do then meet with just a dashed line in between. If there weren't a car lane on the tram tracks, I'd probably go for separated directions. Alv 21:38, 13 September 2008 (UTC)

I would make it two ways, of different types: one a roadway, the other a railway. Each could have a tag indicating the existence of a coincident way of a different type, but keeping them separate makes it easy to add specific attributes to each as necessary. For example, separate names: The road may have one name but the railway another. How can you assign two names to the same way? Or any other attributes that roads and railways have in common?

Keeping different types of ways separate also makes it easy to render a map showing only certain types of ways, railways being an example. (--Stokestack 08:29, 20 February 2009 (UTC))

Since this is only a parsing problem, it should be fixed by the database-parser and not by workaround s in the database. If a tram line is exactly on the read lane, it should be one way. If that can not be tagged correctly, invent better tags! --Phobie 02:27, 12 May 2009 (UTC)

If the tram rails were not there, the street would be tagged as a single way since there is no physical barrier between lanes (in this case not even a solid line) - so it is different from the primary example. Adding the tram, either add a railway=tram or draw a separate way, sharing the same nodes. Which of the two is better is by no means obvious: a single way means less maintenance work, fewer objects in the database but also possible confusion about tags which apply only to one of the two. And even if you think the tag you're adding clearly applies to only one - that may change as tags evolve. Think of a a one-way street (for cars) where the tram passes in both directions: as of today (correct me if I'm wrong) the oneway tag commonly applies to highways, not to railways, so highway=secondaryrailway=tramoneway=yes seems OK. But what if tomorrow we decide to use oneway also for railways? Conclusion: a single way for both is OK as long as all tags clearly apply to both; if there is a chance that tags might become confusing, draw two ways.

As for the "different name" example mentioned above: I consider it bad practice to tag railways with names representing the train/tram lines - I see it frequently but I maintain that this information is better kept in relations and represented by renderers aware of those (such as Öpnvkarte or OpenStreetBrowser). Therefore no "name clashes" between streets and tram lines should arise. --Stanton 17:55, 14 December 2010 (UTC)

Last example

The caption of the image says A footway, apparently not for bicycles. I don't agree, just because there is a cycle barrier it does not mean that cycles are not allowed. It is no problem to pass a cycle barrier on the bicycle, but it slows bicyclist down and prevents them from rushing on the street.

I therefore have changed the example. --Dwi Secundus 15:27, 13 September 2008 (UTC)