<div dir="ltr">Ok Gerd,<div><br></div><div>I'll include this change in the roadmap of my generator. You know as a developer... there are some many things to do in the backlog and our time available is so short! :-)</div><div>Thanks.</div><div><br></div><div>Alexandre</div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-02 9:34 GMT-03:00 GerdP <span dir="ltr"><<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Alexandre,<br>
<br>
well, the advantage of the keep-complete option is that you don't need<br>
the large overlap and still get complete ways and relations, so<br>
it's about disk usage, memory and quality. As long as you files are rather<br>
small<br>
you can probably use a large overlap value instead.<br>
Maybe you can calculate the needed overlap in your generator.<br>
<br>
ciao,<br>
Gerd<br>
<br>
<br>
Alexandre Loss wrote<br>
<span class="">> Hi Gerd,<br>
><br>
> I already made a previous analysis before to change my generator. Well,<br>
> it's possible, but I practically have to rebuild the generator entirely.<br>
> So, I understood that you said that it's better solution but not a "must"<br>
> solution to change generator. If so, I will prefer to keep the generator<br>
> this way for a while.<br>
> However, If you think I can be missing something in my maps due this mixed<br>
> syntax, then I will plan to change my code.<br>
><br>
> Thanks<br>
><br>
> Alexandre<br>
><br>
> 2015-06-02 2:36 GMT-03:00 Gerd Petermann <<br>
<br>
> gpetermann_muenchen@<br>
<br>
</span><span class="">> >:<br>
><br>
>> Hi Alexandre,<br>
>><br>
>> the better solution would be to change your generator so that<br>
>> it writes the data in the expected order (nodes, ways, relations, each<br>
>> with<br>
>> ascending ids). If you do that, you can remove the options --mixed and<br>
>> --overlap<br>
>> and use the default --keep-complete=true.<br>
>><br>
>> A possible compromise:<br>
>> I have to double check that, but I think the keep-complete option only<br>
>> requires that<br>
>> the ids are sorted, it doesn't care about the order of the elements.<br>
>> On the other hand, the xml parser requires the<br>
>> mixed option when the element types are not sorted,<br>
>> and a check prohibtis the combination of --mixed and keep-complete=true.<br>
>> If I am right, I can remove this check.<br>
>><br>
>> Ciao,<br>
>> Gerd<br>
>><br>
</span>>> ------------------------------<br>
<span class="">>> Date: Sat, 30 May 2015 09:15:19 -0300<br>
>> From:<br>
<br>
> alexandre.loss@<br>
<br>
</span>>> To:<br>
<br>
> mkgmap-dev@.org<br>
<span class=""><br>
>> Subject: Re: [mkgmap-dev] Splitter problem: losing a track segment<br>
>><br>
>><br>
>> Hi Gerd,<br>
>><br>
>> Overlap of 10000 fixed my problem. :-)<br>
>><br>
>> Thank you very much!<br>
>><br>
>> Alexandre<br>
>><br>
>> 2015-05-30 8:20 GMT-03:00 Alexandre Loss <<br>
<br>
> alexandre.loss@<br>
<br>
</span><span class="">> >:<br>
>><br>
>> Hi Gerd,<br>
>><br>
>> Thanks for your answer.<br>
>> I'll try your suggestion and give you a feedback about the result.<br>
>><br>
>> Regards,<br>
>><br>
>> Alexandre<br>
>><br>
>> 2015-05-30 5:43 GMT-03:00 Gerd Petermann <<br>
<br>
> gpetermann_muenchen@<br>
<br>
> ><br>
</span><span class="">>> :<br>
>><br>
>> Hi Alexandre,<br>
>><br>
>> I don't have much time to analyse your data today.<br>
>> I think splitter assumes that the tile boundaries<br>
>> are<br>
>> "multiples of 0x200 map units wide and high"<br>
>> when you use resolution=15.<br>
>><br>
>> Since you use keep-complete=false you have to watch<br>
>> the overlap value.<br>
>> You can use a larger overlap value like 10000 to fix this problem.<br>
>><br>
>> Gerd<br>
>><br>
>><br>
</span>>> ------------------------------<br>
<span class="">>> Date: Fri, 29 May 2015 22:04:34 -0300<br>
>> From:<br>
<br>
> alexandre.loss@<br>
<br>
</span>>> To:<br>
<br>
> mkgmap-dev@.org<br>
<span class=""><br>
>> Subject: [mkgmap-dev] Splitter problem: losing a track segment<br>
>><br>
>><br>
>> Hi guys,<br>
>><br>
>> I'm facing a problem in one of my maps, that is probably might be<br>
>> happening in other places where I didn't see yet.<br>
>> The problem can be seen in the figure below taken from MapSource. There<br>
>> is<br>
>> a gap in a track on the border of the tiles:<br>
>><br>
>> [image: Imagem inline 2]<br>
>><br>
>> So I started to analyze the problem step-by-step till find that the<br>
>> problem was generated by Splitter (last version).<br>
>><br>
>> To simplify your analysis, I edited my .osm file before running Splitter<br>
>> and remove all objects (nodes, lines, poi, etc.) not related to the<br>
>> problem, leaving only the line where the problem happens. The result was<br>
>> the file "93352150-Ribeirao_Preto.osm" attached, containing only this:<br>
>><br>
>> <?xml version="1.0" encoding="UTF-8"?><br>
>><br>
> <osm version="0.6" generator="TSuite 6.6.0.4"><br>
>><br>
<br>
>><br>
</span><span class="">> <node id="576" lat="-21.9388623" lon="-48.3347007" visible="true"<br>
>><br>
> version="1"/><br>
>><br>
> <node id="805" lat="-21.8877920" lon="-48.2932640" visible="true"<br>
>><br>
> version="1"/><br>
>><br>
> <node id="806" lat="-21.8674906" lon="-48.2767485" visible="true"<br>
>><br>
> version="1"/><br>
>><br>
> <node id="804" lat="-21.8661147" lon="-48.2756044" visible="true"<br>
>><br>
> version="1"/><br>
>><br>
> <way id="803" visible="true" version="1"><br>
>><br>
> <nd ref="576"/><br>
>><br>
> <nd ref="805"/><br>
>><br>
> <nd ref="806"/><br>
>><br>
> <nd ref="804"/><br>
>><br>
> <tag k="highway" v="trunk"/><br>
>><br>
> <tag k="name" v="SP-255 DANIELLE"/><br>
>><br>
> <tag k="ref" v="SP-255"/><br>
>><br>
> <tag k="addr:city" v="BOA ESPERANÇA DO SUL"/><br>
>><br>
> <tag k="addr:state" v="SP"/><br>
>><br>
> <tag k="addr:country" v="Brasil"/><br>
>><br>
> </way><br>
>><br>
<br>
>><br>
</span><div><div class="h5">> </osm><br>
>><br>
>> Then I ran Splitter on this file and the result was the file<br>
>> "93352150.osm" (attached and compacted), whose content are the lines<br>
>> bellow:<br>
>><br>
>> <?xml version='1.0' encoding='UTF-8'?><br>
>><br>
> <osm version='0.5' generator='splitter' upload='false'><br>
>><br>
> <bounds minlat='-21.895751953125' minlon='-50.262451171875'<br>
>><br>
> maxlat='-20.401611328125' maxlon='-47.548828125'/><br>
>><br>
> <node id='805' lat='-21.8877920' lon='-48.2932640'/><br>
>><br>
> <node id='806' lat='-21.8674906' lon='-48.2767485'/><br>
>><br>
> <node id='804' lat='-21.8661147' lon='-48.2756044'/><br>
>><br>
> <way id='803'><br>
>><br>
> <nd ref='576'/><br>
>><br>
> <nd ref='805'/><br>
>><br>
> <nd ref='806'/><br>
>><br>
> <nd ref='804'/><br>
>><br>
> <tag k='highway' v='trunk'/><br>
>><br>
> <tag k='name' v='SP-255 DANIELLE'/><br>
>><br>
> <tag k='ref' v='SP-255'/><br>
>><br>
> <tag k='addr:city' v='BOA ESPERANÇA DO SUL'/><br>
>><br>
> <tag k='addr:state' v='SP'/><br>
>><br>
> <tag k='addr:country' v='Brasil'/><br>
>><br>
> </way><br>
>><br>
> </osm><br>
>><br>
>> Note that in the "93352150.osm" file is missing the node 576 definition<br>
>> (i.e.:<br>
> <node id="576" lat="-21.9388623" lon="-48.3347007" visible="true"<br>
>><br>
> version="1"/>).<br>
>> And this is the cause of the lost segment.<br>
>><br>
>> I'm running Splitter in the following way:<br>
>><br>
>> java -jar splitter.jar --split-file=93352150-Ribeirao_Preto.list<br>
>> --max-areas=1024 --mixed=true --keep-complete=false --resolution=15<br>
>> --output=xml 93352150-Ribeirao_Preto.osm<br>
>><br>
>> The above .list file is attached.<br>
>><br>
>> If this is not a Splitter error, please, let me know what I'm doing<br>
>> wrong.<br>
>><br>
>> Thanks.<br>
>><br>
>> Alexandre<br>
>><br>
>><br>
>> _______________________________________________ mkgmap-dev mailing list<br>
>><br>
<br>
</div></div>> mkgmap-dev@.org<br>
<span class=""><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 mailing list<br>
>><br>
<br>
</span>> mkgmap-dev@.org<br>
<span class=""><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 list<br>
>><br>
<br>
</span>> mkgmap-dev@.org<br>
<span class=""><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 mailing list<br>
>><br>
<br>
</span>> mkgmap-dev@.org<br>
<span class=""><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>
</span>> 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>
> image.png (12K)<br>
> <<a href="http://gis.19327.n5.nabble.com/attachment/5846805/0/image.png" target="_blank">http://gis.19327.n5.nabble.com/attachment/5846805/0/image.png</a>><br>
<br>
<br>
Alexandre Loss wrote<br>
<span class="">> Hi Gerd,<br>
><br>
> I already made a previous analysis before to change my generator. Well,<br>
> it's possible, but I practically have to rebuild the generator entirely.<br>
> So, I understood that you said that it's better solution but not a "must"<br>
> solution to change generator. If so, I will prefer to keep the generator<br>
> this way for a while.<br>
> However, If you think I can be missing something in my maps due this mixed<br>
> syntax, then I will plan to change my code.<br>
><br>
> Thanks<br>
><br>
> Alexandre<br>
><br>
> 2015-06-02 2:36 GMT-03:00 Gerd Petermann <<br>
<br>
> gpetermann_muenchen@<br>
<br>
</span><span class="">> >:<br>
><br>
>> Hi Alexandre,<br>
>><br>
>> the better solution would be to change your generator so that<br>
>> it writes the data in the expected order (nodes, ways, relations, each<br>
>> with<br>
>> ascending ids). If you do that, you can remove the options --mixed and<br>
>> --overlap<br>
>> and use the default --keep-complete=true.<br>
>><br>
>> A possible compromise:<br>
>> I have to double check that, but I think the keep-complete option only<br>
>> requires that<br>
>> the ids are sorted, it doesn't care about the order of the elements.<br>
>> On the other hand, the xml parser requires the<br>
>> mixed option when the element types are not sorted,<br>
>> and a check prohibtis the combination of --mixed and keep-complete=true.<br>
>> If I am right, I can remove this check.<br>
>><br>
>> Ciao,<br>
>> Gerd<br>
>><br>
</span>>> ------------------------------<br>
<span class="">>> Date: Sat, 30 May 2015 09:15:19 -0300<br>
>> From:<br>
<br>
> alexandre.loss@<br>
<br>
</span>>> To:<br>
<br>
> mkgmap-dev@.org<br>
<span class=""><br>
>> Subject: Re: [mkgmap-dev] Splitter problem: losing a track segment<br>
>><br>
>><br>
>> Hi Gerd,<br>
>><br>
>> Overlap of 10000 fixed my problem. :-)<br>
>><br>
>> Thank you very much!<br>
>><br>
>> Alexandre<br>
>><br>
>> 2015-05-30 8:20 GMT-03:00 Alexandre Loss <<br>
<br>
> alexandre.loss@<br>
<br>
</span><span class="">> >:<br>
>><br>
>> Hi Gerd,<br>
>><br>
>> Thanks for your answer.<br>
>> I'll try your suggestion and give you a feedback about the result.<br>
>><br>
>> Regards,<br>
>><br>
>> Alexandre<br>
>><br>
>> 2015-05-30 5:43 GMT-03:00 Gerd Petermann <<br>
<br>
> gpetermann_muenchen@<br>
<br>
> ><br>
</span><span class="">>> :<br>
>><br>
>> Hi Alexandre,<br>
>><br>
>> I don't have much time to analyse your data today.<br>
>> I think splitter assumes that the tile boundaries<br>
>> are<br>
>> "multiples of 0x200 map units wide and high"<br>
>> when you use resolution=15.<br>
>><br>
>> Since you use keep-complete=false you have to watch<br>
>> the overlap value.<br>
>> You can use a larger overlap value like 10000 to fix this problem.<br>
>><br>
>> Gerd<br>
>><br>
>><br>
</span>>> ------------------------------<br>
<span class="">>> Date: Fri, 29 May 2015 22:04:34 -0300<br>
>> From:<br>
<br>
> alexandre.loss@<br>
<br>
</span>>> To:<br>
<br>
> mkgmap-dev@.org<br>
<span class=""><br>
>> Subject: [mkgmap-dev] Splitter problem: losing a track segment<br>
>><br>
>><br>
>> Hi guys,<br>
>><br>
>> I'm facing a problem in one of my maps, that is probably might be<br>
>> happening in other places where I didn't see yet.<br>
>> The problem can be seen in the figure below taken from MapSource. There<br>
>> is<br>
>> a gap in a track on the border of the tiles:<br>
>><br>
>> [image: Imagem inline 2]<br>
>><br>
>> So I started to analyze the problem step-by-step till find that the<br>
>> problem was generated by Splitter (last version).<br>
>><br>
>> To simplify your analysis, I edited my .osm file before running Splitter<br>
>> and remove all objects (nodes, lines, poi, etc.) not related to the<br>
>> problem, leaving only the line where the problem happens. The result was<br>
>> the file "93352150-Ribeirao_Preto.osm" attached, containing only this:<br>
>><br>
>> <?xml version="1.0" encoding="UTF-8"?><br>
>><br>
> <osm version="0.6" generator="TSuite 6.6.0.4"><br>
>><br>
<br>
>><br>
</span><span class="">> <node id="576" lat="-21.9388623" lon="-48.3347007" visible="true"<br>
>><br>
> version="1"/><br>
>><br>
> <node id="805" lat="-21.8877920" lon="-48.2932640" visible="true"<br>
>><br>
> version="1"/><br>
>><br>
> <node id="806" lat="-21.8674906" lon="-48.2767485" visible="true"<br>
>><br>
> version="1"/><br>
>><br>
> <node id="804" lat="-21.8661147" lon="-48.2756044" visible="true"<br>
>><br>
> version="1"/><br>
>><br>
> <way id="803" visible="true" version="1"><br>
>><br>
> <nd ref="576"/><br>
>><br>
> <nd ref="805"/><br>
>><br>
> <nd ref="806"/><br>
>><br>
> <nd ref="804"/><br>
>><br>
> <tag k="highway" v="trunk"/><br>
>><br>
> <tag k="name" v="SP-255 DANIELLE"/><br>
>><br>
> <tag k="ref" v="SP-255"/><br>
>><br>
> <tag k="addr:city" v="BOA ESPERANÇA DO SUL"/><br>
>><br>
> <tag k="addr:state" v="SP"/><br>
>><br>
> <tag k="addr:country" v="Brasil"/><br>
>><br>
> </way><br>
>><br>
<br>
>><br>
</span><div><div class="h5">> </osm><br>
>><br>
>> Then I ran Splitter on this file and the result was the file<br>
>> "93352150.osm" (attached and compacted), whose content are the lines<br>
>> bellow:<br>
>><br>
>> <?xml version='1.0' encoding='UTF-8'?><br>
>><br>
> <osm version='0.5' generator='splitter' upload='false'><br>
>><br>
> <bounds minlat='-21.895751953125' minlon='-50.262451171875'<br>
>><br>
> maxlat='-20.401611328125' maxlon='-47.548828125'/><br>
>><br>
> <node id='805' lat='-21.8877920' lon='-48.2932640'/><br>
>><br>
> <node id='806' lat='-21.8674906' lon='-48.2767485'/><br>
>><br>
> <node id='804' lat='-21.8661147' lon='-48.2756044'/><br>
>><br>
> <way id='803'><br>
>><br>
> <nd ref='576'/><br>
>><br>
> <nd ref='805'/><br>
>><br>
> <nd ref='806'/><br>
>><br>
> <nd ref='804'/><br>
>><br>
> <tag k='highway' v='trunk'/><br>
>><br>
> <tag k='name' v='SP-255 DANIELLE'/><br>
>><br>
> <tag k='ref' v='SP-255'/><br>
>><br>
> <tag k='addr:city' v='BOA ESPERANÇA DO SUL'/><br>
>><br>
> <tag k='addr:state' v='SP'/><br>
>><br>
> <tag k='addr:country' v='Brasil'/><br>
>><br>
> </way><br>
>><br>
> </osm><br>
>><br>
>> Note that in the "93352150.osm" file is missing the node 576 definition<br>
>> (i.e.:<br>
> <node id="576" lat="-21.9388623" lon="-48.3347007" visible="true"<br>
>><br>
> version="1"/>).<br>
>> And this is the cause of the lost segment.<br>
>><br>
>> I'm running Splitter in the following way:<br>
>><br>
>> java -jar splitter.jar --split-file=93352150-Ribeirao_Preto.list<br>
>> --max-areas=1024 --mixed=true --keep-complete=false --resolution=15<br>
>> --output=xml 93352150-Ribeirao_Preto.osm<br>
>><br>
>> The above .list file is attached.<br>
>><br>
>> If this is not a Splitter error, please, let me know what I'm doing<br>
>> wrong.<br>
>><br>
>> Thanks.<br>
>><br>
>> Alexandre<br>
>><br>
>><br>
>> _______________________________________________ mkgmap-dev mailing list<br>
>><br>
<br>
</div></div>> mkgmap-dev@.org<br>
<span class=""><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 mailing list<br>
>><br>
<br>
</span>> mkgmap-dev@.org<br>
<span class=""><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 list<br>
>><br>
<br>
</span>> mkgmap-dev@.org<br>
<span class=""><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 mailing list<br>
>><br>
<br>
</span>> mkgmap-dev@.org<br>
<span class=""><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>
</span>> 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>
> image.png (12K)<br>
> <<a href="http://gis.19327.n5.nabble.com/attachment/5846805/0/image.png" target="_blank">http://gis.19327.n5.nabble.com/attachment/5846805/0/image.png</a>><br>
<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://gis.19327.n5.nabble.com/Splitter-problem-losing-a-track-segment-tp5846557p5846806.html" target="_blank">http://gis.19327.n5.nabble.com/Splitter-problem-losing-a-track-segment-tp5846557p5846806.html</a><br>
Sent from the Mkgmap Development mailing list archive at Nabble.com.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<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></div></div></blockquote></div><br></div></div></div>