Re: invalid byte sequence for encoding "UTF8" - Mailing list pgsql-general

From Chad Wagner
Subject Re: invalid byte sequence for encoding "UTF8"
Date
Msg-id 81961ff50701161530u1c2fefc6gb1d80040233cf3ef@mail.gmail.com
Whole thread Raw
In response to invalid byte sequence for encoding "UTF8"  ("Gary Benade" <gary@softwareguys.co.za>)
List pgsql-general


On 1/16/07, Gary Benade <gary@softwareguys.co.za> wrote:
I used shp2pgsql.exe to create an import sql for my gis database.
The resultant sql has data like this in it.INSERT INTO "gis"."sa_area" ("label","type","level",the_geom) VALUES ('MÔRELIG','0x2','2','0106000000010000000');
The Ô is ascii char 212.
This wont import, PSQL returns
ERROR: invalid byte sequence for encoding "UTF8": 0xd452
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"


I am not terribly familiar with PostGIS (other than installing it, running the test cases and saying cool :), but it appears that your source data is probably ISO-8859-1.  You should probably use the -W switch with shp2pgsql and specify the client encoding as "LATIN1", it should write a dump file with SET client_encoding to 'LATIN1' instead of UTF8 (or you can manually tweak the SQL file).


--
Chad
http://www.postgresqlforums.com/

pgsql-general by date:

Previous
From: "Patrick Earl"
Date:
Subject: GUID/UUID Support
Next
From: "Chad Wagner"
Date:
Subject: Re: Mounting a data dir read only