Opened 7 years ago

Last modified 2 years ago

#4175 new defect

failed to append changeset

Reported by: ieskok Owned by: jburgess777@…
Priority: minor Milestone:
Component: osm2pgsql Version:
Keywords: Cc:

Description

osm2pgsql fails when appending a changeset file: ... Reading in file: test.osc osm2pgsql: parse-xml2.c:101: StartElement?: Assertion `xlon' failed. Aborted

Revision: 27409 test file: <?xml version='1.0' encoding='UTF-8'?> <osmChange version="0.6" generator="osmconvert 0.5V" timestamp="2012-01-07T09:10:02Z"> <delete>

<node id="43580710" version="2" timestamp="2011-08-27T03:32:11Z" changeset="9134544" uid="29320" user="Kom.pa"/> <node id="43580712" version="2" timestamp="2011-08-27T03:32:11Z" changeset="9134544" uid="29320" user="Kom.pa"/> <node id="43580716" version="2" timestamp="2011-08-27T03:32:11Z" changeset="9134544" uid="29320" user="Kom.pa"/>

</delete> </osmChange>

Change History (2)

comment:1 Changed 7 years ago by amm

osm2pgsql currently requires that nodes contain lat / lon info in the delete action.

It looks like osmconvert does not add lat / lon to nodes for deletes, which is what chokes osm2pgsql.

comment:2 Changed 2 years ago by pnorman

ieskok, does this happen with modern osm2pgsql? (0.90.0 or later)

Note: See TracTickets for help on using tickets.