[postgis-users] shp2pgsql import error: invalid byte sequence forencoding "UTF8": 0x96

[Burgholzer, Robert (DEQ)]

Ahhh, it was my "0x96" that defeated le Google.  The fix, for those of
you awaiting the outcome with bated  breath:

 

Shp2psql -W latin1 ...

 

Encoding is all good from there on out.  Thanks to Leo who posted a
solution in April of 2009!!!

 

r.b.

 

From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
Burgholzer, Robert (DEQ)
Sent: Friday, April 01, 2011 4:31 PM
To: postgis-users at refractions.net
Subject: [postgis-users] shp2pgsql import error: invalid byte sequence
forencoding "UTF8": 0x96

 

I am importing a file from some colleagues that is throwing an error
that I have never encountered before (nor it seems, has Google).    What
is interesting is that this file was an update sent to me whose only
supposed difference is that it is a POINT shapefile instead of a
MULTIPOLYGON.   The MULTIPOLYGON version worked fine, of course I have
no way of knowing what else has REALLY changed with this dataset.  Any
help would be appreciated.  The error occurs with only a subset of the
records, and occurs upon cat'ing the file to psql like so:

 

cat sql/observed_vdgif_xy.sql | psql aquatic_bio -U robertwb

 

ERROR: byte sequence for encoding "UTF8": 0x96 

HINT:  This error can also happen if the byte sequence does not match
the encoding expected by the server, which is controlled by
"client_encoding".

 

Regards,

r.b.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110401/4d8c8b5c/attachment.html>