Hi all,
I've recently found myself doing the same exercise as another poster on this thread to find potentially bogus entries - averaging postcodes per region and finding ones that are significantly outside where they belong.
This raises a question though, let's say I believe these codes are suspect and so does everyone else (indeed I've checked one or two on other websites which use more "official" postcode data), should these codes be removed or at least marked somehow as bogus?
If I'm going to use this data in a project of my own I could remove these entries having manually checked them, but then the data correction isn't being done in a shared way along with the data collection.
What's the best way of setting a feedback mechanism like this up? If necessary I don't mind helping out?
Russ
The supported way of reporting a postcode bad is by clicking on it in the interface and filling in the form. I initially thought that you could try doing a POST to fill in the form. Unfortunately this requires the ID of the postcode in our database and although you could find that out from a bounding box request for where you think the incorrect postcode is, it isn't ideal.
Clearly this is not manageable for large numbers of reports, so we should probably have some sort of interface that could be scripted. We have held back from producing an API as we want to be sure that people have found a location by clicking on the map, so will definitely not implement an API to insert a postcode, but having an API to report a postcode as bad should be fine (unless it results in more work for us in dealing with the reported postcodes).
More work on tools that we can run on the dataset would probably be more useful, and to this end I think that we should make the code that the site runs available to other people as we don't appear to have the resources that we would like to work on the site. Then interested parties such as yourself can work on improving the infrastructure behind the site.
David
On Dec 8, 2007 10:58 PM, russellallen <russellatthevegmarket.co.uk> wrote:
Hi all,
I've recently found myself doing the same exercise as another poster on this thread to find potentially bogus entries - averaging postcodes per region and finding ones that are significantly outside where they belong.
This raises a question though, let's say I believe these codes are suspect and so does everyone else (indeed I've checked one or two on other websites which use more "official" postcode data), should these codes be removed or at least marked somehow as bogus?
If I'm going to use this data in a project of my own I could remove these entries having manually checked them, but then the data correction isn't being done in a shared way along with the data collection.
What's the best way of setting a feedback mechanism like this up? If necessary I don't mind helping out?
Russ
View this message in context: http://www.nabble.com/Marking---flagging-incorrect-entries-tp14233507s26798p... Sent from the NPEmap - Talk mailing list archive at Nabble.com.
npemap-talk@lists.urchin.earth.li