search

lpalli / openaddresses

Automatically exported from code.google.com/p/openaddresses
0 stars 0 forks source link

OSM Data Quality #20

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It seem sthat everytime a browse around to have a look at adresses coming
from OSM, I run into very low quality data. Quite often importnat fields
such as the street names are missing. 
It might be worth considering performing a few quality checks on our
database then:
- Either perform an automatic correction (i.e Based on the spatial location
to identify the country we're in)
- Prepare "tasks" to be checked and corrected by the community. These could
be listed on the wiki and the contributors may spend some time correcting
them using our "Address corrector" Tool.

Original issue reported on code.google.com by jlmise...@gmail.com on 21 Mar 2010 at 4:46

GoogleCodeExporter commented 9 years ago 
I strongly agree. We need to make everything in order to improve the quality of 
the
OSM data.
From a technical perspective, I would use the power of a spatial SQL database in
order to identify the potential issues (e.g. select id from address where city 
is null).
We need also to have reference data, like country, city, region, canton or 
department
boundaries that can be used to make spatial checks.
We have now to organize a bit this data quality insurance work. Do you have 
proposals ?

Original comment by cedric.m...@gmail.com on 21 Mar 2010 at 5:47