Hi Henning, I am confused now. None of the o5m files contains the error that was in yesterdays data, and the file sizes are very different (new files are smaller). Do you have an idea why?
Gerd Henning Scholland wrote > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Gerd > Here it is: http://www.aighes.de/data/mkgmap.zip > > Henning > > Am 24.11.2013 09:02, schrieb Gerd Petermann: >> Hi Henning, >> >> I still don't understand why this change is important for mkgmap, >> maybe I did not fix the real problem. It would be great if you >> could reproduce it again with r312 and --output=o5m . The problem >> was e.g. in file 10100011.o5m. Next, execute splitter r312(or r311) >> with --output=pbf and post a link to both files. >> >> Gerd >> >>> Date: Sat, 23 Nov 2013 23:05:54 +0100 From: > osm@ > To: >>> > mkgmap-dev@.org > Subject: Re: [mkgmap-dev] >>> IO-problem with actual trunk >>> >> Hi Gerd, works as expected. >> >> Henning >> >> Am 23.11.2013 15:11, schrieb Gerd Petermann: >>>>> Hi Henning, >>>>> >>>>> I was not able to reproduce the problem, but I found a >>>>> potential error in the o5m write routine: it did not write >>>>> enough reset bytes. I've changed that in r313. Please try if >>>>> this helps. >>>>> >>>>> Gerd >>>>> >>>>>> Date: Sat, 23 Nov 2013 10:26:07 +0100 From: > osm@ >>>>>> To: > mkgmap-dev@.org > Subject: Re: >>>>>> [mkgmap-dev] IO-problem with actual trunk >>>>>> >>>>>> Am 23.11.2013 09:36, schrieb Gerd Petermann: >>>>>>> Hi Henning, >>>>>>> >>>>>>> okay, maybe it was an error in the update process. I see >>>>>>> that e.g. OSM stats also had problems: >>>>>>> http://osmstats.altogetherlost.com/index.php?item=nodes >>>>>>> >>>>>>> Anyway, it is obvious the code in splitter is missing a >>>>>>> check, either in the o5m read or in the write routine (or >>>>>>> both) :-( >>>>>>> >>>>>>> If you can reproduce the problem with the downloaded >>>>>>> planet, maybe try to use --output=pbf first. >>>>>>> >>>>>>> Gerd >>>>>> >>>>>> Hi Gerd, I'm not that familiar with o5m-format, but it is >>>>>> possible,, that only a part of the world is corrupted? >>>>>> Maybe you remember, that I'm splitting all my maps at ones. >>>>>> And all other maps are correct. If it's not possible, I >>>>>> think splitter have a problem with this. >>>>>> >>>>>> Also I can update the used planet-file with osmupdate. >>>>>> >>>>>> Henning >>>>>> >>>>>> _______________________________________________ mkgmap-dev >>>>>> mailing list > mkgmap-dev@.org > >>>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ mkgmap-dev >>>>> mailing list > mkgmap-dev@.org > >>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >>>>> >>> >>> _______________________________________________ mkgmap-dev >>> mailing list > mkgmap-dev@.org > >>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >> >> >> >> >> _______________________________________________ mkgmap-dev mailing >> list > mkgmap-dev@.org > >> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.14 (GNU/Linux) > > iQEcBAEBAgAGBQJSkisgAAoJEPFgsWC7jOeT90UH/i8z82v8ysHXuw8iOK4+OrWk > FMMz7lWY/E6ngsijFUijWxflA8NZDkavwuc08QSyg+7x6y+cSa53u31hQYTzIYhc > FZGz47NRSWc/pkSC9I2BNu6uFdRDjOQgPP/1HKVzHfcwXvTNn4C4cr1CXdOMGOD3 > pKOjhSP9N1y1htGGCyg5ujTcLmQjRlbjzbL3cvg0TYqDYjYucnzxTUzRCopMn3cL > f6Ew/QcBIc/wF3pHkl9oEaKoLb60AXl/4o1apJrZF12mxNFpM/ffyI8nTn8AAJZc > fHs91VS4QrQkWppX1OidPhVpRj9HbGUNke2Ne+qBL+Jxs6CIDWy9EadfsLz0qlE= > =kkbL > -----END PGP SIGNATURE----- > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev@.org > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- View this message in context: http://gis.19327.n5.nabble.com/IO-problem-with-actual-trunk-tp5786885p5787070.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
