On Thu, 2010-01-21 at 11:29 -0800, Dane Springmeyer wrote:
> On Jan 21, 2010, at 5:51 AM, Mike Warren wrote:
>
> > Jon Burgess <jburgess...@googlemail.com> writes:
> >
> >> If I remember correctly this error occurs when you try to import two
> >> data sets which contain some overlapping data. In your case it
> >> appears
> >> that relation ID 284132 appears in both the data extracts. Only the
> >> slim
> >> mode keeps a copy of this node/way/relation data and triggers this
> >> error.
> >
> > FWIW, I had a similar error (duplicate node) importing just the
> > alberta.osm.bz2 CloudMade extract from December 25th; non-slim mode
> > works fine.
> >
>
> Same error here as well with the haiti extracts from geofabrik today.
It seems there are two versions of a way in the haiti data:
$ bzip2 -dc 2010-01-21-19-30.osm.bz2 | grep 28418855
<way id="28418855" version="18" timestamp="2010-01-21T05:58:07Z" uid="16591"
user="neuhausr" changeset="3672284">
<way id="28418855" version="19" timestamp="2010-01-21T11:07:28Z" uid="1164"
user="dmgroom" changeset="3673648">
I don't know why they are both there, it maybe a bug in the export
process.
One idea which was proposed for osm2pgsql was to record and use the
version field when applying updates. I'm not sure if this would help in
this case, we don't expect to find multiple versions when importing a
single file.
Jon
_______________________________________________
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
