
On Fri, May 20, 2011 at 12:00:58AM +0300, Marko Mäkelä wrote:
There seems to be something wrong with the pbf output, because mkgmap is outputting this kind of messages:
2011/05/19 23:53:11 WARNING (OsmBinHandler): 63240005.osm.pbf: Way http://www.openstreetmap.org/browse/way/107168753 references undefined node 1231941341
This turns out to be a chattiness difference in the mkgmap parsers. The XML parser does not seem to complain when ways are referencing undefined nodes. I tested by checking the nodes of way 57746082, the role=outer way of relation 900367, in my tile 63240006.osm.gz. I searched for '2442732[01345789][0-9]' and did not find any matches apart from the nd ref in the way.
Apart from these warnings, I am still getting the warnings about unclosed polygons, like this:
2011/05/19 23:54:39 WARNING (StyledConverter): 63240008.osm.pbf: Unclosed way http://www.openstreetmap.org/browse/way/23679990 [natural=water] should be converted as shape but the start or end point lies inside the bbox. Skip it.
For some reason, the pbf splitter workflow failed to issue the data error (one dead-end oneway) that I got reported for the same finland.osm.pbf when splitting it to osm.gz.
These two issues are still unexplained and need to be fixed in my opinion. Best regards, Marko