[Geoserver-users] Signs like 'b≤3.2' from json/dbf not showed in Geoserver

Anneliese_Brouwer_Cr · May 13, 2015, 8:14am

Hello community,

It seems as if signs like 'b≤3.2' were not processed properly to dbf/shp
files.

I create shape files from JSON file with GDAL using the statement:

ds.CopyLayer(srcLayer, fileNameWithoutExtension, null);

or with cpg file:

ds.CopyLayer(srcLayer, fileNameWithoutExtension, new string {
"ENCODING=UTF-8" });

All shape files were created, we can see them in Geoserver Preview
(OpenLayers).

But we have problems with signs like '≤'.
In the JSON file those signs are fine but it looks like as if in the dbf
file these signs were not written properly. Depending on what encoding we
use in datasource.CopyLayer, you'll see a question mark or something else.

We have tried using the config var. SHAPE_ENCODING but we did not get the
right result.

We think this is a GDAL issue?
We need those signs in our website (Geoserver,OpenLayers).

We are using GDAL: x86, gdal-111-1600-core
Geoserver: 2.6.0

Any idea what could be wrong and how we can solve this problem?

Solve with GDAL?
Or in Geoserver?

Any feedback is appreciated!

Best regards, A. Brouwer
JSON_SHAPE.zip
<http://osgeo-org.1560.x6.nabble.com/file/n5205499/JSON_SHAPE.zip>

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Signs-like-b-3-2-from-json-dbf-not-showed-in-Geoserver-tp5205499.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Stefano_Costa3 · May 13, 2015, 8:50am

Hi Anneliese,
I just published the SHP you attached in Geoserver 2.6.2 and I can see ‘≤’ chars correctly displayed in GeoServer’s OpenLayers-based preview :

Did you select the correct DBF charset when creating the store in GeoServer?

Best regards,
Stefano

Il giorno mer, 13/05/2015 alle 01.14 -0700, AnnelieseBrouwer ha scritto:

Hello community, 

It seems as if signs like 'b≤3.2' were not processed properly to dbf/shp
files. 

I create shape files from JSON file with GDAL using the statement: 

  ds.CopyLayer(srcLayer, fileNameWithoutExtension, null); 

or with cpg file: 

  ds.CopyLayer(srcLayer, fileNameWithoutExtension, new string[] {
"ENCODING=UTF-8" }); 

All shape files were created, we can see them in Geoserver Preview
(OpenLayers). 

But we have problems with signs like '≤'. 
In the JSON file those signs are fine but it looks like as if in the dbf
file these signs were not written properly. Depending on what encoding we
use in datasource.CopyLayer, you'll see a question mark or something else. 

We have tried using the config var. SHAPE_ENCODING but we did not get the
right result. 

We think this is a GDAL issue? 
We need those signs in our website (Geoserver,OpenLayers). 

We are using GDAL: x86, gdal-111-1600-core 
Geoserver: 2.6.0 

Any idea what could be wrong and how we can solve this problem? 

Solve with GDAL?
Or in Geoserver?

Any feedback is appreciated! 

