On Sat, Jan 25, 2020 at 06:26:35PM -0800, Joseph Herlant wrote: > Hi, > > Taking the england-latest.osm.pbf from > https://download.geofabrik.de/europe/great-britain.html it does fail > with 0.5.4 after several minutes of processing with (not a segfault > per say but still failing):
First, I suspect that (geofabrik) is where I found the original file. > > PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 > tiles 7:17 181 MB > PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 > tiles 7:47 181 MB > PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 > tiles 8:17 181 MB > worker 3 exit > PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 > tiles 8:18 181 MB > PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 0 relations 0 tiles > 8:18 181 MB > process_multipolygons:process (thread 0) > process_multipolygons:finish (thread 0) > maptool: /build/navit-vwCTlu/navit-0.5.4+dfsg.1/navit/maptool/itembin.c:93: > item_bin_copy_attr: Assertion `attr == attr_osm_wayid' failed. > > You mention in the bug there that you were able to run your pbf by > compiling maptool from the git repo. What compilation flags did you > use? I used ./maptool --protobuf -i /ssdback1/ael/mapping/mkgmap/great-britain-latest.osm.pbf test.bin inside my local navit_build directory where I compiled maptool. Many warnings and such scrolled past on the screen which were too fast to read, but I think were just reporting inconsistent or expected tagging in places. I did not bother to pipe through less to check all of that so maybe the could have been assertion failures if they did not prevent final completion. It looks as if the last commit on git when I last pulled was b24b3ed0d76d3cb4886fc821b0c5fb8dad553f15 which I now realise was you on Mon Jan 20 12:03:47 2020 -0800
