Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GeoDa displays string records with special characters as empty cells #491

Closed
jkoschinsky opened this issue Oct 10, 2016 · 6 comments
Closed

Comments

@jkoschinsky
Copy link
Collaborator

GeoDa 1.8.13.5

GeoDa displays string records with special characters (in this case Spanish accents) as empty cells. One of the students in Luc's class needs this.

Left (GeoDa) - Right (GIS)

screen shot 2016-10-10 at 4 17 54 pm

@lixun910
Copy link
Member

Did you Try menu -- encoding?

On Oct 10, 2016, at 4:21 PM, jkoschinsky [email protected] wrote:

GeoDa 1.8.13.5

GeoDa displays string records with special characters (in this case Spanish accents) as empty cells. One of the students in Luc's class needs this.

Left (GeoDa) - Right (GIS)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@jkoschinsky
Copy link
Collaborator Author

great, that works, thx.
Is there a way to auto-detect this or raise a flag at read-in to let users
know this option exists?

On 10 October 2016 at 17:46, Xun Li [email protected] wrote:

Did you Try menu -- encoding?

On Oct 10, 2016, at 4:21 PM, jkoschinsky [email protected]
wrote:

GeoDa 1.8.13.5

GeoDa displays string records with special characters (in this case
Spanish accents) as empty cells. One of the students in Luc's class needs
this.

Left (GeoDa) - Right (GIS)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#491 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANC8f0GwnHLzeDmxx-edp6iJjP5FfoW6ks5qysApgaJpZM4KTAM6
.

@lixun910
Copy link
Member

Yes, see the following, we can keep this ticket open but change the title
to "Auto detect encoding for DBF":

The original DBF standard defines to use ISO8859-1
http://en.wikipedia.org/wiki/ISO/IEC_8859-1, and only ISO8859-1. So, when
you get a Shapefile that is really standards conform, it should be
ISO8859-1. Of course, this (very old) restriction is a not really usable
nowadays.

ArcGIS and Geopublisher, AtlasStyler and Geoserver started to extend the
standard to define the encoding. For ArcGIS
http://support.esri.com/en/knowledgebase/techarticles/detail/21106,
Geopublisher http://en.geopublishing.org/ and AtlasStyler SLD Editor
http://en.geopublishing.org/, just create a .cpg file (with the same
basename as the other Shapefiles) and fill it with the name of the encoding.

e.g. create a myshape.cpg with a texteditor and insert 5 characters "UTF-8"
and save it. If you then open the Shapefile in ArcGIS or Geopublisher or
AtlasStyler, they will read the textual contents of the DBF in that charset.

Xun Li, Ph.D

Assistant Director for Data Science
Center for Spatial Data Science
University of Chicago
http://spatial.uchicago.edu

On Mon, Oct 10, 2016 at 5:50 PM, jkoschinsky [email protected]
wrote:

great, that works, thx.
Is there a way to auto-detect this or raise a flag at read-in to let users
know this option exists?

On 10 October 2016 at 17:46, Xun Li [email protected] wrote:

Did you Try menu -- encoding?

On Oct 10, 2016, at 4:21 PM, jkoschinsky [email protected]
wrote:

GeoDa 1.8.13.5

GeoDa displays string records with special characters (in this case
Spanish accents) as empty cells. One of the students in Luc's class needs
this.

Left (GeoDa) - Right (GIS)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#491 (comment)
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANC8f0GwnHLzeDmxx-
edp6iJjP5FfoW6ks5qysApgaJpZM4KTAM6>
.


You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#491 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACT8T6mna5ZANw08tykTfxq1maLT8fuAks5qysEggaJpZM4KTAM6
.

@lixun910
Copy link
Member

can you send me the data (if it comes with the .cpg file)?

@jkoschinsky
Copy link
Collaborator Author

just emailed it

On 16 October 2016 at 21:39, Xun Li [email protected] wrote:

can you send me the data (if it comes with the .cpg file)?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#491 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANC8fzncsGeLr8NmnaJue6TyguB8YgSdks5q0t_ngaJpZM4KTAM6
.

lixun910 referenced this issue in lixun910/geoda Oct 18, 2016
only for ESRI shape file
@jkoschinsky
Copy link
Collaborator Author

GeoDa 1.8.15.5 — Mac OSX
Confirmed fix:

screen shot 2016-12-21 at 6 24 50 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants