On 2:59 PM, Marko Mäkelä wrote:
You do not seem to provide -Dlog.config to the mkgmap run. Can you try with my logging.properties at http://www.polkupyoraily.net/osm/ please? Look for warnings about multipolygons, coastline, and unclosed areas. Well, I found this:
2011/06/07 13:51:35 WARNING (MultiPolygonRelation): 63240017.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/169902 contains errors. Not very informative but it seems like the relation is indeed broken. Any thoughts? I will take a look but I am not yet exactly sure of what I am looking for. There are a few other problems in that tile but I don't know if the message that happens right after that relation is relevant or not to the problem: 2011/06/07 13:51:35 WARNING (MultiPolygonRelation): 63240017.osm.gz: Polygon 4611686018427417347(9330P)(37530594[1519P],37530542[718P],107036527[25P],107036529[719P],97129165[198P],37530536[175P],105082387[1486P],37530662[47P],65200293[37P],103323627[227P],103323621[144P],106442699[3P],106521867[16P],106521842[749P],37530684[1727P],37530658[1554P]) carries role outer but lies inside an outer polygon. Potentially its role should be inner.
The splitter --pbf seems to work well with Steve's patch in place. I generated finland.osm.pbf today using the PBF splitter and got a few legitimate warnings for unclosed polygons and anti-islands. Yesterday, it gave me the same warnings about dead-end oneways as the XML splitter. So, I do trust your work on the PBF splitter now. Ok, glad that's working properly. I am wondering if we should keep the output option as-is (--pbf) or change it to --output=pbf as suggested before.