<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>HI Gerd, I don’t need to keep any information, unless splitter fails/crashes, in which case I need some idea of what went wrong (this very rarely happens). Perhaps I need to add something to my map build script to wait until splitter has completed before deciding what to do with the logging details, adding them to the log file if it fails and discarding if it succeeds. That would save making changes to splitter. Currently, I just redirect stdout of each step in the build process to the same file, so I would need to replace this with something more intelligent.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Mike<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Gerd Petermann [mailto:GPetermann_muenchen@hotmail.com] <br><b>Sent:</b> 05 August 2016 06:16<br><b>To:</b> Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk><br><b>Subject:</b> Re: [mkgmap-dev] Splitter diagnostic messages<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div id=divtagdefaultwrapper><p style='background:white'><span style='color:black'>Hi Mike,<o:p></o:p></span></p><p style='background:white'><span style='color:black'><o:p> </o:p></span></p><p style='background:white'><span style='color:black'>I've once tried to change the code to allow this and stopped because it is quite a lot of work<o:p></o:p></span></p><p style='background:white'><span style='color:black'>and in my eyes nearly all information printed by splitter is for performance analyses or debugging<o:p></o:p></span></p><p style='background:white'><span style='color:black'>in case that splitter crashes because of memory limits or when the split algo doesn't find a correct split.<o:p></o:p></span></p><p style='background:white'><span style='color:black'><o:p> </o:p></span></p><p style='background:white'><span style='color:black'>I think the lines starting "Length" in following messages are no longer needed:<o:p></o:p></span></p><p style='background:white'><span style='color:black'><o:p> </o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'>Statistics for coords map:<br>Length-1 chunks: 4.586.254, used Bytes including overhead: 47.435.504<br>Length-2 chunks: 13.128, used Bytes including overhead: 160.832<o:p></o:p></span></p></div><p class=MsoNormal style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'>... <o:p></o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'>Length-63 chunks: 153, used Bytes including overhead: 25.464<br>Length-64 chunks: 191, used Bytes including overhead: 26.152<br><br>Number of stored ids: 11.933.022 require ca. 7.16 bytes per pair. 1397668 chunks are used, the avg. number of values in one 64-chunk is 8.<br>Map details: bytes/overhead 17.823.524 / 67.718.172, overhead includes 4 arrays with 16 MB<o:p></o:p></span></p></div><p class=MsoNormal style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p><p style='background:white'><span style='color:black'>I also like to remove the bbox messages from the precompiled sea:<o:p></o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'>Counting nodes of precompiled sea data ...<br>Bounding box -4.921875 48.515625 -4.218749999 49.21875<br>Bounding box -4.218749999 48.515625 -3.515625 49.21875<br>Bounding box -3.515625 48.515625 -2.8125 49.21875<br>Bounding box -2.8125 48.515625 -2.109374999 49.21875<br>Bounding box -2.109374999 48.515625 -1.40625 49.21875<o:p></o:p></span></p></div><p class=MsoNormal style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p><p style='background:white'><span style='color:black'>What information would you like to keep? Maybe you can extract those?<o:p></o:p></span></p><p style='background:white'><span style='color:black'><o:p> </o:p></span></p><p style='background:white'><span style='color:black'>Gerd<o:p></o:p></span></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>Von:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>> im Auftrag von Mike Baggaley <<a href="mailto:mike@tvage.co.uk">mike@tvage.co.uk</a>><br><b>Gesendet:</b> Donnerstag, 4. August 2016 23:58:30<br><b>An:</b> <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br><b>Betreff:</b> [mkgmap-dev] Splitter diagnostic messages</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:#1F497D'>Hi Steve/Gerd (or whoever is the splitter expert), I was just wondering whether it would be possible to reduce the amount of diagnostic information produced by Splitter. I use a batch file to build my map, and the output from each process is appended to a log file. I get an enormous amount of uninteresting info from Splitter that I have to scroll past to see the output from mkgmap. Not a major problem, but it would be useful if there was an option to reduce this (I already have --status-freq=0 in my command line).<o:p></o:p></span></p><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:#1F497D'>Cheers,<o:p></o:p></span></p><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:#1F497D'>Mike<o:p></o:p></span></p><p style='background:white'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p style='background:white'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p></div></div></body></html>