That could be done but it's not straightforward; you'll get a lot of overlapping postcode sectors and sectors with non-contiguous parts. GeoLytix produced an open dataset like that some time ago: http://blog.geolytix.net/tag/postcode-boundaries/
Owen On 26 September 2016 at 09:39, Colin Smale <colin.sm...@xs4all.nl> wrote: > How about deriving polygons for the postcode sector level (XX9 9) from the > centroid point cloud, and adding the polygons to OSM? I don't know how many > that would give, but it would be a whole lot less than 500k and still at a > very usable level. > > > //colin > > On 2016-09-26 10:01, Gervase Markham wrote: > > On 25/09/16 21:47, Owen Boswarva wrote: > > I can't see any reason why there should be a problem using Code-Point > Open in OSM, now that Ordnance Survey has applied the Open Government > Licence in place of its own licence. If you read further down, the wiki > page gives examples of OSM projects that use Code-Point Open. > > > OK, that's good news. What's the quickest route to getting Nominatim to > understand this data set? File a Nominatim bug to get the search engine > to import the data set directly? Or add 500,000ish points to OSM itself > with something like type = "postcode_centre"? > > Gerv > > > _______________________________________________ > Talk-GB mailing list > Talk-GB@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-gb > > > _______________________________________________ > Talk-GB mailing list > Talk-GB@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-gb > >
_______________________________________________ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
