@Rob yes I had seen that. It is a great tool, but as you say it's difficult to be absolutely sure that what you get back is accurate
To summarise what I'll be looking at doing Filter the following from the ONS Postcode data: - Postcodes which have a date of termination set - Postcodes whose centroid is shared with other postcodes - Postcodes which have a quality indicator other than "Within the building of the matched address closest to the postcode" Then match these filtered centroids to ways from Openstreetmap that have the following criteria: - The way is closed - The postcode centroid is inside the way - The way does not already have a "addr:postcode" tag - The way is tagged building=* There are future enhancements that can be done around tackling ways tagged amenity=* as per Rovastars comments, and reporting on postcode accuracy but the above is enough for the initial version I think. If there are no objections to the above, I will start work on optimizing the script and get in touch with the import mailing list to discuss how to actually tackle the task of importing the data. On 14 January 2013 19:54, Rob Nickerson <[email protected]> wrote: > Hi Aidan, > > Sounds like you have thought this through to ensure that this "import" > will work well in practice. I would be more satisfied if imports were to > closed ways with building=* only (as mentioned by others). > > Have you seen the Land Registry 'price paid' open data that includes > addresses and postcodes. Matt had a go at creating a simple tool that > matches their data to OSM address tags [1]. It's a great start, but be > aware that the "nearby houses" only matches on street name and number so > you can end up with addresses in different towns. Also it's quickest if you > specify at least the first number after the space (e.g. CV4+8) > > Rob > > > [1] http://milliams.dev.openstreetmap.org/postcodefinder/landregistry/ >
_______________________________________________ Talk-GB mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-gb
