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: o...@aighes.de > To: mkgmap-dev@lists.mkgmap.org.uk > 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@lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
