Steve Ratcliffe wrote >> The main difference seems to be polygons. > > I used osmconvert to convert the .o5m and .pbf to .osm; they were > identical apart from a difference in the last decimal place of minlon > and maxlat in the > <bounds> > elements. > > So the problem would appear to be on the mkgmap side, not the splitter > side. Or perhaps with reading o5m, I've not tried splitting with o5m as > input.
Yes, the problem is probably in the o5m reader of mkgmap. I am looking at it. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Commit-r2412-merge-the-o5m-support-branch-tp5740691p5740818.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list [email protected] http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
