<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 Felix,<br><br>it seems that the default --search-limit is too low for japan with sea data.<br>With --search-limit=5000000 I see a very good split after ~30 seconds:<br>Solution is nice. Can't find a better solution: 86 tile(s). The smallest node count is 1111027 (92 %), the worst aspect ratio is near 3.94<br><br>For many other input files, this will just increase run time a lot.<br><br>I am not very happy with this option. I think I will replace it<br>with something more useful like<br>--wanted-fill-ratio=90<br>which means try to find a solution where the least populated<br>tile has 90% of max-nodes.<br><br>The problem is that some areas do not allow such a good result,<br>so I am still looking for good criteria to stop the search, maybe<br>I'll use the overall search time in seconds:<br>--max-search-time=60<br>would use the best result found after 60 seconds.<br><br>Any other ideas?<br><br>Gerd<br><br><br><div><hr id="stopSpelling">From: gpetermann_muenchen@hotmail.com<br>To: mkgmap-dev@lists.mkgmap.org.uk<br>Date: Sat, 31 May 2014 08:21:43 +0200<br>Subject: [mkgmap-dev] FW: Splitter defaulting on Japan<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr"><br><br><div><hr id="ecxstopSpelling">From: gpetermann_muenchen@hotmail.com<br>To: extremecarver@gmail.com<br>Subject: RE: [mkgmap-dev] Splitter defaulting on Japan<br>Date: Sat, 31 May 2014 08:17:31 +0200<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">Hi Felix,<br><br>thanks for reporting. I can reproduce the problem. It disappears when<br>you remove the --precomp-sea option.<br>I'll try to find out why.<br><br>> Where is the log saved? Do I need to provide it? Splitter not fully up <br>This message is printed to stderr for the case that you pipe stdout to a file like this:<br>java -jar splitter .... > splitter.log<br><br>Gerd<br><br><div>> Date: Sat, 31 May 2014 05:33:06 +0200<br>> From: extremecarver@gmail.com<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: [mkgmap-dev] Splitter defaulting on Japan<br>> <br>> Failed to calculate areas. See log for details.<br>> <br>> Where is the log saved? Do I need to provide it? Splitter not fully up <br>> to date - see compiled date (svn update just before)...<br>> I'll retry with up to date splitter still...<br>> <br>> c:\OpenMTBMap\maps>java -Xmx9600m -jar c:\openmtbmap\splitter.jar <br>> --precomp-sea=c:\openmtbmap\maps\sea.zip --max-nodes=1200000 <br>> --output=pbf "--keep-complete" --max-areas=255 <br>> --geonames-file=cities5000 --description=japan --mapid=65590000 c:\OpenMTBMa<br>> p\osmpbf_geofabrik\japan.o5m<br>> Splitter version unknown compiled 2014-05-28T18:16:29+0200<br>> boundary-tags=use-exclude-list<br>> cache=<br>> description=japan<br>> geonames-file=cities5000<br>> keep-complete=true<br>> mapid=65590000<br>> max-areas=255<br>> max-nodes=1200000<br>> max-threads=8 (auto)<br>> mixed=false<br>> no-trim=false<br>> num-tiles=<br>> output=pbf<br>> output-dir=<br>> overlap=auto<br>> polygon-desc-file=<br>> polygon-file=<br>> precomp-sea=c:\openmtbmap\maps\sea.zip<br>> problem-file=<br>> problem-report=<br>> resolution=13<br>> search-limit=1000000<br>> split-file=<br>> status-freq=120<br>> stop-after=dist<br>> write-kml=<br>> Elapsed time: 0s Memory: Current 184MB (2MB used, 182MB free) Max 8533MB<br>> Time started: Sat May 31 02:40:37 CEST 2014<br>> Map is being split for resolution 13:<br>> - area boundaries are aligned to 0x800 map units (0.0439453125 degrees)<br>> - areas are multiples of 0x800 map units wide and high<br>> Processing c:\OpenMTBMap\osmpbf_geofabrik\japan.o5m<br>> Bounding box 122.56070000000001 20.08228 154.4709 45.80245<br>> 10'000'000 nodes processed... id=752184948<br>> 20'000'000 nodes processed... id=922482748<br>> 30'000'000 nodes processed... id=1233696234<br>> 40'000'000 nodes processed... id=1315824764<br>> 50'000'000 nodes processed... id=1421002430<br>> 60'000'000 nodes processed... id=1497506798<br>> 70'000'000 nodes processed... id=1751094845<br>> 80'000'000 nodes processed... id=2040104150<br>> 90'000'000 nodes processed... id=2350328457<br>> in 1 file<br>> Time: Sat May 31 02:41:01 CEST 2014<br>> Counting nodes of precompiled sea data ...<br>> Bounding box 144.84375 19.6875 145.546875 20.390625<br>> Bounding box 135.703124999 20.390625 136.406249999 21.09375<br>> Bounding box 144.84375 20.390625 145.546875 21.09375<br>> Bounding box 122.34375000000001 23.90625 123.04687499900001 24.609375<br>> <br>> <br>> ........<br>> cut away here...<br>> .......<br>> Bounding box 142.734375 45.703125 143.4375 46.40625<br>> Bounding box 143.4375 45.703125 144.140625 46.40625<br>> Bounding box 149.0625 45.703125 149.765625 46.40625<br>> Bounding box 149.765625 45.703125 150.46875 46.40625<br>> Bounding box 150.46875 45.703125 151.171875 46.40625<br>> Added 835594 nodes from precompiled sea data.<br>> Precompiled sea data pass took 1797 ms<br>> Exact map coverage is (20.08227825164795,122.56068706512451) to <br>> (45.80243110656738,154.47088479995728)<br>> Rounded map coverage is (20.0390625,122.51953125) to <br>> (45.8349609375,154.51171875)<br>> Splitting nodes into areas containing a maximum of 1'200'000 nodes each...<br>> Highest node count in a single grid element is 205'139<br>> Trying to find nice split for (20.0390625,122.51953125) to <br>> (45.8349609375,154.51171875) with 98'482'055 nodes<br>> searching for split with min-nodes 12000, learned 0 good partial solutions<br>> Split was not yet succesfull. Trying to remove large empty areas...<br>> Trying again with 1 trimmed partition(s), also allowing big empty parts.<br>> Solving partition (23.818359375,122.6953125) to <br>> (45.8349609375,153.0615234375) with 98'482'055 nodes<br>> Trying to find nice split for (23.818359375,122.6953125) to <br>> (45.8349609375,153.0615234375) with 98'482'055 nodes<br>> searching for split with min-nodes 12000, learned 0 good partial solutions<br>> Warning: No solution found for partition (23.818359375,122.6953125) to <br>> (45.8349609375,153.0615234375) with 98'482'055 nodes<br>> Final solution has 0 tile(s). The smallest node count is <br>> 9223372036854775807 (0 %), the worst aspect ratio is near -1.0<br>> Failed to calculate areas. See log for details.<br>> Failed to calculate areas.<br>> Sorry. Cannot split the file without creating huge, almost empty, tiles.<br>> Please specify a bounding polygon with the --polygon-file parameter.<br>> Time finished: Sat May 31 02:41:04 CEST 2014<br>> _______________________________________________<br>> mkgmap-dev mailing list<br>> mkgmap-dev@lists.mkgmap.org.uk<br>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<br></div> </div></div> </div>
<br>_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div> </div></body>
</html>