Paul:
Thanks for the reply
I was using the gui version on windows. And yes it actually crashed. I was
using it on a machine where I cannot get to my email so I can't run the same
test that causes a crash.
The crash may be from a sequence of events rather than a single event. When I
try to load another file that has caused crashes before I get the following
error:
Failed record number #35
Failed SQL begins: "INSERT INTO "public"."Elevation_Point"
("objectid","nam","acc","ela","mcc","na2","na3","na4","tse","zv2","cdv","ocx","ocy","gblink","na6","akt","otn","modificati","fldbid","scale","originatin","pmid","ltt_curren","ltt_featur","ltt_versio","ltt_status","l"
Failed in pgui_exec(): ERROR: current transaction is aborted, commands ignored
until end of transaction block
It processed several lines before starting to report errors but it did not
crash when I did it from this location although it did at the place I have been
working.
One file that gives the encoding error is afghanistan_natural.shp from the OSM
shapefile dataset as does afghanistan_poi.shp and afghanistan_water.shp
Bruce
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Paul Ramsey
Sent: Thursday, September 30, 2010 1:22 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] shape to postgis inporter fails or crashes
Just use the -w switch to specify WINDOWS-1252 as your encoding.
Should work fine from there.
P.
BTW, it shouldn't crash, it should just stop and show the error. Is
that what it is doing, or do you get honest-to-god coredumps?
On Thu, Sep 30, 2010 at 10:17 AM, Clay, Bruce <[email protected]> wrote:
> I am trying to load OpenStreetMap and GDAM data from the shapefiles that
> were posted on the network. Some of the work file but those with special
> characters often fail or in came cases the application crashes.
>
>
>
> The error message get is - Unable to convert field value "<some osm name>"
> to UTF-8: iconv reports "Illegal byte sequence"
>
>
>
> DBF file character encoding is set to WINDOWS-1252 which if I am reading
> correctly should support Unicode characters.
>
>
>
> Based on comments posted on the net I also tried setting encoding to
> "Latin1"
>
> Any thoughts on how to correct this problem would be greatly appreciated.
>
>
>
> I am using PostgreSql version 8.8 and PostGis 1.5.1
>
>
>
> Bruce
>
>
>
> This message and any enclosures are intended only for the addressee. Please
> notify the sender by email if you are not the intended recipient. If you
> are
> not the intended recipient, you may not use, copy, disclose, or distribute
> this
> message or its contents or enclosures to any other person and any such
> actions
> may be unlawful. Ball reserves the right to monitor and review all messages
> and enclosures sent to or from this email address.
>
> _______________________________________________
> postgis-users mailing list
> [email protected]
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
This message and any enclosures are intended only for the addressee. Please
notify the sender by email if you are not the intended recipient. If you are
not the intended recipient, you may not use, copy, disclose, or distribute this
message or its contents or enclosures to any other person and any such actions
may be unlawful. Ball reserves the right to monitor and review all messages
and enclosures sent to or from this email address.
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
