One point … your colour scheme doesn’t help people who have vision problems
An option to toggle would be nice

any idea if/when full post code, lat long, street name, town, county etc may be made available FOC?

I also had trouble downloading the SSIS package for 2008 but got around this by making my own.

A note to all who might try this…

If you’re having trouble getting the data in to sql due to the large number of files then, rather than go through the pain of creatign a file loop, simply concatenate the raw files in Windows. e.g. extract the zip to a folder, then issue a “copy *.csv uk_postcodes.csv” (can also be performed from a sql task if you can use xp_cmdshell and need to automate this step).

Once you have a single file with all the data in (which no longer appears to have problems with the missing quotes as of 15th Feb 2011), you can simply import it in to SQL using the data import wizard (right click on destination DB and choose Tasks->import data). I would recommend adding a header for column names in the CSV first rather than getting [column 0] etc from the wizard as there isn’t one in the CSV by default but this is up to you. Beware the last column too as this will not fit in the default sql type of varchar(50). Change it to 100. Also put double quotes as the text delimiter

Perhaps rather than run immediately you might want to try saving as SSIS to the local server and then open from Visual Studio (BIDS). This will allow you to fine tune the import and you can delete all the columns you don’t want to import.

This system worked for me.

Dave

An updated version of this article is available at my other blog:

http://blog.endjin.com/2010/12/a-step-by-step-guide-to-mongodb-for-net-developers/

This one has images!

I’m a bit late to this post. The image files are missing. Is is possible to restore them?

Thanks

OS i believe works from their own Grid Reference system, and the long/lat co-ordinates may well be converted mathematically leading to a degree of error. Would love to have this confirmed though – a quick lookup of a postcode on Google maps shows the postcode in the right place but the equivalent long/lat pair being 4 or 5 streets out!

Having the lat / lng of a postcode is great but if the location to be identified is not exactly on that coordinate it is not in the postcode it should be. This made me realise there is probably a tolerance for each coordinate (say, 1 mile radius around the coordinate) but surely this cannot be the same for all postcodes?

If you can shed any light on this I’d appreciate it although you really have done enough for us already