UPDATE: See here as a live map the top two features, which are the validation points:
The resulting 25 spikes and kickbacks out of 1900 Parish polygons for East Anglia are, at 1.3%, a ratio I might have envied in my digital data capture days (1982 - 92 here). Whilst they didn't affect the integrity of my project - Parishes are used as anchors for attributes by which wealth is measured, rather than as areas or perimeters per se - it seemed only natural to inform the Ordnance Survey creators of said deviations.
While I as a user can find and point to the errors, only the authors can fix it - indeed the Ordnance Survey's copyright notice only allows to copy the data under fair dealing - but returning to the download page I found no feedback mechanism other than a Customer Service email... But wait! They promote their data not only online but also in open events publicised by @plangfordsmith such as this one. I asked there how to feed back this information and a few emails later they check Socium's error polygons and firstname.lastname@example.org reply that these will be incorporated in the next update... rimshot
So that loops the loop:
- from @pterhaar unofficial announcement at Where2.0 early 2010 (thanks @stevenfeldman for this) to the actual release that April
- through augmenting a portion in East Anglia in my project, that lead to QCing late last year upon Socium's launch and uncovering errors
- to returning the error files this month to the Ordnance Survey, and finally the update of said data at the next data release cycle