[postgis-users] Re: Problem with shp2pgsql (MULTILINESTRING 8260 as 1
Carlos Ho Shih Ning
cning at atech.br
Thu Dec 18 12:25:13 PST 2003
Indeed you are right.
The trouble is that for some files there are too many of those errors
although the table is successfully loaded into the database.
Just in case you might provide me an opinion.
Do you think that shp2pgsql is too stringent regarding to the definition
of the MULTILINESTRING or something else, while viewers like ArcView
and JUMP are more tolerant and avoid annoying the user about those problems?
I have the impression that nothing is missed despite of that error message.
thank you very much :-)
Date: Wed, 17 Dec 2003 21:48:40 +0100
From: strk <strk at keybit.net>
To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
Subject: Re: [postgis-users] Problem with shp2pgsql (MULTILINESTRING 8260 as 1
vertices, set to NULL)
Message-ID: <20031217214839.A32379 at freek.keybit.net>
In-Reply-To: <09B2A867E595294DB69E2C8885647EEC823650 at xingu.atech.local.br>;
from cning at atech.br on Wed, Dec 17, 2003 at 04:27:40PM -0300
References: <09B2A867E595294DB69E2C8885647EEC823650 at xingu.atech.local.br>
Content-Type: text/plain; charset=us-ascii
Reply-To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
The messages (althought written in non correct english) says
that some of the multilinestrings has just one vertex, being illegal
MultiLineStrings. The number shown is the shape number, and it seems
to be just some of the shapes to have this problem. You should have
no problems in feeding tm_26_set_02.sql to pgsql, you will just have
some NULL records in the resulting table.
Let me know if this is not the case.
message is sen
> I have been using shp2pgsql pretty successfully with some small nags such as avoiding the use of upper case in the name of a table.
> While doing the following command in a Linux machine:
> shp2pgsql -d tm_26_set_02 tm_26_set_02 test > tm_26_set_02.sql
> I was presented with a repeated list of message:
> MULTILINESTRING 5584 as 1 vertices, set to NULL
> MULTILINESTRING 5611 as 1 vertices, set to NULL
> MULTILINESTRING 5620 as 1 vertices, set to NULL
> Obviously the next step would be ineffective (I am using the non-default port 15432):
> psql -d test -f tm_26_set_02.sql -p 15432
> How can I solve this problem?
> I attached a zip file with the sample shapefile that caused the error.
> By the way, I have no problem in loading the shapefile in Jump and ArcView.
> thank you in advance
More information about the postgis-users