Hi All,
Thanks for replying.
The data is being read from SQL Server, where it is encoded in Latin1. I'm
reading it from SQL Server, and writing it to postgis using a .NET process.
I'm not doing anything special to convert from one character set to the other,
so maybe that's the problem.
Aaron
-----Original Message-----
From: postgis-users <postgis-users-boun...@lists.osgeo.org> On Behalf Of
postgis-users-requ...@lists.osgeo.org
Sent: Sunday, April 08, 2018 1:00 PM
To: postgis-users@lists.osgeo.org
Subject: postgis-users Digest, Vol 194, Issue 4
Send postgis-users mailing list submissions to
postgis-users@lists.osgeo.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osgeo.org/mailman/listinfo/postgis-users
or, via email, send a message with subject or body 'help' to
postgis-users-requ...@lists.osgeo.org
You can reach the person managing the list at
postgis-users-ow...@lists.osgeo.org
When replying, please edit your Subject line so it is more specific than "Re:
Contents of postgis-users digest..."
Today's Topics:
1. Re: postgis-users Digest, Vol 194, Issue 3 (Freddy Gonthier)
2. Re: postgis-users Digest, Vol 194, Issue 3 (b.j.kob...@utwente.nl)
----------------------------------------------------------------------
Message: 1
Date: Sun, 8 Apr 2018 11:24:45 +0200
From: Freddy Gonthier <freddy.gonth...@gmail.com>
To: postgis-users@lists.osgeo.org
Subject: Re: [postgis-users] postgis-users Digest, Vol 194, Issue 3
Message-ID:
<cabdf1v1fubwqkrcb9c0zsn2saxn6qbkrunqbrpuwdg56yyy...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Bonjour,
Il faut que l’application qui ouvre le fichier avec les données sources le
fasse avec le même code page que celui qui a été utiliser pour écrire les
enregistrements du fichier source. Attention, il existe des limites connues
comme un fichier source écrit avec plusieurs code page, ou encore, les
caractères du code page du fichier sources ne sont pas tous transposables vers
le code page de la base données.
Cordialement,
F. Gonthier
2018-04-07 21:00 GMT+02:00 <postgis-users-requ...@lists.osgeo.org>:
> Send postgis-users mailing list submissions to
> postgis-users@lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osgeo.org/mailman/listinfo/postgis-users
> or, via email, send a message with subject or body 'help' to
> postgis-users-requ...@lists.osgeo.org
>
> You can reach the person managing the list at
> postgis-users-ow...@lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of postgis-users digest..."
>
>
> Today's Topics:
>
> 1. Encoding and Collation Question (Aaron Edwards)
> 2. Re: Encoding and Collation Question
> (Darafei Komяpa Praliaskouski)
> 3. Re: Encoding and Collation Question (Gary Turner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 6 Apr 2018 22:05:37 +0000
> From: Aaron Edwards <aedwa...@b3insight.com>
> To: "postgis-users@lists.osgeo.org" <postgis-users@lists.osgeo.org>
> Subject: [postgis-users] Encoding and Collation Question
> Message-ID:
> <DM5PR1301MB20585A056DB69B2ABE409EFB91BA0@DM5PR1301MB2058.
> namprd13.prod.outlook.com>
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I'm trying to create a spatial layer in GoeServer using postgis. The
> problem is that there are a few special characters in the name column
> (rivers and streams in New Mexico). In Zuni river, for example, the N
> has a tilde character over it. So the labels are all wonky.
>
> What Encoding and Collation would prevent this? I tried WIN1252 and
> English_United States.1252, but that prevented me from installing the
> ogr_fdw extension, and that seemed to preclude the use of
> UpdateGeometrySRID(), which I need.
>
> Thanks.
>
> Aaron
>
> -------------- next part -------------- An HTML attachment was
> scrubbed...
> URL: <http://lists.osgeo.org/pipermail/postgis-users/
> attachments/20180406/259dd5f8/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 07 Apr 2018 11:23:17 +0000
> From: Darafei "Komяpa" Praliaskouski <m...@komzpa.net>
> To: PostGIS Users Discussion <postgis-users@lists.osgeo.org>
> Subject: Re: [postgis-users] Encoding and Collation Question
> Message-ID:
> <CAC8Q8t+UxG9WbQTepaPBkUQcvorPhUYxiSKVC
> emzjaol+fw...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> If something from one character becomes two or more characters, you're
> dealing with multibyte encoding, most likely UTF-8.
>
> сб, 7 апр. 2018 г. в 1:05, Aaron Edwards <aedwa...@b3insight.com>:
>
> > Hi,
> >
> >
> >
> > I’m trying to create a spatial layer in GoeServer using postgis.
> > The problem is that there are a few special characters in the name
> > column (rivers and streams in New Mexico). In Zuni river, for
> > example, the N
> has
> > a tilde character over it. So the labels are all wonky.
> >
> >
> >
> > What Encoding and Collation would prevent this? I tried WIN1252 and
> > English_United States.1252, but that prevented me from installing
> > the ogr_fdw extension, and that seemed to preclude the use of
> > UpdateGeometrySRID(), which I need.
> >
> >
> >
> > Thanks.
> >
> >
> >
> > Aaron
> >
> >
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/postgis-users
> -------------- next part -------------- An HTML attachment was
> scrubbed...
> URL: <http://lists.osgeo.org/pipermail/postgis-users/
> attachments/20180407/119732c4/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 8 Apr 2018 00:15:45 +1200
> From: Gary Turner <g...@elizr.com>
> To: postgis-users@lists.osgeo.org
> Subject: Re: [postgis-users] Encoding and Collation Question
> Message-ID: <841617ea-d425-d43f-33ae-7e5ab7b92...@elizr.com>
> Content-Type: text/plain; charset="windows-1252"; Format="flowed"
>
> IIRC, postgres/gis tables are UTF-8 by default. That's probably the
> best option to use to avoid hassles, and to be more stable long-term.
>
> If you are having problems, I suspect that the issue is what encoding
> your source data was/is in, and what process you used to import it.
>
> Can you do it again? What process did you use? Do you know what
> encoding it was in?
>
>
> On 07/04/18 10:05, Aaron Edwards wrote:
> >
> > Hi,
> >
> > I’m trying to create a spatial layer in GoeServer using postgis.
> > The problem is that there are a few special characters in the name
> > column (rivers and streams in New Mexico). In Zuni river, for
> > example, the N has a tilde character over it. So the labels are all wonky.
> >
> > What Encoding and Collation would prevent this? I tried WIN1252 and
> > English_United States.1252, but that prevented me from installing
> > the ogr_fdw extension, and that seemed to preclude the use of
> > UpdateGeometrySRID(), which I need.
> >
> > Thanks.
> >
> > Aaron
> >
> >
> >
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/postgis-users
>
> -------------- next part -------------- An HTML attachment was
> scrubbed...
> URL: <http://lists.osgeo.org/pipermail/postgis-users/
> attachments/20180408/55f6da7c/attachment-0001.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
> ------------------------------
>
> End of postgis-users Digest, Vol 194, Issue 3
> *********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.osgeo.org/pipermail/postgis-users/attachments/20180408/3508eb69/attachment-0001.html>
------------------------------
Message: 2
Date: Sun, 8 Apr 2018 10:05:57 +0000
From: <b.j.kob...@utwente.nl>
To: <postgis-users@lists.osgeo.org>
Subject: Re: [postgis-users] postgis-users Digest, Vol 194, Issue 3
Message-ID: <89526db2-a552-4775-b4d7-22a67540b...@utwente.nl>
Content-Type: text/plain; charset="utf-8"
Please refer from using other languages, this is an english language list....
--
Barend Köbben
On 08/04/2018, 11:25, "postgis-users on behalf of Freddy Gonthier"
<postgis-users-boun...@lists.osgeo.org<mailto:postgis-users-boun...@lists.osgeo.org>
on behalf of freddy.gonth...@gmail.com<mailto:freddy.gonth...@gmail.com>>
wrote:
Bonjour,
Il faut que l’application qui ouvre le fichier avec les données sources le
fasse avec le même code page que celui qui a été utiliser pour écrire les
enregistrements du fichier source. Attention, il existe des limites connues
comme un fichier source écrit avec plusieurs code page, ou encore, les
caractères du code page du fichier sources ne sont pas tous transposables vers
le code page de la base données.
Cordialement,
F. Gonthier
2018-04-07 21:00 GMT+02:00
<postgis-users-requ...@lists.osgeo.org<mailto:postgis-users-requ...@lists.osgeo.org>>:
Send postgis-users mailing list submissions to
postgis-users@lists.osgeo.org<mailto:postgis-users@lists.osgeo.org>
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osgeo.org/mailman/listinfo/postgis-users
or, via email, send a message with subject or body 'help' to
postgis-users-requ...@lists.osgeo.org<mailto:postgis-users-requ...@lists.osgeo.org>
You can reach the person managing the list at
postgis-users-ow...@lists.osgeo.org<mailto:postgis-users-ow...@lists.osgeo.org>
When replying, please edit your Subject line so it is more specific than "Re:
Contents of postgis-users digest..."
Today's Topics:
1. Encoding and Collation Question (Aaron Edwards)
2. Re: Encoding and Collation Question
(Darafei Komяpa Praliaskouski)
3. Re: Encoding and Collation Question (Gary Turner)
----------------------------------------------------------------------
Message: 1
Date: Fri, 6 Apr 2018 22:05:37 +0000
From: Aaron Edwards <aedwa...@b3insight.com<mailto:aedwa...@b3insight.com>>
To: "postgis-users@lists.osgeo.org<mailto:postgis-users@lists.osgeo.org>"
<postgis-users@lists.osgeo.org<mailto:postgis-users@lists.osgeo.org>>
Subject: [postgis-users] Encoding and Collation Question
Message-ID:
<dm5pr1301mb20585a056db69b2abe409efb91...@dm5pr1301mb2058.namprd13.prod.outlook.com<mailto:dm5pr1301mb20585a056db69b2abe409efb91...@dm5pr1301mb2058.namprd13.prod.outlook.com>>
Content-Type: text/plain; charset="utf-8"
Hi,
I'm trying to create a spatial layer in GoeServer using postgis. The problem
is that there are a few special characters in the name column (rivers and
streams in New Mexico). In Zuni river, for example, the N has a tilde
character over it. So the labels are all wonky.
What Encoding and Collation would prevent this? I tried WIN1252 and
English_United States.1252, but that prevented me from installing the ogr_fdw
extension, and that seemed to preclude the use of UpdateGeometrySRID(), which I
need.
Thanks.
Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.osgeo.org/pipermail/postgis-users/attachments/20180406/259dd5f8/attachment-0001.html>
------------------------------
Message: 2
Date: Sat, 07 Apr 2018 11:23:17 +0000
From: Darafei "Komяpa" Praliaskouski <m...@komzpa.net<mailto:m...@komzpa.net>>
To: PostGIS Users Discussion
<postgis-users@lists.osgeo.org<mailto:postgis-users@lists.osgeo.org>>
Subject: Re: [postgis-users] Encoding and Collation Question
Message-ID:
<cac8q8t+uxg9wbqtepapbkuqcvorphuyxiskvcemzjaol+fw...@mail.gmail.com<mailto:cac8q8t%2buxg9wbqtepapbkuqcvorphuyxiskvcemzjaol%2bfw...@mail.gmail.com>>
Content-Type: text/plain; charset="utf-8"
If something from one character becomes two or more characters, you're dealing
with multibyte encoding, most likely UTF-8.
сб, 7 апр. 2018 г. в 1:05, Aaron Edwards
<aedwa...@b3insight.com<mailto:aedwa...@b3insight.com>>:
> Hi,
>
>
>
> I’m trying to create a spatial layer in GoeServer using postgis. The
> problem is that there are a few special characters in the name column
> (rivers and streams in New Mexico). In Zuni river, for example, the N
> has a tilde character over it. So the labels are all wonky.
>
>
>
> What Encoding and Collation would prevent this? I tried WIN1252 and
> English_United States.1252, but that prevented me from installing the
> ogr_fdw extension, and that seemed to preclude the use of
> UpdateGeometrySRID(), which I need.
>
>
>
> Thanks.
>
>
>
> Aaron
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@lists.osgeo.org<mailto:postgis-users@lists.osgeo.org>
> https://lists.osgeo.org/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.osgeo.org/pipermail/postgis-users/attachments/20180407/119732c4/attachment-0001.html>
------------------------------
Message: 3
Date: Sun, 8 Apr 2018 00:15:45 +1200
From: Gary Turner <g...@elizr.com<mailto:g...@elizr.com>>
To: postgis-users@lists.osgeo.org<mailto:postgis-users@lists.osgeo.org>
Subject: Re: [postgis-users] Encoding and Collation Question
Message-ID:
<841617ea-d425-d43f-33ae-7e5ab7b92...@elizr.com<mailto:841617ea-d425-d43f-33ae-7e5ab7b92...@elizr.com>>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
IIRC, postgres/gis tables are UTF-8 by default. That's probably the best
option to use to avoid hassles, and to be more stable long-term.
If you are having problems, I suspect that the issue is what encoding your
source data was/is in, and what process you used to import it.
Can you do it again? What process did you use? Do you know what encoding it was
in?
On 07/04/18 10:05, Aaron Edwards wrote:
>
> Hi,
>
> I’m trying to create a spatial layer in GoeServer using postgis. The
> problem is that there are a few special characters in the name column
> (rivers and streams in New Mexico). In Zuni river, for example, the N
> has a tilde character over it. So the labels are all wonky.
>
> What Encoding and Collation would prevent this? I tried WIN1252 and
> English_United States.1252, but that prevented me from installing the
> ogr_fdw extension, and that seemed to preclude the use of
> UpdateGeometrySRID(), which I need.
>
> Thanks.
>
> Aaron
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@lists.osgeo.org<mailto:postgis-users@lists.osgeo.org>
> https://lists.osgeo.org/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.osgeo.org/pipermail/postgis-users/attachments/20180408/55f6da7c/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
postgis-users mailing list
postgis-users@lists.osgeo.org<mailto:postgis-users@lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/postgis-users
------------------------------
End of postgis-users Digest, Vol 194, Issue 3
*********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.osgeo.org/pipermail/postgis-users/attachments/20180408/27b8841f/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
postgis-users mailing list
postgis-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users
------------------------------
End of postgis-users Digest, Vol 194, Issue 4
*********************************************
_______________________________________________
postgis-users mailing list
postgis-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users
