Encoding
From MapbenderWiki
This is a complex issue and can create lots of errors that are hard to resolve.
Contents |
Introduction
The encoding specifies which character set is used to encode string. This is important for a number of places:
- Displaying HTML pagee
- Encoding Databases
- Encoding Texts
- Format of Capabilities Documents
Use Cases
When you run into a problem you have to first start by finding at which point of you architecture the problem arises. The following use cases list the involved components.
WMS
- Browser (Encoding it can be set manually - even for each frame individually!)
- Webserver (can override what you intend to have when no setting can be found in the HTML page header)
- MapServer:
- If the text in the image is spelled wrong (fx. road names) then probably your data source is ambiguous
- If only the text in the result set of a FeatureInfo request is wrong then probably the header of the HTML page is missing or incorrect
- If the OGC Capabilites document and associated metadata tags are displayed wrong then probably the encoding of that file is different to the Mapbender database (this should be fixed as of versions >=2.2???)
- Mapbender
- If you call FeatureInfo directly via JavaScript then Mapbender is not involved
- If you use the tunnel then Mapbender also messes with the Encoding! First find out what actually Mapbender does!
- Database or Shapefile: The software may expect a different setting to what the source data has.
WFS
- Browser (Encoding it can be set manually - even for each frame individually!)
- Webserver (can override what you intend to have when no setting can be found in the HTML page header)
- WFS
- MapServer (don't know how MS handles this)
- GeoServer can be set globally in the configuration. This means that all data stores must have the same encoding!
- Database or Shapefile: The software may expect a different setting to what the source data has.
Technical Solution
Some technical solutions are developed in the page Encoding UTF8/ISO8859-1.
