
Hello team, On Wed, 9 Dec 2009 14:04:34 +0200 Marko Mäkelä <marko.makela@iki.fi> wrote:
Hi Valentijn, Steve, Felix, all,
On Wed, Dec 09, 2009 at 12:57:34PM +0100, Valentijn Sessink wrote:
Hi,
I'm not sure I understand the mkgmap:tag stuff after all.
The "mkgmap:ferry" is an internal mkgmap tag, isn't it? I.e. it's a sort of intermediate tag, meaning the OSM input map should *never* have the mkgmap:whatever tags present?
The map data on the OpenStreetMap server should never have any mkgmap: tags set. That would be like "mapping for a renderer", a practice that is frowned upon.
I don't see that there's anything wrong with adding mkgmap: tags to the OSM database. After all, the wiki plainly says that you can put any tag you like on a node/way/relation. I have been tagging roads that look like flare roads but are not actually flare roads with mkgmap:flare-check. This stops mkgmap whining about them. I also use mkgmap:dir-check to tag roundabout segments that would otherwise show up as having the wrong direction. The presence of those tags doesn't have any affect on how the roads are rendered/edited. The only "crime" I have committed is that I have yet to document the tags. But those test disabling tags are quite different in concept to tags like mkgmap:unpaved or mkgmap:ferry. I agree that those tags do not need to be added to OSM data. Cheers, Mark