Best regards, A. Brouwer 
JSON_SHAPE.zip
<[http://osgeo-org.1560.x6.nabble.com/file/n5205499/JSON_SHAPE.zip](http://osgeo-org.1560.x6.nabble.com/file/n5205499/JSON_SHAPE.zip)>  

--
View this message in context: [http://osgeo-org.1560.x6.nabble.com/Signs-like-b-3-2-from-json-dbf-not-showed-in-Geoserver-tp5205499.html](http://osgeo-org.1560.x6.nabble.com/Signs-like-b-3-2-from-json-dbf-not-showed-in-Geoserver-tp5205499.html)
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
[http://ad.doubleclick.net/ddm/clk/290420510;117567292;y](http://ad.doubleclick.net/ddm/clk/290420510;117567292;y)
_______________________________________________
Geoserver-users mailing list
[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)

Stefano_Costa3 · May 13, 2015, 4:06pm

OK, now the picture is clearer.

I can't try the Shapefile you generated with Geoserver 1.6 (as I said,
it stubbornly refuses to start on my machine), but I tested it in GS
2.6.2 and it works fine, so I'm pretty confident your file is correct.

I know that the Shapefile specification mandated ISO8859-1 charset be
used in DBF files (see:
http://gis.stackexchange.com/questions/3529/which-character-encoding-is-used-by-the-dbf-file-in-shapefiles), so probably GS 1.6 followed closely the standard and assumed any DBF file was encoded in ISO8859-1.
I can't know for sure though, it's just a guess.

Please always use the "Reply to all" button or the other people on the
list won't be able to follow along and help you.

Best regards,
Stefano

Il giorno mer, 13/05/2015 alle 15.23 +0000, Anneliese Brouwer|Crotec
B.V. ha scritto:

Stefano,

We have a web application in which we use Geoserver and OpenLayers.
The user can select a gml file. In code we upload the file, create json file, with gdal we create the shape files (geometry types can be point, line, region) , and with geoserverrest we create datastore and layers in Geoserver.

Yes, I did try UTF-8. In some messages on the Internet about the issue people mention ISO-8859-1. So I tried that one also.

Thanks for the help.

Best regards

Anneliese Brouwer
Ontwikkelaar

-----Oorspronkelijk bericht-----
Van: Stefano Costa [mailto:stefano.costa@anonymised.com]
Verzonden: woensdag 13 mei 2015 16:57
Aan: Anneliese Brouwer | Crotec B.V.
Onderwerp: Re: [Geoserver-users] Signs like 'b≤3.2' from json/dbf not showed in Geoserver

Hi Anneliese,

>
> I did some modifications in my code (C#) but still not seeing the'≤'
> chars.
>
> (Geoserver 1.6.0).

Wow, quite an ancient version of GeoServer you've got there, I wasn't even able to make it start on my machine.

> <entry key=""charset"">ISO-8859-1</entry>
>

Did you try using UTF-8 as charset:

<entry key=""charset"">UTF-8</entry>

Also, I'm wondering why you are using the REST interface to create / configure datastores instead of the web admin interface...

Best,
Stefano

Jukka_Rahkonen · May 13, 2015, 5:17pm

Hi,

Perhaps off-topic, but I would like to see stronger proof about ISO8859-1 being mandated in DBF or shapefiles.

From the dBase history http://www.eweek.com/database/30-years-ago-the-rise-fall-and-survival-of-ashton-tates-dbase-2.html it appears that dBase II came in 1981, dBase III in 1984, and dBase IV 1988. On the other hand, in article http://en.wikipedia.org/wiki/ISO/IEC_8859-1 we are told that the standard is three years younger than dBase III:
"ISO/IEC 8859-1:1998, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin alphabet No. 1, is part of the ISO/IEC 8859 series of ASCII-based standard character encodings, first edition published in 1987."

The shapefile specification http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf does not speak anything about codepages and very little about dbf, not even which dbf version should be used. In all shapefiles I have had a closer look the dbf part is marked to be version III in the headers.

A blog http://dbaseblogs.com/kkolosky/2012/07/11/code-page-and-dbase-for-dos-system-is-not-configured-for-current-code-page/ shows that dBase IV 2.0 supported DOS codepages 437 and 850, http://en.wikipedia.org/wiki/Code_page_437 and http://en.wikipedia.org/wiki/Code_page_850. So no support for ISO8859-1 at all in a native dBase product.

Well, I think I could have used my time better by trying to find something helpful for Anneliese instead of correcting an error in the Internet.

-Jukka Rahkonen-
________________________________________
Stefano Costa wrote:

OK, now the picture is clearer.

I can't try the Shapefile you generated with Geoserver 1.6 (as I said,
it stubbornly refuses to start on my machine), but I tested it in GS
2.6.2 and it works fine, so I'm pretty confident your file is correct.

I know that the Shapefile specification mandated ISO8859-1 charset be
used in DBF files (see:
http://gis.stackexchange.com/questions/3529/which-character-encoding-is-used-by-the-dbf-file-in-shapefiles), so probably GS 1.6 followed closely the standard and assumed any DBF file was encoded in ISO8859-1.
I can't know for sure though, it's just a guess.

Please always use the "Reply to all" button or the other people on the
list won't be able to follow along and help you.

Best regards,
Stefano

Il giorno mer, 13/05/2015 alle 15.23 +0000, Anneliese Brouwer|Crotec
B.V. ha scritto:

Stefano,

We have a web application in which we use Geoserver and OpenLayers.
The user can select a gml file. In code we upload the file, create json file, with gdal we create the shape files (geometry types can be point, line, region) , and with geoserverrest we create datastore and layers in Geoserver.

Yes, I did try UTF-8. In some messages on the Internet about the issue people mention ISO-8859-1. So I tried that one also.

Thanks for the help.

Best regards

Anneliese Brouwer
Ontwikkelaar

-----Oorspronkelijk bericht-----
Van: Stefano Costa [mailto:stefano.costa@…1107…]
Verzonden: woensdag 13 mei 2015 16:57
Aan: Anneliese Brouwer | Crotec B.V.
Onderwerp: Re: [Geoserver-users] Signs like 'b≤3.2' from json/dbf not showed in Geoserver

Hi Anneliese,

>
> I did some modifications in my code (C#) but still not seeing the'≤'
> chars.
>
> (Geoserver 1.6.0).

Wow, quite an ancient version of GeoServer you've got there, I wasn't even able to make it start on my machine.

> <entry key=""charset"">ISO-8859-1</entry>
>

Did you try using UTF-8 as charset:

<entry key=""charset"">UTF-8</entry>

Also, I'm wondering why you are using the REST interface to create / configure datastores instead of the web admin interface...

Best,
Stefano

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Stefano_Costa3 · May 13, 2015, 5:24pm

I finally managed to run GeoServer 1.6.2 on a VM, I published your shape file and I can see all the characters correctly:

So… not sure why it doesn’t work for you… or it doesn’t work only when you publish the layer via the rest interface?

Regards,
–S

Il giorno mer, 13/05/2015 alle 17.17 +0000, Rahkonen Jukka (MML) ha scritto:

Hi,

Perhaps off-topic, but I would like to see stronger proof about ISO8859-1 being mandated in DBF or shapefiles.

>From the dBase history [http://www.eweek.com/database/30-years-ago-the-rise-fall-and-survival-of-ashton-tates-dbase-2.html](http://www.eweek.com/database/30-years-ago-the-rise-fall-and-survival-of-ashton-tates-dbase-2.html) it appears that dBase II came in 1981, dBase III in 1984, and dBase IV 1988. On the other hand, in article [http://en.wikipedia.org/wiki/ISO/IEC_8859-1](http://en.wikipedia.org/wiki/ISO/IEC_8859-1) we are told that the standard is three years younger than dBase III: 
"ISO/IEC 8859-1:1998, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin alphabet No. 1, is part of the ISO/IEC 8859 series of ASCII-based standard character encodings, first edition published in 1987."

The shapefile specification [http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf](http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf) does not speak anything about codepages and very little about dbf, not even which dbf version should be used. In all shapefiles I have had a closer look the dbf part is marked to be version III in the headers.

A blog [http://dbaseblogs.com/kkolosky/2012/07/11/code-page-and-dbase-for-dos-system-is-not-configured-for-current-code-page/](http://dbaseblogs.com/kkolosky/2012/07/11/code-page-and-dbase-for-dos-system-is-not-configured-for-current-code-page/) shows that dBase IV 2.0 supported DOS codepages 437 and 850, [http://en.wikipedia.org/wiki/Code_page_437](http://en.wikipedia.org/wiki/Code_page_437) and [http://en.wikipedia.org/wiki/Code_page_850](http://en.wikipedia.org/wiki/Code_page_850). So no support for ISO8859-1 at all in a native dBase product.

Well, I think I could have used my time better by trying to find something helpful for Anneliese instead of correcting an error in the Internet. 

-Jukka Rahkonen-
________________________________________
Stefano Costa wrote:

OK, now the picture is clearer.

I can't try the Shapefile you generated with Geoserver 1.6 (as I said,
it stubbornly refuses to start on my machine), but I tested it in GS
2.6.2 and it works fine, so I'm pretty confident your file is correct.

I know that the Shapefile specification mandated ISO8859-1 charset be
used in DBF files (see:
[http://gis.stackexchange.com/questions/3529/which-character-encoding-is-used-by-the-dbf-file-in-shapefiles](http://gis.stackexchange.com/questions/3529/which-character-encoding-is-used-by-the-dbf-file-in-shapefiles)), so probably GS 1.6 followed closely the standard and assumed any DBF file was encoded in ISO8859-1.
I can't know for sure though, it's just a guess.

Please always use the "Reply to all" button or the other people on the
list won't be able to follow along and help you.

Best regards,
Stefano

Il giorno mer, 13/05/2015 alle 15.23 +0000, Anneliese Brouwer|Crotec
B.V. ha scritto:
> Stefano,
>
> We have a web application in which we use Geoserver and OpenLayers.
> The user can select a gml file. In code we upload the file, create json file,  with gdal we create the shape files (geometry types can be point, line, region) , and with geoserverrest we create datastore and layers in Geoserver.
>
> Yes, I did try UTF-8. In some messages on the Internet about the issue people mention ISO-8859-1. So I tried that one also.
>
> Thanks for the help.
>
> Best regards
>
> Anneliese Brouwer
> Ontwikkelaar
>
>
>
>
>
>
> -----Oorspronkelijk bericht-----
> Van: Stefano Costa [[mailto:stefano.costa@anonymised.com](mailto:stefano.costa@anonymised.com)]
> Verzonden: woensdag 13 mei 2015 16:57
> Aan: Anneliese Brouwer | Crotec B.V.
> Onderwerp: Re: [Geoserver-users] Signs like 'b≤3.2' from json/dbf not showed in Geoserver
>
> Hi Anneliese,
>
> >
> > I did some modifications in my code (C#) but still not seeing the'≤'
> > chars.
> >
> > (Geoserver 1.6.0).
>
> Wow, quite an ancient version of GeoServer you've got there, I wasn't even able to make it start on my machine. :-)
>
> >   <entry key=""charset"">ISO-8859-1</entry>
> >
>
>
> Did you try using UTF-8 as charset:
>
> <entry key=""charset"">UTF-8</entry>
>
> Also, I'm wondering why you are using the REST interface to create / configure datastores instead of the web admin interface...
>
> Best,
> Stefano
>
>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
[http://ad.doubleclick.net/ddm/clk/290420510;117567292;y](http://ad.doubleclick.net/ddm/clk/290420510;117567292;y)
_______________________________________________
Geoserver-users mailing list
[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)

Anneliese_Brouwer_Cr · May 13, 2015, 5:34pm

Stefano,

I am going to do two tests. Publishing without the GeoserverRest and via the GeoserverRest.

I’ll let you know.

Best regards

···

Anneliese Brouwer

Van: Stefano Costa [mailto:stefano.costa@…1107…]
Verzonden: woensdag 13 mei 2015 19:24
Aan: Rahkonen Jukka (MML)
CC: Anneliese Brouwer | Crotec B.V.; geoserver-users@lists.sourceforge.net
Onderwerp: Re: [Geoserver-users] Signs like ‘b≤3.2’ from json/dbf not showed in Geoserver

I finally managed to run GeoServer 1.6.2 on a VM, I published your shape file and I can see all the characters correctly:

So… not sure why it doesn’t work for you… or it doesn’t work only when you publish the layer via the rest interface?

Regards,
–S

Il giorno mer, 13/05/2015 alle 17.17 +0000, Rahkonen Jukka (MML) ha scritto:

Hi,

Perhaps off-topic, but I would like to see stronger proof about ISO8859-1 being mandated in DBF or shapefiles.

From the dBase history [http://www.eweek.com/database/30-years-ago-the-rise-fall-and-survival-of-ashton-tates-dbase-2.html](http://www.eweek.com/database/30-years-ago-the-rise-fall-and-survival-of-ashton-tates-dbase-2.html) it appears that dBase II came in 1981, dBase III in 1984, and dBase IV 1988. On the other hand, in article [http://en.wikipedia.org/wiki/ISO/IEC_8859-1](http://en.wikipedia.org/wiki/ISO/IEC_8859-1) we are told that the standard is three years younger than dBase III:

"ISO/IEC 8859-1:1998, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin alphabet No. 1, is part of the ISO/IEC 8859 series of ASCII-based standard character encodings, first edition published in 1987."

The shapefile specification [http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf](http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf) does not speak anything about codepages and very little about dbf, not even which dbf version should be used. In all shapefiles I have had a closer look the dbf part is marked to be version III in the headers.

A blog [http://dbaseblogs.com/kkolosky/2012/07/11/code-page-and-dbase-for-dos-system-is-not-configured-for-current-code-page/](http://dbaseblogs.com/kkolosky/2012/07/11/code-page-and-dbase-for-dos-system-is-not-configured-for-current-code-page/) shows that dBase IV 2.0 supported DOS codepages 437 and 850, [http://en.wikipedia.org/wiki/Code_page_437](http://en.wikipedia.org/wiki/Code_page_437) and [http://en.wikipedia.org/wiki/Code_page_850](http://en.wikipedia.org/wiki/Code_page_850). So no support for ISO8859-1 at all in a native dBase product.

Well, I think I could have used my time better by trying to find something helpful for Anneliese instead of correcting an error in the Internet.

-Jukka Rahkonen-

________________________________________

Stefano Costa wrote:

OK, now the picture is clearer.

I can't try the Shapefile you generated with Geoserver 1.6 (as I said,

it stubbornly refuses to start on my machine), but I tested it in GS

2.6.2 and it works fine, so I'm pretty confident your file is correct.

I know that the Shapefile specification mandated ISO8859-1 charset be

used in DBF files (see:

[http://gis.stackexchange.com/questions/3529/which-character-encoding-is-used-by-the-dbf-file-in-shapefiles](http://gis.stackexchange.com/questions/3529/which-character-encoding-is-used-by-the-dbf-file-in-shapefiles)), so probably GS 1.6 followed closely the standard and assumed any DBF file was encoded in ISO8859-1.

I can't know for sure though, it's just a guess.

Please always use the "Reply to all" button or the other people on the

list won't be able to follow along and help you.

Best regards,

Stefano

Il giorno mer, 13/05/2015 alle 15.23 +0000, Anneliese Brouwer|Crotec

B.V. ha scritto:

> Stefano,

> We have a web application in which we use Geoserver and OpenLayers.

> The user can select a gml file. In code we upload the file, create json file,  with gdal we create the shape files (geometry types can be point, line, region) , and with geoserverrest we create datastore and layers in Geoserver.

> Yes, I did try UTF-8. In some messages on the Internet about the issue people mention ISO-8859-1. So I tried that one also.

> Thanks for the help.

> Best regards

> Anneliese Brouwer

> Ontwikkelaar

> -----Oorspronkelijk bericht-----

> Van: Stefano Costa [[mailto:stefano.costa@...1107...](mailto:stefano.costa@...1107...)]

> Verzonden: woensdag 13 mei 2015 16:57

> Aan: Anneliese Brouwer | Crotec B.V.

> Onderwerp: Re: [Geoserver-users] Signs like 'b≤3.2' from json/dbf not showed in Geoserver

> Hi Anneliese,

> >

> > I did some modifications in my code (C#) but still not seeing the'≤'

> > chars.

> >

> > (Geoserver 1.6.0).

> Wow, quite an ancient version of GeoServer you've got there, I wasn't even able to make it start on my machine. :-)

> >   <entry key=""charset"">ISO-8859-1</entry>

> >

> Did you try using UTF-8 as charset:

> <entry key=""charset"">UTF-8</entry>

> Also, I'm wondering why you are using the REST interface to create / configure datastores instead of the web admin interface...

> Best,

> Stefano

------------------------------------------------------------------------------

One dashboard for servers and applications across Physical-Virtual-Cloud

Widest out-of-the-box monitoring support with 50+ applications

Performance metrics, stats and reports that give you Actionable Insights

Deep dive visibility with transaction tracing using APM Insight.

[http://ad.doubleclick.net/ddm/clk/290420510;117567292;y](http://ad.doubleclick.net/ddm/clk/290420510;117567292;y)

_______________________________________________

Geoserver-users mailing list

[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)

[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)

Anneliese_Brouwer_Cr · May 14, 2015, 9:42am

Finally it works!

After changing some code we can see signs like: ≤ in Geoserver.

To make it work I did two things:

When converting from JSON to Shp files (GDAL) I have added the config. Var SHAPE_ENCODING

Gdal.SetConfigOption(“SHAPE_ENCODING”, “UTF-8”);

When ccreating the datastore and layers in Geoserver from Directory of shapefiles I have added a Put request (GeoserverRest):

string putData = @"<?xml version=""1.0""?>

“+ dsName + @”

added by RoServices/REST

Directory of spatial files (shapefiles)

true

<entry key=““memory mapped buffer””>false

<entry key=““create spatial index””>false

<entry key=““charset””>UTF-8

<entry key=““filetype””>shapefile

<entry key=““url””>" + dataStr + @"

";

···

Thanks Stefano and Rob for helping me to solve our problem.

Best regards, Annelies Brouwer

SHAPE_ENCODING usually works fine – where/how are you viewing the resulting shapefiles and determining they’re “wrong”?

If using GeoServer, are you setting the “charset” property to UTF-8/whatever when you create your datastore?

Rob

–

Koordinates
PO Box 1604, Shortland St, Auckland 1140, New Zealand
Phone +64-9-966 0433 koordinates.com

Van: Anneliese Brouwer | Crotec B.V.
Verzonden: woensdag 13 mei 2015 19:29
Aan: ‘Stefano Costa’; Rahkonen Jukka (MML)
CC: geoserver-users@lists.sourceforge.net
Onderwerp: RE: [Geoserver-users] Signs like ‘b≤3.2’ from json/dbf not showed in Geoserver

Stefano,

I am going to do two tests. Publishing without the GeoserverRest and via the GeoserverRest.

I’ll let you know.

Best regards

Anneliese Brouwer

Van: Stefano Costa [mailto:stefano.costa@…1107…]
Verzonden: woensdag 13 mei 2015 19:24
Aan: Rahkonen Jukka (MML)
CC: Anneliese Brouwer | Crotec B.V.; geoserver-users@lists.sourceforge.net
Onderwerp: Re: [Geoserver-users] Signs like ‘b≤3.2’ from json/dbf not showed in Geoserver

I finally managed to run GeoServer 1.6.2 on a VM, I published your shape file and I can see all the characters correctly:

So… not sure why it doesn’t work for you… or it doesn’t work only when you publish the layer via the rest interface?

Regards,
–S

Il giorno mer, 13/05/2015 alle 17.17 +0000, Rahkonen Jukka (MML) ha scritto:

Hi,

Perhaps off-topic, but I would like to see stronger proof about ISO8859-1 being mandated in DBF or shapefiles.

From the dBase history [http://www.eweek.com/database/30-years-ago-the-rise-fall-and-survival-of-ashton-tates-dbase-2.html](http://www.eweek.com/database/30-years-ago-the-rise-fall-and-survival-of-ashton-tates-dbase-2.html) it appears that dBase II came in 1981, dBase III in 1984, and dBase IV 1988. On the other hand, in article [http://en.wikipedia.org/wiki/ISO/IEC_8859-1](http://en.wikipedia.org/wiki/ISO/IEC_8859-1) we are told that the standard is three years younger than dBase III:

"ISO/IEC 8859-1:1998, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin alphabet No. 1, is part of the ISO/IEC 8859 series of ASCII-based standard character encodings, first edition published in 1987."

The shapefile specification [http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf](http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf) does not speak anything about codepages and very little about dbf, not even which dbf version should be used. In all shapefiles I have had a closer look the dbf part is marked to be version III in the headers.

A blog [http://dbaseblogs.com/kkolosky/2012/07/11/code-page-and-dbase-for-dos-system-is-not-configured-for-current-code-page/](http://dbaseblogs.com/kkolosky/2012/07/11/code-page-and-dbase-for-dos-system-is-not-configured-for-current-code-page/) shows that dBase IV 2.0 supported DOS codepages 437 and 850, [http://en.wikipedia.org/wiki/Code_page_437](http://en.wikipedia.org/wiki/Code_page_437) and [http://en.wikipedia.org/wiki/Code_page_850](http://en.wikipedia.org/wiki/Code_page_850). So no support for ISO8859-1 at all in a native dBase product.

Well, I think I could have used my time better by trying to find something helpful for Anneliese instead of correcting an error in the Internet.

-Jukka Rahkonen-

________________________________________

Stefano Costa wrote:

OK, now the picture is clearer.

I can't try the Shapefile you generated with Geoserver 1.6 (as I said,

it stubbornly refuses to start on my machine), but I tested it in GS

2.6.2 and it works fine, so I'm pretty confident your file is correct.

I know that the Shapefile specification mandated ISO8859-1 charset be

used in DBF files (see:

[http://gis.stackexchange.com/questions/3529/which-character-encoding-is-used-by-the-dbf-file-in-shapefiles](http://gis.stackexchange.com/questions/3529/which-character-encoding-is-used-by-the-dbf-file-in-shapefiles)), so probably GS 1.6 followed closely the standard and assumed any DBF file was encoded in ISO8859-1.

I can't know for sure though, it's just a guess.

Please always use the "Reply to all" button or the other people on the

list won't be able to follow along and help you.

Best regards,

Stefano

Il giorno mer, 13/05/2015 alle 15.23 +0000, Anneliese Brouwer|Crotec

B.V. ha scritto:

> Stefano,

> We have a web application in which we use Geoserver and OpenLayers.

> The user can select a gml file. In code we upload the file, create json file,  with gdal we create the shape files (geometry types can be point, line, region) , and with geoserverrest we create datastore and layers in Geoserver.

> Yes, I did try UTF-8. In some messages on the Internet about the issue people mention ISO-8859-1. So I tried that one also.

> Thanks for the help.

> Best regards

> Anneliese Brouwer

> Ontwikkelaar

> -----Oorspronkelijk bericht-----

> Van: Stefano Costa [[mailto:stefano.costa@...1107...](mailto:stefano.costa@...1107...)]

> Verzonden: woensdag 13 mei 2015 16:57

> Aan: Anneliese Brouwer | Crotec B.V.

> Onderwerp: Re: [Geoserver-users] Signs like 'b≤3.2' from json/dbf not showed in Geoserver

> Hi Anneliese,

> >

> > I did some modifications in my code (C#) but still not seeing the'≤'

> > chars.

> >

> > (Geoserver 1.6.0).

> Wow, quite an ancient version of GeoServer you've got there, I wasn't even able to make it start on my machine. :-)

> >   <entry key=""charset"">ISO-8859-1</entry>

> >

> Did you try using UTF-8 as charset:

> <entry key=""charset"">UTF-8</entry>

> Also, I'm wondering why you are using the REST interface to create / configure datastores instead of the web admin interface...

> Best,

> Stefano

------------------------------------------------------------------------------

One dashboard for servers and applications across Physical-Virtual-Cloud

Widest out-of-the-box monitoring support with 50+ applications

Performance metrics, stats and reports that give you Actionable Insights

Deep dive visibility with transaction tracing using APM Insight.

[http://ad.doubleclick.net/ddm/clk/290420510;117567292;y](http://ad.doubleclick.net/ddm/clk/290420510;117567292;y)

_______________________________________________

Geoserver-users mailing list

[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)

[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)

Stefano_Costa3 · May 14, 2015, 9:56am

Great, I'm glad it works now!

Bye,
--S

Il giorno gio, 14/05/2015 alle 09.42 +0000, Anneliese Brouwer|Crotec
B.V. ha scritto:

Finally it works!