[Tagging] Comparison of tag support: Mapnik, Osmarender, Potlatch, JOSM, Kosmos, Map Features (wiki)

Pieren pieren3 at gmail.com
Mon Dec 14 10:02:51 GMT 2009


On Mon, Dec 14, 2009 at 10:05 AM, Steve Bennett <stevagewp at gmail.com> wrote:
>>> It might be better to think in terms of "core" tags and "specialist"
>>> tags or something. If something is core, we expect all decent
>>> renderers to render it.
>>
>> How do you enforce this with people doing the renderer maintenance in
>> their spare time? ;-)
>
> I didn't say enforce! All I'm saying, is you give a list of
> priorities, like "all renderers should support these tags". Just like
> when you "saw what the other renderers are doing", I think programmers
> would be inspired to implement that kind of list. And obviously
> certain kinds of tags can be implemented very easily, just with a
> colour or whatever, while others are harder.
>

What is "core" and what is not ? What is in the wiki Map Features ?
But anyone can add his tag, approved by 10 or 12 voters in the Map
Features...
You cannot fix priorities for other people creating the data or other
applications using the data. What is the "core" for OpenCycleMap is
not the same as the "core" for OpenWaterwayMap, OpenCrimeMap,
OpenHikingMap, OpenShopMap, OpenTourismMap, OpenSchoolMap, etc...
You are really expecting too much from the "rendering" side of the
project. What we need is a clear definition of the tags and this is
done by searching a consensus on the wiki and on this list and we see
if we succeed or fail with the statistics. If we don't have a common
definition of the tags, we end up with different rendering rules and
even worst, with different tagging presets in the editors.
So, what we have to do first, if we have to fix priorities, is to
improve the definitions of the tags, avoid duplicates or changes in
the meaning of the tags one year or two after their creation (e.g. the
other thread about cycleway on this ML).

Pieren.




More information about the Tagging mailing list