[OSM-talk-be] boundary names and my program
Jo
winfixit at gmail.com
Thu Nov 29 20:56:06 UTC 2012
>
> What Ben really means is "tagging for the editor". Tagging for the mapper
> should always be done, just as tagging for the data user.
>
> In the same way, you should tag for the rendering, but not for one
> specific renderer. I mean that you should use standard tags, usable by a
> broad range of renderers, and not try to get it pretty for Mapnik. If it
> isn't grass, you shouldn't tag it as grass just because you want a green
> colour on the map.
>
> In the same way, you shouldn't use a tag because one editor proposes or
> uses it. But you should use a tag that can be understood by most mappers
> (in a raw format), so tag for the mapper.
>
> The name vs note discussion is indeed about one editor only supporting
> note tags.
>
You mean one editor NOT supporting the use of note tags? JOSM supports both
name and note tags. Beyond that it allows to display names based on tags of
objects and even tags from their parents to identify them.
This is very practical to group all bicycle node routes together based on
the network they belong to. Or to show names of public transport route
relations composed of {operator} {ref} {from} {via} {to} and for bus stops
as {operator} {ref} {name} {route_ref}.
Jo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20121129/1f4c2392/attachment.htm>
More information about the Talk-be
mailing list