logo separator

[mkgmap-dev] [PATCH v1] grok unpavedness

From Marko Mäkelä marko.makela at iki.fi on Wed Dec 9 12:04:34 GMT 2009

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.

The mkgmap: tags can be added by mkgmap itself (for example, when a
style file contains { add mkgmap:whatever=whatever }) or to the *.osm
input files by a custom preprocessor.

> As far as I read Steve Hosgood's remarks, it looks like anyone could be
> tempted into adding mkgmap:ferry tags to OSM, but that sounds at least a
> bit odd to me. Or don't I understand Steve's remarks here?

Steve, was this just a misunderstanding?  As of r1425, the mkgmap default
line style adds mkgmap:unpaved and mkgmap:ferry attributes.  I see that
Felix (extremecarver) suggested some further attributes that indicate
unpavedness.  I will probably incorporate those to the default style.

Best regards,


More information about the mkgmap-dev mailing list