<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>spatial on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/spatial/</link><description>Recent content in spatial 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, 14 Mar 2012 22:11:00 +0000</lastBuildDate><atom:link href="https://www.adathedev.co.uk/tags/spatial/index.xml" rel="self" type="application/rss+xml"/><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><item><title>GB Post Code Geographic Data Load to SQL Server using .NET</title><link>https://www.adathedev.co.uk/2011/01/gb-post-code-geographic-data-load-to.html</link><pubDate>Mon, 24 Jan 2011 08:38:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/01/gb-post-code-geographic-data-load-to.html</guid><description>Ordnance Survey now make available a number of mapping data/geographic datasets to download for free, allowing unrestricted use for commercial and non-commercial use. One of these is the Code-Point Open dataset, which gives a precise geographic location of each post code in Great Britain as a CSV file.
This file contains the Easting and Northing coordinates for each postcode. You may want to convert these to Latitude/Longitude coordinates to then load into a GEOGRAPHY column in SQL Server (as of 2008) and do all kinds of spatial wizardry in the database.</description></item></channel></rss>