Mercurial > mxd2map > mxd2map
comparison doku/source/functionality.txt @ 235:00a39e8b6eed
* INSTALL.txt: Added a paragraph to make the env-vars available in Apache
* doku/source/_templates/layout.html: defining a custom footer with the
version-string included
* doku/source/conf.py: adopt versionstring and copyright
* doku/source/functionality.txt: formating-cosmetics, correct icon
| author | Stephan Holl <stephan.holl@intevation.de> |
|---|---|
| date | Fri, 05 Aug 2011 09:18:53 +0200 |
| parents | df533a03ad9f |
| children | d10fd4de02aa |
comparison
equal
deleted
inserted
replaced
| 234:d20477c1a7f8 | 235:00a39e8b6eed |
|---|---|
| 9 | 9 |
| 10 To transform an ArcGIS mxd file to a MapServer configuration file the mxd file | 10 To transform an ArcGIS mxd file to a MapServer configuration file the mxd file |
| 11 must have a valid and available data source and must not fit the | 11 must have a valid and available data source and must not fit the |
| 12 :ref:`restriction-label` described in the appropriate section. | 12 :ref:`restriction-label` described in the appropriate section. |
| 13 | 13 |
| 14 .. image:: ../funktionsweise/funktionsweise-MXD-konverter.png | 14 .. image:: ../funktionsweise/funktionsweise-MXD2map.png |
| 15 :align: center | 15 :align: center |
| 16 :alt: MXD2map-Schema | 16 :alt: MXD2map-Schema |
| 17 :width: 500px | 17 :width: 500px |
| 18 | 18 |
| 19 .. _howtouse-label: | 19 .. _howtouse-label: |
| 55 | 55 |
| 56 To have the full functionality for ArcGIS map conversion it is necessary to have | 56 To have the full functionality for ArcGIS map conversion it is necessary to have |
| 57 the ESRI fonts available. ArcGIS products install these fonts to the default | 57 the ESRI fonts available. ArcGIS products install these fonts to the default |
| 58 windows font folder ``c:\\windows\\fonts``. To make them available for the converter | 58 windows font folder ``c:\\windows\\fonts``. To make them available for the converter |
| 59 there has to be a MapServer font set (see | 59 there has to be a MapServer font set (see |
| 60 http://mapserver.org/mapfile/fontset.html). The MXD2map converter comes with an | 60 http://mapserver.org/mapfile/fontset.html). |
| 61 | |
| 62 The MXD2map converter comes with an | |
| 61 initial fontset containing all relevant ESRI fonts and the free font FreeSans. | 63 initial fontset containing all relevant ESRI fonts and the free font FreeSans. |
| 62 The font set file named fonts.txt can be edited and further fonts can be added. | 64 The font set file named fonts.txt can be edited and further fonts can be added. |
| 63 To use a font set, the file needs to be referenced in the MapServer template | 65 To use a font set, the file needs to be referenced in the MapServer template |
| 64 otherwise the converter can not create character symbols and will show up errors | 66 otherwise the converter can not create character symbols and will show up errors |
| 65 in the conversion process. | 67 in the conversion process. |
| 66 | 68 |
| 67 The converter uses a separate symbol file to provide symbol sets to the | 69 The converter uses a separate symbol file to provide symbol sets to the |
| 68 | |
| 69 template to have initial symbols available. If no symbol file is referenced a | 70 template to have initial symbols available. If no symbol file is referenced a |
| 70 new one is created by the converter if necessary. The resulting symbol set is | 71 new one is created by the converter if necessary. The resulting symbol set is |
| 71 written to the same directory as the output mapfile named | 72 written to the same directory as the output mapfile named |
| 72 [mapfile-name]-symbols.sym. | 73 [mapfile-name]-symbols.sym. |
| 73 | 74 |
| 114 * Simple Labeling-syntax (a subset of ArcGISs VBScript-labels) | 115 * Simple Labeling-syntax (a subset of ArcGISs VBScript-labels) |
| 115 | 116 |
| 116 * Other features | 117 * Other features |
| 117 | 118 |
| 118 * Umlauts are translated into its equivalents within LAYER-names, | 119 * Umlauts are translated into its equivalents within LAYER-names, |
| 119 CLASS-names and also mapfile-names. Though it is good standard not to | 120 CLASS-names and also mapfile-names. Though it is good standard not to |
| 120 use them since they mostly cause problems when using them within | 121 use them since they mostly cause problems when using them within |
| 121 OWS-related services. | 122 OWS-related services. |
| 122 * | 123 |