
On Fri, May 27, 2011 at 11:29:15AM +0100, Steve Ratcliffe wrote:
There could still be bugs in the mkgmap pbf reader code. Although it has been in for a while, its probably not been used much until now.
I routinely use the PBF input format for creating my --style=routes-* layers. If there are bugs in the PBF input, they could be in the parsing of polygons. I guess I could find this out easily: create a style that translates only natural=water polygons, and feed finland.osm.pbf to it. If it complains about areas that the default style does not complain about, then the PBF parser is to blame. Some time ago, I complained that the PBF code path did not produce some warnings about oneways coming from or going to nowhere, while the XML path did. I just realized that the head of the mkgmap.log.* was most likely discarded because of the numerous warnings about unreferenced nodes in ways. I only had configured 4 log files of at most 5MB each. Marko