Could splitter output a sensible polygon on runs without using one afterwards? Geofabrik doesn't change their polygons often, so if one runs it, splitter creates them, and one can reuse them for future runs, that would be the best I think... Maybe splitter could add 100m or 200m on generation, so small changes wouldn't matter (or does the polygon need to be exact?). On 29.11.2012 15:26, GerdP wrote:
" reg. overlapping polygons: I have a solution that works well for rectilinear polygons with only a few corners (like those that Henning uses), but it collapses when you use the polygons from geofabrik which contain diagonal lines. It's quite complicated to approximate such a polygon with rectangles , and I fear the result will never be near to what the user wants: Either it contains additional areas outside the original polygon or data is missing. So I plan to stop processing if such a polygon is used with a message like "Bounding polygon is too complex. Avoid diagonal lines!" Would that be okay for all? Gerd