[mkgmap-dev] [PATCH v1] Multipolygon: do not warn about joining problems for ways outside the bbox
From Marko Mäkelä marko.makela at iki.fi on Wed Nov 10 09:35:17 GMT 2010
On Wed, Nov 10, 2010 at 01:07:11AM -0800, aighes wrote: > >Hi >Splitter used 59.897461,25.312500 to 63.061523,27.246094, for splitting this >tile. > >I already take a watch at all multipolygon-Errors. This message was the only >one, which was about the multipolygon of the lake. But I uploaded the hole >file at http://hscholland.de/data/mkgmap.log.0 The file does include some more detail: 2010/11/10 09:59:06 WARNUNG (MultiPolygonRelation): 12000022.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/1239779 contains errors. 2010/11/10 09:59:06 WARNUNG (MultiPolygonRelation): 12000022.osm.gz: Polygon 4611686018427680884(436P)(23072094[436P]) carries role inner but is not inside any other polygon. Potentially it does not belong to this multipolygon. The generated polygon mentioned in the detail message has apparently been produced from http://www.openstreetmap.org/browse/way/23072094. This polygon is between 25.24875 and 25.44025 degrees longitude. Part of it is within your bounding box. Please try to extract this way from your tile file and see if the part that is within the bounding box makes sense. Or, to reduce the size of the file, first extract only this multipolygon from the input that you are feeding to splitter, and then split it. Then you should be able to load the tile in JOSM, possibly after some XML header tweaking. Marko
- Previous message: [mkgmap-dev] [PATCH v1] Multipolygon: do not warn about joining problems for ways outside the bbox
- Next message: [mkgmap-dev] [PATCH v1] Multipolygon: do not warn about joining problems for ways outside the bbox
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list