<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>geospatial on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/geospatial/</link><description>Recent content in geospatial 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/geospatial/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></channel></rss>