I'm wondering if this FAQ is still up to date, which notes that the postcodes were computed in October 2012 and haven't been updated since. http://wiki.openstreetmap.org/wiki/Nominatim/FAQ#My_postcode_is_missing.2Fwrong_but_I.27ve_fixed_it_in_the_OSM_data._What_is_wrong.3F There are many duplicate tickets about postcodes in Trac and Github issue trackers.
I'd much prefer to load the OS open data as a separate list into Nominatim, otherwise it'll be a nightmare trying to update the OSM data when the next release of the OS open data comes out. Adding postcodes to specific buildings in OSM is still useful to produce more accurate geocoding and reverse geocoding results. Shaun > On 26 Sep 2016, at 09:39, Chris Hill <[email protected]> wrote: > > Please do not add postcode centroids to the map. They are not real, do not > exist and do not belong in the OSM DB. > > On 26 September 2016 09:01:38 BST, Gervase Markham <[email protected]> > 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 > [email protected] > https://lists.openstreetmap.org/listinfo/talk-gb > <https://lists.openstreetmap.org/listinfo/talk-gb> > > -- > Cheers, Chris (chillly) > _______________________________________________ > Talk-GB mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk-gb
_______________________________________________ Talk-GB mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-gb
