> > WanMil, > >> I will try to reproduce your errors and to improve the error messages. > > I wasn't complaining about the quality of the messages, merely telling > you that they were happening.
You should complain :-) Logging fake ids does not help anyone to have a look on the OSM data. The warnings you see indicate wrong OSM data (an inner way intersects an outer way) OR it indicates problems with the tiles. In any case one must have the chance to check that. > >> Which dump do you use for your Baltic map? > > I grabbed it with XAPI (a mistake as it was about 2GB uncompressed) and > have merged some other stuff into it. > > So to make life easy, I have uploaded a tile that you can try to: > > http://www.smartavionics.com/OSM/63240006.osm.gz > > That tile has land in the bottom half and a few islands. > > Mark That's great. I will grab it now and check it tomorrow. I suppose that the problem is the autoclosing mechanism. The new multipolygon code tries to close ways by just readding the first point. I think I must add a bounding box check (if first and last point of an unclosed polygon touches the bounding box then the polygon is complemented by the bounding box - otherwise the simple algorithm is taken) WanMil _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
