ginal-Nachricht
> Datum: Fri, 12 Aug 2011 13:35:07 +0200
> Von: "Peter Körner"
> An: Frederik Ramm
> CC: mar...@gmx.eu, dev@openstreetmap.org
> Betreff: Re: [OSM-dev] osm2pgsql: parse-xml2.c:100: StartElement: Assertion
> `xlon\' failed.
> Am 31.05
Am 31.05.2011 00:25, schrieb Frederik Ramm:
Hi,
mar...@gmx.eu wrote:
osm2pgsql persists on getting coordinates (lon/lat) even when it
reads an .osc file and the OSM object in question is to delete.
Which software generates .osc files that do *not* have lon/lat
attributes on nodes to be delete
Hi,
Jonas Häggqvist wrote:
Well. Maybe. This changed caused nodes to not be deleted from my
database, since I was applying a bbox the change was getting discarded
since the bbox check failed.
So either the lon/lat *is* needed, or the bbox check should be skipped
for the delete action. Someon
On 31-05-2011 00:25, Frederik Ramm wrote:
Hi,
mar...@gmx.eu wrote:
osm2pgsql persists on getting coordinates (lon/lat) even when it
reads an .osc file and the OSM object in question is to delete.
Which software generates .osc files that do *not* have lon/lat attributes
on nodes to be deleted?
al for most applications. The point is, you
would save up to 50% file size.
Markus
Original-Nachricht
> Datum: Tue, 31 May 2011 00:25:15 +0200
> Von: Frederik Ramm
> An: mar...@gmx.eu
> CC: dev@openstreetmap.org
> Betreff: Re: [OSM-dev] osm2pgsql: parse-xml2.
Hi,
mar...@gmx.eu wrote:
osm2pgsql persists on getting coordinates (lon/lat) even when it
reads an .osc file and the OSM object in question is to delete.
Which software generates .osc files that do *not* have lon/lat
attributes on nodes to be deleted?
My question: Does osm2pgsql really nee
Hello,
today this error message was relayed to me:
osm2pgsql: parse-xml2.c:100: StartElement: Assertion `xlon' failed.
I managed to identify the problem:
osm2pgsql persists on getting coordinates (lon/lat) even when it reads an .osc
file and the OSM object in question is to delete.
as
7 matches
Mail list logo
