[OSM-dev] Minute Diffs Broken
Brett Henderson
brett at bretth.com
Tue May 5 10:10:52 BST 2009
Brett Henderson wrote:
>>> Also, there's a potential flaw with this approach. Lets say I
>>> create node 100 with version 1 in changeset 10 in Potlatch and leave
>>> my changeset open. You then come along with JOSM and edit node 100
>>> creating version 2 within changeset 11 and close your changeset
>>> immediately. Osmosis will pick up changeset 11 after 5 minutes and
>>> distribute node 100 version 2. A day later Osmosis will pick up
>>> changeset 10 and distribute it node 100 version 1.
>>
>> Ouch, I hadn't thought of this, but of course you are right. - But
>> now that the XML contains version numbers, would it not be the
>> superior approach anyway to base --apply-change on version numbers
>> anyway?
>
> Probably. Like much of osmosis it is intentionally dumb which leads
> to it being predictable and easy to maintain. Patches welcome :-)
One thing I forgot to mention. I wasn't just referring to the
--apply-change task. It will also impact other tasks such as
--write-pgsql-change, --write-apidb-change, etc which impacts systems
such as ROMA. It may also impact other downstream systems such as
mapnik rendering and XAPI.
More information about the dev
mailing list