<br><br><div class="gmail_quote">On 26 April 2010 15:13, Jerry Clough - OSM <span dir="ltr"><<a href="mailto:sk53_osm@yahoo.co.uk">sk53_osm@yahoo.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div>GRASS seems to have some kind of Voronoi algorithm, but I find its interface very non-intuitive, so have not found it to try it out. This may be worth pursuing as an alternative route.<br>
<br>As an aside: I notice that virtually all postcode boundaries are obviously created in this way. For instance the Philips Street Atlas shows totally implausible boundaries along the River Trent in S. Notts. Given that postcode boundaries are ultimately determined by logistically sensible walks for postmen, in this case it's pretty safe to assume that the boundary is actually the river. What this means is that by applying a bit of local knowledge and the existing points it is possible to create better delineating zones in OSM than appear in current mapping. Whether this is a good thing to do, or not, I
leave for others to decide.<br></div><br></div></div></blockquote></div><br>I think that GEOS has now implemented both voronoi and Delaunay triangulation algorithms. I am not quite though that they have a Python Binding. Some part of GEOS is expose through the GDAL binding, but it is incomplete.<br>
<br>Emilie Laffray<br>