Re: [Talk-GB] Postcode data

2013-03-12 Thread Brian Prangle
Aidan I've had a look at your list and would say it's way under - you only have 3 B27 codes and I've completed addressing this whole postcode area - I've not got every one complete but I'm sure there's far more than the 3 you're showing, including the one for my own house which is missing!

Re: [Talk-GB] Postcode data

2013-03-12 Thread Rob Nickerson
Brian, The list was of invalid postcodes. Hopefully everything you entered was a valid postcode (it seems that way given that only 3 invalid B27 postcodes appear in the list). Rob On 12 March 2013 22:37, Brian Prangle bpran...@gmail.com wrote: Aidan I've had a look at your list and would

Re: [Talk-GB] Postcode data

2013-03-05 Thread Aidan McGinley
Rob, Probably, I'm a little busy at the moment so not really going to get round to doing it in the short term. Can probably rustle up a list mapping the ways and nodes to the incorrect postcode fairly quickly which would probably help? Aidan On 1 March 2013 17:35, Rob Nickerson

Re: [Talk-GB] Postcode data

2013-03-01 Thread Aidan McGinley
* How accurate is the data already in OSM? Interesting question Rob, as of today there's approximately 200,000 ways or nodes tagged with postcodes in OSM, this is made up of about 29,000 unique postcodes. Those numbers are not 100% accurate as my bounding box for getting the data overlaps a bit

Re: [Talk-GB] Postcode data

2013-03-01 Thread Rob Nickerson
That's an interesting list for anyone who is concerned with data cleansing! Some of the results are because only the first part of a postcode has been entered, however even these have numerous formats (e.g. CV3, CV3 ???, CV3 ///). For the other errors, it tends to be typos (e.g. CO!6 7BJ, where !

Re: [Talk-GB] Postcode data

2013-02-28 Thread Robert Whittaker (OSM lists)
On 27 February 2013 09:03, Andy Allan gravityst...@gmail.com wrote: On 26 February 2013 22:08, Aidan McGinley aidmcgin+openstreet...@gmail.com wrote: is the actual output that would get loaded onto OSM. Please don't load this data into OpenStreetMap. It's not a good idea. 1) The source data

Re: [Talk-GB] Postcode data

2013-02-28 Thread Aidan McGinley
I haven't had time to do the analysis yet Robert, I've been focussing on fixing the issues I've already identified, once they are done I'll do something more detailed. But at a high level these are the numbers: 95 total buildings with an existing postcode tag (after removing ways mapped to more

Re: [Talk-GB] Postcode data

2013-02-28 Thread Steve Doerr
On 28/02/2013 12:27, Aidan McGinley wrote: 12 of these buildings only have the first part of the postcode. All of these partially match what is output by the script, for example way 5042255 is tagged in OSM as SW15 and the script identifies it as SW15B2U. Hopefully that's a typo for

Re: [Talk-GB] Postcode data

2013-02-28 Thread Aidan McGinley
Steve, yes you're right that was a typo on my part :) Here is the full analysis of the problematic ways 61130908 SW2 4RT in OSM vs SW2 4SG from ONS 112682060 in OSM SW1 2SE vs SW1V 2SE from ONS 139941192 in OSM vs SE11 5EN vs SE11 5EF from ONS 116957518 in OSM vs SW1V 1DX vs SW1P 1JQ from ONS

Re: [Talk-GB] Postcode data

2013-02-28 Thread Rob Nickerson
Interestingly out of the 95 you also identified 2 postcodes that are incorrect in OSM... raising the obvious questions: * How accurate is the data already in OSM? * Should imports be compared to 100% accuracy or a more realistic measure of OSM accuracy? Rob

Re: [Talk-GB] Postcode data

2013-02-27 Thread Andy Allan
On 26 February 2013 22:08, Aidan McGinley aidmcgin+openstreet...@gmail.com wrote: is the actual output that would get loaded onto OSM. Please don't load this data into OpenStreetMap. It's not a good idea. 1) The source data appears to be heavily overprocessed. Users should note that postcodes

