logo separator

[mkgmap-dev] highway=razed

From Gerd Petermann gpetermann_muenchen at hotmail.com on Fri Sep 18 08:08:57 BST 2015

Hi Andrzej,

I think 1st I wanted to point out that the "mop up" rule
should be removed, it is likely to produce wrong routing.
I found it because in my area a motorway replaced a primary
road and that primary road is now mapped with highway=razed,
e.g. here

It also mops up all kinds of typos and undocumented tagging, e.g.

Regarding area=yes:
I understand that we don't want to add those highways to NOD,
at least not until mkgmap is able to calculate direkt ways through
an area. On the other hand, the rule 
railway=platform [0x16 road_class=0 road_speed=0 resolution 23]
is likely to do that. I guess it is okay here because we make sure that
railway=platform is pedestrian only?


>  > Most of these ways are areas, but don't have the area=yes tag.
>  > I am not sure why the "mop up" rule would ignore them when the
>  > area=yes tag exists.
> I'm not sure if I understand your problem, so following are my 
> observations only.
> Area described as a highway could be a multipolygon, without are=yes 
> tag. Myltipolygon is area by default. I add following line to my style:
> highway=* & mkgmap:mp_created=true { add area=yes; }
> Highway area drown as a line clutters map and IMHO should be avoided. 
> Usually there exist corresponding highway line too.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20150918/e15c19d4/attachment-0001.html>

More information about the mkgmap-dev mailing list