Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-11 Thread michael spreng
Hi Wiktor I maintain an import of public transport stops in Switzerland. These public transport stops have a unique identifier (uic_ref) which is used for example in time table applications, so we include it. But I spend quite a bit of time maintaining these refs, as mappers usually don't know

[OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Wiktor Niesiobedzki
Hi, In Poland we have quite a few addresses imported from government sources for quite long time, but as time goes on, changes are made to the source databases, and local communities don't have any viable tools, to track, what has changed in source. In case of city of Skarżysko-Kamienna, local

Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Marc Gemis
As far as I know, the tools that generates the missing address in Flanders, does this purely based upon addr:street and addr:housenumber. Look at [1], and fill in e.g. 1980 or 2610 as postal code , check Load OSM data and press update Documentation for end-users can be found under the

Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Jason Remillard
Hi Wiktor, I don't think an address tag is needed or desirable. The best way of doing this is to compare versions of the official data (perhaps every 6 months), making a list of things that have changed so that they can be examined in OSM. Of coarse the big issue is that the matching is not

Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Marc Gemis
On Sat, Jan 10, 2015 at 1:38 PM, Wiktor Niesiobedzki o...@vink.pl wrote: 3. Addresses change. Currently there is no way to isolate the situation, that a point in OSM needs a change of street name, city name or housenumber, because this name changed has changed in the source. I can't mark all

Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Wiktor Niesiobedzki
I'd like to add a few words on the topic. First - the state of the OSM and sources in Poland: 1. Data sources and OSM use different standard of naming of the streets and not always it can be mapped automatically 2. Addresses change - some addresses change cities, some change streets, some gain

Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Mateusz Konieczny
Documenting invalid entries in other database (adding elements only with addr:ref and source:addr) is a bad idea - such entries should not appear in OSM database. Also, there seems to be a project with a similar goal, called BANO (Base d'Adresses Nationale Ouverte). AFAIK it is covering France

Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Simon Poole
Addresses are trivial to match by geographic proximity and the actual values and given that addresses are one of the things that are quite likely to move and be attached to other objects (and loose any non-standard ref tags in the process) any tool that relies solely on such ref tags is going to

Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Wiktor Niesiobedzki
2015-01-10 16:44 GMT+01:00 Jason Remillard remillard.ja...@gmail.com: Hi Wiktor, I don't think an address tag is needed or desirable. The best way of doing this is to compare versions of the official data (perhaps every 6 months), making a list of things that have changed so that they can

Re: [OSM-talk] Keeping imported data updated with source changes

2015-01-10 Thread Jason Remillard
Hi Wiktor, If you want to automated this, you will need a database outside of OSM, that stores the matches between the municipiality and OSM addresses. the municipal differences over time, the OSM differences over time. The same underlying matching algorithm previously described is used to create