Lithuanian address cadastre information was opened in October last year. We started importing the data to OSM straight away. Most (90-95%) of addresses could be imported automatically (taking care of existing addresses, putting address on a building when there is only one candidate, removing any excess addresses). Remaining addresses were added semi-automatically using JOSM remote control. This increased the number of addresses from 300 thousand to 1.1 million.
Here is a video of the progress: https://www.youtube.com/watch?v=Eebl0xxT-nM
But we quickly found out that importing addresses is the least difficult part. We have a number of QA rules in Lithuania, including:
Street name information is part of the dataset being opened, but it is way harder to import that data automatically as ways have to be created, combined, split, moved etc. Another thing was that OpenStreetMap data of street geometry is way more precise, so in some cases only human can correctly specify the geometry of the street. Therefore it was decided to go through ALL streets (highway=residential,unclassified,living_street) and add name or noname tag. Several mappers participated using simple report giving JOSM remote control to streets which needed review closest to their starting point. Each mapper started from their own point. This way more than 25000 ways have been reviewed and necessary data added.
Here is a video of name adding progress: https://www.youtube.com/watch?v=Zc3TQQhO_rA
Admin boundary info was also in the opened dataset. It is also being fixed manually. Still in progress.
Comment from IpswichMapper on 5 April 2021 at 21:30
Good work! Always nice to see address imports
Comment from Jedrzej Pelka on 6 April 2021 at 20:57
Polish OSM community has this map for the quality assurance of address points: http://v3.mrowka.org/adresy/
The yellow stars are for addresses without the associated named street in vicinity. The pink stars are for addresses without any road in vicinity.
Does Lithuanian community have a similar visualisation, apart from the videos above?
Comment from Tomas Straupis on 6 April 2021 at 21:13
Maps visualising types/positions of errors look cool, but they do not help the general process of QA. Idea is that wanted quality level must be reached and then maintained, therefore with each new automated error check introduced we:
This means that we mostly need a LIST, rather than a MAP.
Therefore we do have a LIST in our patrolling web-application, together with changeset approval and synchronisation with external datasets.
This also means that there are NO address errors which would live longer than one day.
(some too widespread, too hard to fix, or less important errors are on a different stream: some number of those ~10 are calculated and fixed daily, examples of such errors would be missing tracktypes, rivers with too sharp angles between segments, missing admin boundaries for “addr:city” etc. but those would once again be LISTS, not MAPS, and that is by design)
Comment from Tomas Straupis on 6 April 2021 at 21:15
Having a list of errors also helps improving the homogeneity of the data.
Comment from MapMakinMeyers on 10 April 2021 at 14:54
do you have the wiki for the import, or the raw source? Thanks!
Comment from Tomas Straupis on 10 April 2021 at 16:11
No wiki. Data comes from geofabrik.de. Created with QGIS.