Hi, Brett Henderson wrote: >> This was necessary in order to process replicate diffs which sometimes >> contain the same object twice, causing the old implementation to >> complain about change streams "not being sorted" (as "being sorted", >> for Osmosis, means that every object has to be greater than the >> previous).
> Which task was complaining? I had intended to create a new task which > would take a (sorted) change stream with full changes and collapse them > into a single change per entity. This new task would allow existing > tasks such as --apply-change to continue to be used as is. In my case it was --merge-changes which complained. I had downloaded some changes with --rri, and later did the same thing again and wanted to merge the two before then processing the unified result with osm2pgsql. Bye Frederik _______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
