[prev in list] [next in list] [prev in thread] [next in thread]
List: postgis-users
Subject: [postgis-users] shp2pgsql bufg
From: strk <strk () freek ! keybit ! net>
Date: 2003-06-18 8:23:08
Message-ID: 20030618102308.A49303 () freek ! keybit ! net
[Download RAW message or body]
Hello... yet another shp2pgsql problem here !
(( problem 1 ))
>From a shapefile imported with shp2pgsql I get an extra EMPTY geometry.
This is the last INSERT from generated sql:
insert into "rfi2_14" values('174','0','0','0','0','0.000',
NULL,NULL,NULL,NULL,NULL,
GeometryFromText('MULTILINESTRING ()',30001) );
It looks like a NULL entry, no dbf data, no geometry...
The postgis parser does not like 'MULTILINESTRING ()'
"couldn't parse geometry"
Shouldn't shp2pgsql check for these exceptions storing a NULL
geometry instead, and maybe printing a warning on stderr ?
I'm not considering also the possibility that this last record was not
in the shapefile at all.
(( problem 2 ))
>From a shapefile imported with shp2pgsql I get some MULTILINESTRING
geometries which has someting missed at the beginning of definition:
GeometryFromText(
'MULTILINESTRING (,686443.612958726 150851.536125343 0 ))',
30001)
Getting this problem makes me think that probably problem 1 is also
just shp2pgsql related, might be a bogus multilinestring handling.
*****
any hint on catching the bug ?
--strk;
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic