[OSM-dev] Data corruption :) II

[Frederik Ramm]

Hi,

Stefan de Konink wrote:
>> My suggestion for your current issue would be to leave it alone until we
>> have API 0.6 in place, because with our current infrastructure you are
>> fighting windmills - every day new inconsistencies are created. With any
>> luck, that will be a thing of the past once we have full transactions
>> with API 0.6; so AFTER that is active we can prepare one big "fix legacy
>> inconsistencies" operation and remove them once and for all.
> 
> Not acceptable.

I cannot see the logic behind this. You will not be able to force 
consistency onto 0.5; if your software cannot work with inconsistencies 
then it cannot work with the dumps/diffs we produce until 0.6. So either 
you find a way to handle these things on your side, or you will not be 
able to run your software until 0.6 anyway. Even if you do a mass change 
now to fix the existing inconsistencies, each day will produce new ones, 
and your software will fall over. Unless you find a way to deal with the 
inconsistencies, in which case you'd have to tell us why exactly 15k 
inconsistencies are "not acceptable" while a few hundred are.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"