In my style I have the following: (highway=motorway | highway=trunk | highway=primary | highway=secondary | highway=tertiary | highway=motorway_link | highway=trunk_link | highway=primary_link | highway=secondary_link | highway=tertiary_link | highway=residential | highway=unclassified | highway=track | highway=bridleway | highway=cycleway | highway=footway | highway=path) & area=yes {delete highway} # delete unwanted areas I leave highway=service and highway=pedestrian as these are valid but the others are not. Regards, Mike -----Original Message----- From: DD8KQ [mailto:dd8kq@gmx.de] Sent: 13 September 2020 10:09 To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk>; Ticker Berkin <rwb-mkgmap@jagit.co.uk> Subject: Re: [mkgmap-dev] highway=unclassified & area=yes Hi Ticker just for me a hint, how can i ignore this in a style ? Am 13.09.2020 um 09:59 schrieb Ticker Berkin:
Hi all
Checking the GBR, I detect 1865 of these highway areas. They are done in a consistent and systematic way by a number of mappers.
I don't think it is a mapping error or an attempt to define the extent of a junction as per the proposed tagging highway=junction. Rather it is some option on the editing tool or some guidelines they are following that says to do this as a way of documenting the changes they have made within the junction area.
I'll ask some of the mappers why they are doing it.
These constructs can cause invalid routes to be calculated as well as confusing/irrelevant direction pop-ups and I now ignore them in my style.
Ticker
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- ##################################################### Viele Grüße und 73 de Manfred Haiduk, DD8KQ e-mail mhaiduk@t-online.de dd8kq@gmx.de #####################################################