Very good point. I guess if someone came across such a situation a nasty workaround would be to increase the --overlap value by enough to make the problem go away, though that would likely introduce other problems (memory usage, performance, nodes in > 4 areas, ...). A proper fix would require some extra analysis of the 'big ways' or 'big relations' (the splitter is already vaguely aware of these) to decide how best to deal with them. But that's not something I feel like implementing if it can be helped :) Chris SR> I'm not sure if this what Lambertus was thinking of but what about SR> polygons that completely encircle a tile, or are so big that they SR> cut across a tile in such a way that joining up the nodes in the SR> overlap area cuts across the tile. I don't think those things can SR> work. SR> SR> Probably doesn't happen for real though. Certainly no one has SR> reported a case where that appeared to happen. SR> SR> ..Steve SR>