Re: [Talk-GB] Postcode data

2013-02-27 Thread Kevin Peat
Aidan, On 27 Feb 2013 09:04, Andy Allan gravityst...@gmail.com wrote: Please don't load this data into OpenStreetMap. It's not a good idea. 100% agree with Andy. To be acceptable your script would need to do at least as good a job as mappers could do by hand which I don't think is possible

Re: [Talk-GB] Postcode data

2013-02-27 Thread Aidan McGinley
Thanks for the feedback Andy, I'll tackle each point below, @Kevin hopefully #3 should address your concerns about accuracy 1) The source data appears to be heavily overprocessed. This only applies to data other than the postcode centroids, such as the Census Output Areas and other

Re: [Talk-GB] Postcode data

2013-02-27 Thread Aidan McGinley
That's right Ed, if a building already has a postcode I won't be changing it. I'm actually outputting them separately and using them for some quality assurance. I'd be interested to know the two postcodes you are referring to just to check how they look in the source data. On 27 February 2013

Re: [Talk-GB] Postcode data

2013-02-27 Thread Kevin Peat
Aidan, On 27 February 2013 11:12, Aidan McGinley ... I've only included the highest quality data which is postcode centroids that fall within a building within the area of the postcode... Does that allay any concerns about the import? Does the centroid always fall within the postcode area?

Re: [Talk-GB] Postcode data

2013-02-27 Thread Aidan McGinley
Kevin, Yes, the centroid falls within the postcode area for the highest quality indicator by definition. To be marked in the highest quality data set, the centroid must fall inside a building within the postcode area (see the user guide that accompanies the data for more details). These high

Re: [Talk-GB] Postcode data

2013-02-27 Thread Rob Nickerson
Hi Andy, Aidan approached the talk-gb mailing list last month about this postcode idea [1]. A discussion was held, and from the back of this several changes were made (mainly related to reducing the size of the import to ensure that only the very best data was used, but also to ensure that QA was

Re: [Talk-GB] Postcode data

2013-02-26 Thread Aidan McGinley
Time for an update on this. I've done my first proper test run of this today using the latest ONS file. The test was run over an area of about 60 square miles in southwest London. There's about 3000 postcodes in the result set which I'm pretty impressed with assuming they are all valid, so we

Re: [Talk-GB] Postcode data

2013-01-21 Thread Aidan McGinley
@Brian - Yes I need to formulate how to QA this. I'd like to automate the QA as much as possible but having some elements done manually is obviously beneficial and the more people that can cast their eye over it the better. Any volunteers please do let me know, and also if anyone has any ideas

Re: [Talk-GB] Postcode data

2013-01-18 Thread Matt Williams
On 15 January 2013 19:28, Rob Nickerson rob.j.nicker...@gmail.com wrote: Hi Matt, I'm getting results from other cities in the Land Registry tool. Should this apply the same +- 0.1 degrees logic? Would also be nice if you could add the edit this way in external links (like those on a way's

Re: [Talk-GB] Postcode data

2013-01-18 Thread Matt Williams
On 17 January 2013 23:01, Rob Nickerson rob.j.nicker...@gmail.com wrote: I would imagine that this would add a fair number of postcodes, and although those interested in address lookup can just use the centroid database without needing to go to OSM, this requires knowledge of the database

Re: [Talk-GB] Postcode data

2013-01-17 Thread Robert Whittaker (OSM lists)
On 16 January 2013 13:04, Brian Prangle bpran...@gmail.com wrote: You might like to get a volunteer to check a pilot import that's limited within a manageable area - suggest a limited range of postcodes Another useful check would be to apply your matching over the OSM database, and pull out all

Re: [Talk-GB] Postcode data

2013-01-17 Thread Rob Nickerson
I would imagine that this would add a fair number of postcodes, and although those interested in address lookup can just use the centroid database without needing to go to OSM, this requires knowledge of the database (which non-UK developers might not have) and does not link postcodes back to

Re: [Talk-GB] Postcode data

2013-01-16 Thread Brian Prangle
Hi Aidan You might like to get a volunteer to check a pilot import that's limited within a manageable area - suggest a limited range of postcodes Regards Brian On 15 January 2013 11:32, Aidan McGinley aidmcgin+openstreet...@gmail.comwrote: @Rob yes I had seen that. It is a great tool, but

Re: [Talk-GB] Postcode data

2013-01-15 Thread Aidan McGinley
@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

Re: [Talk-GB] Postcode data

2013-01-15 Thread Rob Nickerson
Hi Matt, I'm getting results from other cities in the Land Registry tool. Should this apply the same +- 0.1 degrees logic? Would also be nice if you could add the edit this way in external links (like those on a way's page on OSM.org). Cheers, Rob ___

