[mkgmap-dev] IO-problem with actual trunk

Sun Nov 24 18:43:02 GMT 2013

Hi Henning,

GerdP wrote
> 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?

A few more details:
Executing osmconvert with yesterdays data always shows this:
c:\temp>osmconvert 10100001.o5m -o=10100001.o5m.osm
osmconvert Warning: wrong sequence at relation 305138
osmconvert Warning: next object is node 10216945201
osmconvert Warning: osmconvert Warning: unexpected contents after logical
end of
 file: 10100001.o5m

c:\temp>osmconvert 10100002.o5m -o=10100002.o5m.osm
osmconvert Warning: wrong sequence at relation 383908
osmconvert Warning: next object is node 10204620185
osmconvert Warning: osmconvert Warning: unexpected contents after logical
end of
 file: 10100002.o5m

and more errors for 10100011.o5m:
c:\temp>osmconvert 10100011.o5m -o=10100011.o5m.osm
osmconvert Warning: wrong sequence at relation 152458
osmconvert Warning: next object is node 10221551320
osmconvert Warning: invalid .o5m string reference: 70->131436542
osmconvert Warning: invalid .o5m string reference: 70->88921963
osmconvert Warning: invalid .o5m string reference: 70->506

With the new data I see only the expected messages:
c:\temp\henning>osmconvert 10100001.o5m -o=10100001.o5m.osm
osmconvert Warning: wrong sequence at relation 305138
osmconvert Warning: next object is node 10216945201

c:\temp\henning>osmconvert 10100002.o5m -o=10100002.o5m.osm
osmconvert Warning: wrong sequence at relation 383908
osmconvert Warning: next object is node 10204620185

Some of the converted .osm files are equal, but the o5m files are different
(garbage at the end
of the file). So, in other words, it seems that your file system was
corrupted.

Gerd

--
View this message in context: http://gis.19327.n5.nabble.com/IO-problem-with-actual-trunk-tp5786885p5787076.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.