[OSM-newbies] Highway=stile vs Barrier=stile

[Dave Stubbs]

2009/1/2 xeen <aka.xeen at gmail.com>:
> Never tag for the renders.


Feel free to tag for the renderers.

When people talk about not tagging for the renderers, what they
generally mean is don't mis-tag just to get something rendered. ie:
don't tag a marsh as a park because the renderer just happens to paint
it the green colour you want.
This is not the case here: highway=stile is a completely legitimate
way of tagging a stile.
Continue to use highway=stile if you wish... the JOSM editor is
applying a set of rendering rules just like the web maps are.


> barrier=stile is the correct one, and sooner or later Osmarender and
> Mapnik will catch up. JOSM shows this "error icon" because it deems
> highway=xyz to be a way or at least have some extent (i.e. highways
> can't be nodes).

The tag was always highway=stile. There's thousands in existence. It
works perfectly well. There was a wiki discussion where barriers were
thought about and the people on that discussion decided to rename
stiles as barrier=stile to make it more consistent. There's no
compulsion for anybody to agree with this, and also there's no reason
we can't use both.

So yes, eventually I'm sure the t at h and main osm tiles will follow.


> Unless the stile is like 10m long, it doesn't make sense to draw it as
> a way – and it would conflict with the classification of the road. So,
> if you desperately want that icon in Osmarender, add both tags; if you
> want to tag correctly, use only barrier=stile and wait for the renders
> to catch up.

As I explained above this interpretation is wrong.

There's now two tags for stiles. JOSM has a bug in that it doesn't
recognise one which it should know about, and the web maps haven't
been updated with the newly introduced tag.

Dave