[GIS] Geoserver WMS character representation error (UTF-8)

geoservergetfeatureinfomapinfowms

I created a layer that is connected to an Oracle DB table. I can access the layer as WMS and as WFS. The character representation is correct in the WFS but has errors in the WMS service. I used Qgis and MapInfo for testing and I have the same problem with both.

Screenshot MapInfo info tool (WMS):

Screenshot MapInfo info tool (WFS):

I recognized that I have the same problem with all my WMS layers where german umlauts are used. In the Geoserver global settings the charset is set to UTF-8. How can I fix this?

EDIT: I tested the same WMS with ArcGIS Explorer and Gaia. Both can display the character correctly. The problem seems to be the software that is used to access the WMS… I will let you know when the ticket is answered.

Best Answer

Check making a call with the browser and the developer tools of the browser that the GetFeatureInfo response is being declared as UTF-8.

Or directly try to modify the html/xml GetFeatureInfo templates to enforce the client display the results in utf-8 adding a line like this in the header:

<meta http-equiv="content-type" content="text/html; charset=UTF-8"></meta>

Of course, in the client you should use the html/xml info formats.

Related Solutions

How to Make GeoServer Return JSON for WMS GetFeatureInfo

Update The 'hack' given below is necessary only for Geoserver versions 2.2.x and below. With version 2.3.0 and upwards, Geoserver can return JSON for WMS GetFeatureInfo request natively.

End of Update

There is an open feature request for this on geoserver's bug tracker.

Using custom GetFeatureInfo Templates, it is possible to generate a Json response from Geoserver.

You can follow these steps:

1]Go to the following folder

GEOSERVER_DATA_DIR/workspaces/{workspace}/{datastore}/{featuretype}/

2] Create 3 empty text files with the following names: header.ftl, content.ftl & footer.ftl

3] Open the content.ftl file, and copy the following free-marker code:

[
<#list features as feature>
{ "Type": "${type.name}"
<#list feature.attributes as attribute>
    <#if !attribute.isGeometry>
    , "${attribute.name}": "${attribute.value}"
    </#if>
</#list>
}
</#list> ,{}
]

4] Save the file and now make the WMS getFeatureInfo request. You'll see that the response is in JSON.

Note: You need to remember that this will wrap the numeric values in inverted commas as a string. Hence you might have to take care of it in the client code.

[GIS] GeoServer cascading WMS, FeatureInfo is lost

According to the documentation:

GetFeatureInfo cascading for servers that do support the application/vnd.ogc.gml feature info format. Works in both standard and reprojected case.

It seems that your server does provide that format but I haven't actually tested that it does. You may need to make sure that your request is also in that format?

So the bottom line is that it should be working - can you check what the request that is sent to the remote server looks like (may be with wireshark if you don't have access to the remote logs).

Best Answer

Related Solutions

How to Make GeoServer Return JSON for WMS GetFeatureInfo

[GIS] GeoServer cascading WMS, FeatureInfo is lost

Related Question