I don't care so much about efficiency if the results are better. if we can't support it maybe it's better to drop incomplete polygons. You asked earlier for some other relation question. I would say a maximum of 3 levels is just good enough. Also you have to be careful of loops. Relations can contain other relations and even themselves. for map making most are not really important since they are just collections and have no useful tags for a garmin map. as an example I use it to have all ways and relations of an import in a single relation. On 13 Sep 2009, at 12:21 , Chris Miller wrote:
I've grabbed a copy of this test case and when I find the time will see what can be done about it in the splitter. It sounds like it might be quite a tricky problem to solve efficiently though.
SR> On 12/09/09 23:30, Apollinaris Schoell wrote: SR>
this branch fixes the polygon in one tile. big improvement! here is a tricky small example where it still fails when split into 2 tiles. http:/apo42.dyndns.org/shastalake.tgz SR> That appears to be a good test case. SR> SR> I had to remove the bounds element as that just selects a tiny area SR> within the lake, but then the whole lake could be seen when SR> compiling the un-splitted file. SR> SR> After splitter is run then the 18800010.img file does not look good, SR> although JOSM shows the lake fairly well. SR> SR> ..Steve SR>
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev