diff doku/source/functionality.txt @ 194:216105271856

Merged with Stephans commits.
author raimund renkert <raimund.renkert@intevation.de>
date Wed, 20 Jul 2011 16:27:49 +0200
parents 43f1cbdcd597
children 1e3a5019c4ed
line wrap: on
line diff
--- a/doku/source/functionality.txt	Wed Jul 20 16:17:16 2011 +0200
+++ b/doku/source/functionality.txt	Wed Jul 20 16:27:49 2011 +0200
@@ -1,3 +1,6 @@
+.. index:: features, functionality, configuration, runtime-parameter,
+commandline
+
 -------------
 Functionality
 -------------
@@ -9,7 +12,7 @@
 must have a valid and available data source and must not fit the
 :ref:`restriction-label` described in the appropriate section.
 
-.. image:: ../funktionsweise/funktionsweise-MXD-konverter.svg
+.. image:: ../funktionsweise/funktionsweise-MXD-konverter.png
 
 .. _howtouse-label:
 
@@ -25,6 +28,16 @@
 1. The converter.properties file (see converter.properties.sample)
 2. via commandline arguments
 
+The converter.properties.sample file::
+
+
+  # Java properties file for the MXD Converter Tool.
+  mxd = \\full\\path\\to\\mxd-file
+  map = \\full\\path\\to\\map-file
+  map-template = \\full\\path\\to\\mapfile-template
+
+Make sure  you mask backslahes with an additional backslash.
+
 Both take a parameter for the path to the mxd file, the outputfile and a mapfile
 template for initial mapfile config. Commandline parameters have a higher
 priority than the properties file.
@@ -40,7 +53,7 @@
 
 To have the full functionality for ArcGIS map conversion it is necessary to have
 the ESRI fonts available. ArcGIS products install these fonts to the default
-windows font folder "c:\\windows\\fonts". To make them available for the converter
+windows font folder ``c:\\windows\\fonts``. To make them available for the converter
 there has to be a MapServer font set (see
 http://mapserver.org/mapfile/fontset.html). The MXD2map converter comes with an
 initial fontset containing all relevant ESRI fonts and the free font FreeSans.
@@ -50,7 +63,7 @@
 in the conversion process.
 
 The converter uses a separate symbol file to provide symbol sets to the
-MapServer configuration. A pre-build symbol file can be referenced in the
+
 template to have initial symbols available. If no symbol file is referenced a
 new one is created by the converter if necessary. The resulting symbol set is
 written to the same directory as the output mapfile named
@@ -60,33 +73,37 @@
 Features
 --------
 
-Currently supported features:
+MXD2map currently supportes the following features:
 
- * The MXD2map converter can use ArcSDE database connections and local
-   shapefile datasources to create a mapfile.
+ * Datasources
+   * ArcSDE database connections (requires MapServer built against ArcSDE, Client-dlls needed)
+   * ESRI-Shapefiles
 
- * Convertable symbols:
+ * Symbols:
 
    * Simple marker symbols
    * Character marker symbols
    * Arrow marker symbols
+   * Symbols based on TTF-characters of special cartographic fonts
    * Any combination of character marker symbols
    * Linesymbols with pattern and cartographic attributes
    * Polygons filled with solid color and outline
-   * Polygons filled with a hatch and outline
-
- * Convertable layer:
+   * Polygons filled with a hatch and hatched outline
 
-   * Feature layer
-   * Layer containing unique values
-   * Layer containing class breaks
-   * Grouplayer with one grouplevel
+ * Layer types:
+
+   * Featurelayer (vectors) as POINT, LINESTRING and POLYGON
+   * Classifications with unique values
+   * Classifications with class breaks
+   * Grouplayers with one grouplevel (as MapServer does not support more than one nested level)
 
  * Further map attributes:
 
-   * Projection and units
-   * Min/max scale denominations
+   * Projections and units based on the EPSG-table
+   * Min/max scale denominations at layer and label-level
    * Map extents
    * Simple labeling
    * Filter and expressions
+   * ArcSDE Jointables
+   * 
 
This site is hosted by Intevation GmbH (Datenschutzerklärung und Impressum | Privacy Policy and Imprint)