<div dir="ltr">gerd p <div><br></div><div>under stood mate , but why does it only happen to this one , but when i change others max nodes it is all ok </div><div><br></div><div>i will send the style files i use , </div><div><br></div><div>stephen </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 6, 2015 at 10:18 AM, GerdP <span dir="ltr"><<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Stephen,<br>
<br>
the log shows no problems. Why do you think that max-nodes=400000 doesn't<br>
work?<br>
Do you see an error message in mkgmap?<br>
If yes, please provide your style files so that I can reproduce the problem.<br>
Maybe your style still adds one POI for each point of each highway?<br>
<br>
Gerd<br>
<br>
<br>
steve sgalowski wrote<br>
> canada splitter log file<br>
> as expected , looks like i was correct<br>
> the size of the split has to be smaller<br>
> stephen<br>
><br>
> On Tue, Jan 6, 2015 at 7:25 AM, Carlos Dávila <<br>
<br>
> cdavilam@<br>
<br>
> ><br>
> wrote:<br>
><br>
>> Final file size depends on the amount of data in the input, not on the<br>
>> value of max-nodes. If you need a final img smaller than a given size you<br>
>> have to reduce the area covered by the input file or reduce the number of<br>
>> osm elements from the input that go into the map playing with your style<br>
>> files.<br>
>><br>
>> El 05/01/15 a las 22:07, Steve Sgalowski escribió:<br>
>><br>
>>> gerd and carlos<br>
>>> i am now running the splitter log file setup on my canada map<br>
>>> and see what it does , the end result on this map = 6.8 gb img file<br>
>>> wonder why some country can exceed and others not<br>
>>> stephen<br>
>>><br>
>>><br>
>>> On Tue, Jan 6, 2015 at 7:00 AM, Carlos Dávila <<br>
<br>
> cdavilam@<br>
<br>
> >> <mailto:<br>
<br>
> cdavilam@<br>
<br>
> >> wrote:<br>
>>><br>
>>> Not sure what you mean. If you split a given country in a higher<br>
>>> number of tiles (lower max-nodes) final size will be the same or<br>
>>> slightly bigger, as there are more duplicated info due to overlap.<br>
>>> Or you are loosing some information in the process to reduce final<br>
>>> file size.<br>
>>><br>
>>> El 05/01/15 a las 21:34, Steve Sgalowski escribió:<br>
>>><br>
>>> in some of the countries i do , if i dont make the node count<br>
>>> small , the map size exceedds , size limit of 3 gb<br>
>>> then unshure how , canada has done this ok<br>
>>><br>
>>> stephen<br>
>>><br>
>>><br>
>>> On Tue, Jan 6, 2015 at 5:24 AM, Gerd Petermann<br>
>>> <<br>
<br>
> gpetermann_muenchen@<br>
<br>
> >> <mailto:<br>
<br>
> gpetermann_muenchen@<br>
<br>
> ><br>
>>> <mailto:<br>
<br>
> gpetermann_muenchen@<br>
<br>
> >> <mailto:<br>
<br>
> gpetermann_muenchen@<br>
<br>
> >>> wrote:<br>
>>><br>
>>> Hi all,<br>
>>><br>
>>> I wonder what splitter should do in this case:<br>
>>><br>
>>> Stephen uses paramter --max-nodes=80000<br>
>>> and splitter reports<br>
>>> "Highest node count in a single grid element is 557,084"<br>
>>><br>
>>> It is obvious that at least one tile will have much more<br>
>>> than the<br>
>>> requested 80.000 nodes,<br>
>>> on the other hand, the file africa.osm.pbf contains large<br>
>>> nearly<br>
>>> empty areas,<br>
>>> and that makes it very difficult to find a good split.<br>
>>> The current version r416 fails because it doesn't accept<br>
>>> tiles<br>
>>> with less than 5% of<br>
>>> the max-nodes value, so it searches for a solution where<br>
>>> every<br>
>>> tile has at least 4000 nodes,<br>
>>> and that might not exist.<br>
>>><br>
>>> I see these options:<br>
>>> 1) splitter can continue trying to split the data, accepting<br>
>>> almost empty output files<br>
>>> (e.g. some with < 5 nodes and very high aspect ratios like<br>
>>> 32)<br>
>>> 2) if that fails, splitter can set the max-nodes value to<br>
>>> 557,084<br>
>>> and try again<br>
>>> 3) or stop with an error message that tells the user that<br>
>>> it is<br>
>>> not possible<br>
>>> to split with the used resolution<br>
>>> 4) or restart using a higher resolution (15 would be<br>
>>> required<br>
>>> here instead of 13),<br>
>>><br>
>>> @Stephen<br>
>>> What reason do you have to use such a small max-nodes value?<br>
>>> Would it be ok for you to use a higher one?<br>
>>><br>
>>> Gerd<br>
>>><br>
>>><br>
>> _______________________________________________<br>
>> mkgmap-dev mailing list<br>
>><br>
<br>
> mkgmap-dev@.org<br>
<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>
> mkgmap-dev mailing list<br>
<br>
> mkgmap-dev@.org<br>
<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>
> splitter.log (356K)<br>
> <<a href="http://gis.19327.n5.nabble.com/attachment/5829156/0/splitter.log" target="_blank">http://gis.19327.n5.nabble.com/attachment/5829156/0/splitter.log</a>><br>
<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://gis.19327.n5.nabble.com/Problem-in-splitter-Africa-tp5829130p5829158.html" target="_blank">http://gis.19327.n5.nabble.com/Problem-in-splitter-Africa-tp5829130p5829158.html</a><br>
Sent from the Mkgmap Development mailing list archive at Nabble.com.<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></blockquote></div><br></div>