<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Henning,<br><br>please try r332:<br><a href="http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&path=%2F&rev=332" target="_blank">http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&path=%2F&rev=332</a><br><br>The osm ways must have a tag name and a tag mapid.<br>This is how it works:<br>1) read the osm ways, create one polygon for each OSM way<br>2) combine all polygons (this may create "islands")<br>3) use this combined polygon as if it was read with the --polygon-file option<br>4) split<br>5) for each named polygon, create the files <br><name>-templates.args<br><name>-areas.poly<br>optional: <name>-<kml-file>.kml<br><br>Attached is your examle and the output files created for an older Europe densities.txt.<br><br>Gerd<br><br><div>Date: Sun, 11 May 2014 12:24:49 +0200<br>From: osm@aighes.de<br>To: mkgmap-dev@lists.mkgmap.org.uk<br>Subject: Re: [mkgmap-dev] splitter removes multipolygon-tags<br><br><pre>-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br> <br>Hi Gerd,<br> <br>I created a example based on my map of Germany (highway=motorway) and<br>Alps (highway=primary).<br> <br>My thoughts are, that splitter creates based on these two polygons<br>three temporary polygons. One containing area only touched by Germany<br>(landuse=forest), one containing area only touched by Alps<br>(landuse=farmland) and one containing area touched by both<br>(landuse=military).<br> <br>The result will be three list of tiles. The naming of tiles isn't<br>important.<br> <br>Also splitter should output two templates.args (for each input-poly<br>one), as you already wrote. The file for Germany should contain all<br>tiles in forest-area and military-area, the file for Alps military and<br>farmland.<br> <br>Henning<br> <br>Am 11.05.2014 11:25, schrieb Gerd Petermann:<br>> Hi Henning,<br>> <br>> don't worry, splitter already contains a lot of code that is only<br>> needed for the handling of overlapping tiles. I am not sure if I<br>> got it right what you mean in your example. Would it be okay to<br>> calculate the tiles for Germany and write them, and in a final pass<br>> find all tiles which overlap the polygon for Hessen and copy those<br>> with the mapids for Hessen? Or could splitter just create a<br>> templates.Hessen.args containing something like mapname: 10000001 <br>> input-file: 110000092.o5m mapname: 10000002 input-file:<br>> 110000093.o5m mapname: 10000003 input-file: 110000094.o5m mapname:<br>> 10000004 input-file: 110000098.o5m mapname: 10000005 input-file:<br>> 110000112.o5m<br>> <br>> This would safe some GB disk IO.<br>> <br>> Gerd<br>> <br>> <br>>> Date: Sun, 11 May 2014 11:15:29 +0200 From: osm@aighes.de To:<br>>> mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] splitter<br>>> removes multipolygon-tags<br>>> <br>> Hi Gerd,<br>> <br>> the flexibility is, that I actually can just add new areas to my <br>> areas.list and don't have to care about anything. If mkgmap throws<br>> out a warning about too many nodes in a tile, I let splitter create<br>> a new areas.list for the region and I can continue.<br>> <br>> In the new workflow I then have to adjust the script, which copies<br>> the multiple used tiles.<br>> <br>> It would be very helpful, if splitter can do the copying of tiles.<br>> <br>> Splitter detects overlapping areas in areas.list and handles these <br>> regions as a own polygon and is writing tiles for each map, which <br>> touches the overlapping area.<br>> <br>> So for example, if a split a map of Hessen (10000000) and a map of <br>> Germany (11000000), splitter will use a polygon of Germany with a<br>> hole at the place where Hessen-poly-file has a coverage and<br>> Hessen-polygon.<br>> <br>> So the resulting areas.list could looks like:<br>> <br>> 11000001;10000001: .... 11000002: ....<br>> <br>> So splitter is able to write the data of a tile in Hessen to the<br>> map of Hessen and to the map of Germany.<br>> <br>> Maybe such a system is a better and more robust solution then<br>> handling overlapping tiles. But I don't want to made you code that<br>> only for me.<br>> <br>> Henning<br>> <br>> <br>> Am 11.05.2014 10:49, schrieb Gerd Petermann:<br>>>>> Hi Henning,<br>>>>> <br>>>>> can you describe what flexibility you are loosing? Could<br>>>>> splitter be improved ?<br>>>>> <br>>>>> Gerd<br>>>>> <br>>>>>> Date: Sun, 11 May 2014 10:46:31 +0200 From: osm@aighes.de<br>>>>>> To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re:<br>>>>>> [mkgmap-dev] splitter removes multipolygon-tags<br>>>>>> <br>>>>> Hi Gerd, this is, what I'm thinking about to do, but on the<br>>>>> other hand I'm loosing the actual flexibility. I think I will<br>>>>> give it a try and will see, how it works.<br>>>>> <br>>>>> Henning<br>>>>> <br>>>>> Am 11.05.2014 08:24, schrieb Gerd Petermann:<br>>>>>>>> Hi Henning,<br>>>>>>>> <br>>>>>>>> If you don't mind to have a map of e.g. Germany which<br>>>>>>>> also contains small parts of other areas, I think the<br>>>>>>>> fastest way is this:<br>>>>>>>> <br>>>>>>>> combine your *.poly files so that you have one<br>>>>>>>> henning.poly that contains the areas for which you want<br>>>>>>>> to create maps. Execute splitter with<br>>>>>>>> --polygon-file=henning.poly --max-nodes=...<br>>>>>>>> --stop-after=split --write-kml=splitter.kml planet.o5m<br>>>>>>>> <br>>>>>>>> If you have an actual densitites_out.txt for planet,<br>>>>>>>> you can also copy it to the working directory and<br>>>>>>>> rename it to densities.txt. Splitter will use this file<br>>>>>>>> instead of reading the planet.o5m, and the program<br>>>>>>>> finishes within seconds.<br>>>>>>>> <br>>>>>>>> As a result you have a kml file and an areas.list. The<br>>>>>>>> next step would be to re-combine the areas so that they<br>>>>>>>> build the maps that you want to create.<br>>>>>>>> <br>>>>>>>> If you need the same tile for two maps, but with<br>>>>>>>> different mapids, I suggest to copy the output file of<br>>>>>>>> splitter. Maybe a small script is needed to perform<br>>>>>>>> this step.<br>>>>>>>> <br>>>>>>>> Gerd<br>>>>>>>> <br>>>>>>>> <br>>>>>>>> <br>>>>>>>> <br>>>>>>>>> Date: Sat, 10 May 2014 20:31:51 +0200 From:<br>>>>>>>>> osm@aighes.de To: mkgmap-dev@lists.mkgmap.org.uk<br>>>>>>>>> Subject: Re: [mkgmap-dev] splitter removes<br>>>>>>>>> multipolygon-tags<br>>>>>>>>> <br>>>>>>>>> Hi Gerd, ok, so my next step will be to optimize my<br>>>>>>>>> tiles.<br>>>>>>>>> <br>>>>>>>>> Henning<br>>>>>>>>> <br>>>>>>>>> Am 10.05.2014 17:27, schrieb GerdP:<br>>>>>>>>>> Hi Henning,<br>>>>>>>>>> <br>>>>>>>>>> I did not try what happens when 5 tiles overlap the<br>>>>>>>>>> same point, but it should work. As I said, you<br>>>>>>>>>> should try to avoid that, as each tile will require<br>>>>>>>>>> the complete reading of the input file.<br>>>>>>>>>> <br>>>>>>>>>> Gerd<br>>>>>>>>> <br>>>>>>>>> _______________________________________________<br>>>>>>>>> mkgmap-dev mailing list<br>>>>>>>>> mkgmap-dev@lists.mkgmap.org.uk <br>>>>>>>>> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>>>>>>>> <br>>>>>>>> <br>>>>>>>> <br>>>>>>>> <br>>>>>>>> _______________________________________________<br>>>>>>>> mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<br>>>>>>>> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>>>>>>>> <br>>>>>> <br>>>>>> _______________________________________________ mkgmap-dev <br>>>>>> mailing list mkgmap-dev@lists.mkgmap.org.uk <br>>>>>> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>>>>> <br>>>>> <br>>>>> <br>>>>> <br>>>>> _______________________________________________ mkgmap-dev<br>>>>> mailing list mkgmap-dev@lists.mkgmap.org.uk <br>>>>> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>>>>> <br>>> <br>>> _______________________________________________ mkgmap-dev<br>>> mailing list mkgmap-dev@lists.mkgmap.org.uk <br>>> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>> <br>> <br>> <br>> <br>> _______________________________________________ mkgmap-dev mailing<br>> list mkgmap-dev@lists.mkgmap.org.uk <br>> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>> <br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.14 (GNU/Linux)<br> <br>iQEcBAEBAgAGBQJTb0/wAAoJEKXggIeC16WPE2oIAI9b1fXZQPA81MWPNI+07rYG<br>6AaLJVuen+btCTGJ/PUtePUGhkeV9zXXuQveDo4JUxACMpWOfGjgsDCbzRiSH3pH<br>mSCgL4UaCMMDT9XIePiOIigwOfzzh9oQkmiVoLSxuGb4tCK8/RmLhyGM7UeozT5V<br>1JIFlIeATwRgRN5KeUEehWjDTYbTUwxYkv0vcOxRvOjet8pHLkQl8bF1ZXAT/Ydb<br>CEz7Ht3ga/GDqf+lZyvb7vzY9FSowsBhvCKt4MnXuO8Z2A3kLltGSZ6v+DiRnpRP<br>KU/E8702TZcvjDLF9RNUEXECNAdLVccST00NDg1ciLlt4a66SItQwynFw/+32Sw=<br>=QeJ2<br>-----END PGP SIGNATURE-----<br></pre><br>_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div> </div></body>
</html>