[osmosis-dev] --simplify-change with a conflictResolutionMethod

Andrew Harvey andrew.harvey4 at gmail.com
Sun Jan 8 01:15:58 GMT 2012


I tried editing
osmosis-0.40.1/core/src/main/java/org/openstreetmap/osmosis/core/sort/v0_6/SortedHistoryChangePipeValidator.java
at line 49 to be > rather than >=, altering the validation hence
removing the error message. This seems to remove one of the duplicated
<way items (which is what I want for --simplify-change), in my case it
removed the first one.

On Sun, Jan 8, 2012 at 9:38 AM, Andrew Harvey <andrew.harvey4 at gmail.com> wrote:
> I have the following .osc file. The important part is it has two ways
> with both the same id and version, except different dates and
> changesets.
>
> <?xml version='1.0' encoding='UTF-8'?>
> <osmChange version="0.6" generator="Osmosis 0.40.1">
>  <modify>
>    <way id="1" version="1" timestamp="2011-06-25T18:39:36Z" uid="1"
> user="user" changeset="1">
>      <nd ref="1"/>
>      <nd ref="1"/>
>      <tag k="foo" v="bar"/>
>    </way>
>  </modify>
>  <modify>
>    <way id="1" version="1" timestamp="2011-06-25T19:39:36Z" uid="1"
> user="user" changeset="2">
>      <nd ref="1"/>
>      <nd ref="1"/>
>      <tag k="foo" v="bar_bar"/>
>    </way>
>  </modify>
> </osmChange>
>
> Running it through osmosis with,
>
> osmosis --read-xml-change in.osc --sort-change --simplify-change
> --write-xml-change out.osc
>
> fails.
>
> Can it be expected that --simplify-change be able to handle this and
> offer a conflictResolutionMethod argument like --merge? Or is there
> some other way to handle this case?



More information about the osmosis-dev mailing list