
Hi Minko, I am not sure if I can help here. You use the precomp-sea option, that means that ways with natural=coastline are filtered in this way: a) the tag natural=coastline is removed from the original way b) a copy of the way with the same points is created. This new way has a Fake-Id like 4611686018427387908 and the tags natural=coastline,mkgmap:stylefilter=polyline This happens before style processing. Iam not sure why this is done. Gerd
Date: Sat, 1 Feb 2014 09:59:05 +0100 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] coastline boundaries
Anyone who can explain this behaviour? Are the tags on ways copied to boundary lines or are the boundaries treated independently?
I wrote:
Hi, How can I filter out all lines wich are part of boundaries that have a natural=coastline tag? For instance this way: http://www.openstreetmap.org/way/39862450
On my map I dont want to see the boundary lines along the coastlines, but in the style files I can't filter boundary=administrative & natural!=coastline. Somehow administrative boundaries are processed without the coastline tags.
Or can I use osmfilter to delete all ways that are tagged with natural=coastline AND are part of a boundary relation?
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev