Re: [mkgmap-dev] Overview map

2017-03-12 Thread Gerd Petermann
Hi Mike, I don't see a need to change the syntax for the levels statements, but if you have a patch for the docu please post it. Gerd Von: mkgmap-dev im Auftrag von Mike Baggaley Gesendet:

Re: [mkgmap-dev] Splitter multiple input files

2017-03-12 Thread Gerd Petermann
Hi Mike, you can use mutiple input files but with some limitations. In short, if you want to use --keep-complete it is better to merge the files first. Gerd Von: mkgmap-dev im Auftrag von Mike Baggaley

[mkgmap-dev] Splitter multiple input files

2017-03-12 Thread Mike Baggaley
Quick question - can splitter accept multiple input files? I'm currently using osmconvert to merge data into a single file before passing to splitter, but wondered whether I am unnecessarily doing this merge. Thanks, Mike ___ mkgmap-dev mailing list

Re: [mkgmap-dev] Stylefile : Rule for delete all proposed features ?

2017-03-12 Thread Thomas Morgenstern
okay, die allgemeine Regel ist nicht erforderlich. es reicht, wenn ich die Regel für konkrete Objecte anwende. Und konkret bin ich bisher nur auf building und amenity=parking gestoßen. mfg thomas Am 12.03.2017 um 10:30 schrieb Gerd Petermann: Hallo Thomas, das macht aus meiner Sicht

Re: [mkgmap-dev] Stylefile : Rule for delete all proposed features ?

2017-03-12 Thread Gerd Petermann
Hallo Thomas, das macht aus meiner Sicht keinen Sinn. Nimm mein Beispiel http://www.openstreetmap.org/way/58422569 Das Gebäude existiert, du willst es aber nicht rendern, weil jemand vorhat, darin einen Baumarkt zu eröffnen. Ich würde verstehen, wenn Du das tag shop=proposed automatisch löschen

Re: [mkgmap-dev] Stylefile : Rule for delete all proposed features ?

2017-03-12 Thread Thomas Morgenstern
Hallo, ich habe polygone gefunden mit dem tag =proposed. Und diese will ich nicht rendern. Ich will eine allgemeine stylerule in mein Stylefile einbauen, wo alle objecte mit =proposed gelöscht bzw. nicht gerendert werden. Mit einzelnen lines ist das kein Problem . z.B. highway=proposed {delete

Re: [mkgmap-dev] Stylefile : Rule for delete all proposed features ?

2017-03-12 Thread Gerd Petermann
Hi Thomas, I still don't understand how that would work. My first example probably wasn't good because the tag key sidewalk:both is never evaluated with the default style. Consider also this way http://www.openstreetmap.org/way/323342627 with highway=residential surface=proposed My

Re: [mkgmap-dev] Stylefile : Rule for delete all proposed features ?

2017-03-12 Thread Thomas Morgenstern
I want not drop before styleproccessing. For example : the object 346 400 898 has the tag 'building=proposed' . I want drop the whole objekt. Near by are another objects (amenity=parking ; parking=proposed). The obcekt is in tenerife, near Adeje. I want not render generelly all objects, which

Re: [mkgmap-dev] Stylefile : Rule for delete all proposed features ?

2017-03-12 Thread Gerd Petermann
Hi Thomas, that is not possible with the current version. Not sure what you want to achive. If a way has the tags highway=residential,sidewalk:both=proposed,name=A-road do you want to drop the single tag sidewalk:both=proposed before style processing or do you want to drop the complete way ?

[mkgmap-dev] Stylefile : Rule for delete all proposed features ?

2017-03-12 Thread Thomas Morgenstern
Hi , can someone give me a hint for a proper rule in stylefile . I want delete all objects (line, polygon, poi) which have tag = proposed. I do not want to write individuall rules for each object ; example : parking=propose {delete parking} separate. thanks thomas