<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ordnance Survey on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/ordnance-survey/</link><description>Recent content in Ordnance Survey on AdaTheDev Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>adathedev@gmail.com (Adrian Hills)</managingEditor><webMaster>adathedev@gmail.com (Adrian Hills)</webMaster><lastBuildDate>Wed, 13 Mar 2013 23:09:00 +0000</lastBuildDate><atom:link href="https://www.adathedev.co.uk/tags/ordnance-survey/index.xml" rel="self" type="application/rss+xml"/><item><title>GB Post Code Importer Conversion Accuracy Fix</title><link>https://www.adathedev.co.uk/2013/03/gb-post-code-importer-conversion.html</link><pubDate>Wed, 13 Mar 2013 23:09:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2013/03/gb-post-code-importer-conversion.html</guid><description>In a post last year (Ordnance Survey Data Importer Coordinate Conversion Accuracy) I looked into an accuracy issue with the conversion process within the GeoCoordConversion DLL that I use in this project (blog post). Bottom line, was that it was a minor with an average inaccuracy of around 2.5 metres and a max of ~130 metres by my reckoning. I&amp;rsquo;ve since had a few requests asking if I can supply an updated GeoCoordConversion DLL with fixes to the calculations.</description></item><item><title>Ordnance Survey Data Importer Coordinate Conversion Accuracy</title><link>https://www.adathedev.co.uk/2012/03/ordnance-survey-data-importer.html</link><pubDate>Wed, 14 Mar 2012 22:11:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2012/03/ordnance-survey-data-importer.html</guid><description>Update 13 March 2013: Please see latest blog post (fix) on this here.
Thanks to a comment on my original post around my project that imports Ordnance Survey CodePoint data into SQL Server, I was made aware of a potential issue with the (awesome) third party GeoCoordConversion DLL I use to convert the Eastings/Northings coordinates supplied in the Ordnance Survey data files, into Latitude/Longitude coordinates. The issue relates to an inaccuracy in the conversion process, specifically to do with integer divisions instead of double.</description></item><item><title>OS Data Importer Supports Scale Gazetteer Dataset</title><link>https://www.adathedev.co.uk/2011/03/os-data-importer-supports-scale.html</link><pubDate>Sun, 27 Mar 2011 21:54:00 +0100</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/03/os-data-importer-supports-scale.html</guid><description>I&amp;rsquo;ve just pushed some updates to GitHub for the Ordnance Survey Data Importer .NET app I&amp;rsquo;ve been working on every now and then (see my previous posts: GB Post Code Geographic Data Load to SQL Server using .NET and OS CodePoint Data Geography Load Update).
Aside from a little re-jigging to potentially pave the way to load more Ordnance Survey data files to SQL Server in the future, it now supports importing the 1:50000 Scale Gazetteer data file to SQL Server (available to download from here).</description></item></channel></rss>