Re: [Talk-GB] Postcode data

2013-01-14 Thread Rob Nickerson
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

[Talk-GB] Postcode data

2013-01-13 Thread Aidan McGinley
Been toying with some ideas for how to use the ONS Postcode data[1]. One idea that I have been exploring is to check if the value for the centre of the postcode is inside a closed way, and if so then tag that way with the appropriate addr:postcode. I mocked up a script to check this using the

Re: [Talk-GB] Postcode data

2013-01-13 Thread Brian Prangle
Hi Aidan If you were to do this then two things you should consider: 1. only tag closed ways where tag is building=xx AFAIK water and woods and gardendens etxc don't have postcodes 2. how to treat buildings where there is already a postcode and if correct/incorrect Regards Brian On 13

Re: [Talk-GB] Postcode data

2013-01-13 Thread Chris Hill
On 13/01/13 15:21, Aidan McGinley wrote: Been toying with some ideas for how to use the ONS Postcode data[1]. One idea that I have been exploring is to check if the value for the centre of the postcode is inside a closed way, and if so then tag that way with the appropriate addr:postcode. I

Re: [Talk-GB] Postcode data

2013-01-13 Thread Aidan McGinley
Thanks for the feedback. @Brian - The script is filtering to only include closed ways, although I wasn't sure whether to restrict it to just ones with building=xxx, as this would mean some of the amenity=XXX type tags would get missed. It's trivial to do though should this go ahead. Had not

Re: [Talk-GB] Postcode data

2013-01-13 Thread Rovastar
Postcodes don't have to assigned to buildings in OSM. In the last couple of weeks I have not added any postcodes to buildings but I have added postcodes to amenities as areas including stadiums, schools, hospitals and police stations. None of these were buildings. Once you have a plan here then

[Talk-GB] Postcode data to be free in 2010

2009-12-09 Thread Dave F.
*I'm sure this is old news to some of you, but... **http://news.bbc.co.uk/1/hi/technology/8402327.stm Cheers Dave F. * ___ Talk-GB mailing list Talk-GB@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-gb

[Talk-GB] Postcode data to be free in 2010 - well not exactly.....

2009-12-09 Thread Peter Miller
On 9 Dec 2009, at 15:18, Dave F. wrote: *I'm sure this is old news to some of you, but... **http://news.bbc.co.uk/1/hi/technology/8402327.stm Arhhh. but Correction - Poscodes will not be free http://giscussions.blogspot.com/2009/12/correction-poscodes-will-not-be-free.html The government

Re: [Talk-GB] Postcode data to be free in 2010 - well not exactly.....

2009-12-09 Thread Tom Hughes
On 09/12/09 21:29, Peter Miller wrote: *I'm sure this is old news to some of you, but... **http://news.bbc.co.uk/1/hi/technology/8402327.stm Arhhh. but Correction - Poscodes will not be free http://giscussions.blogspot.com/2009/12/correction-poscodes-will-not-be-free.html I don't think