Mercurial > mxd2map
comparison doku/source/functionality.txt @ 182:91e2d46d7968
Added functionality, restrictions and how to build runtime enviroment
to documentation.
| author | Raimund Renkert <rrenkert@intevation.de> |
|---|---|
| date | Mon, 18 Jul 2011 15:12:24 +0200 |
| parents | |
| children | fe6dbfc86144 |
comparison
equal
deleted
inserted
replaced
| 181:0bde090506f9 | 182:91e2d46d7968 |
|---|---|
| 1 ------------- | |
| 2 Functionality | |
| 3 ------------- | |
| 4 | |
| 5 The MXD2map converter works as a commandline tool to transform maps from the | |
| 6 proprietary ArcGIS file format "MXD" to a MapServer configuration file. | |
| 7 | |
| 8 To transform an ArcGIS mxd file to a MapServer configuration file the mxd file | |
| 9 must have a valid and available data source and must not fit the restrictions | |
| 10 described in the appropriate section. | |
| 11 | |
| 12 How to use | |
| 13 ---------- | |
| 14 The converter is started via the commandline running the command:: | |
| 15 | |
| 16 $java -jar mxd2map.jar | |
| 17 | |
| 18 The converter can be configured in two ways: | |
| 19 | |
| 20 1. The converter.properties file (see converter.properties.sample) | |
| 21 2. via commandline arguments | |
| 22 | |
| 23 Both take a parameter for the path to the mxd file, the outputfile and a mapfile | |
| 24 template for initial mapfile config. Commandline parameters have a higher | |
| 25 priority than the properties file. | |
| 26 | |
| 27 The available parameters on the commandline are:: | |
| 28 | |
| 29 -m or --mxd The mxd file to convert. | |
| 30 | |
| 31 -a or --map The path to the output file. Should end with ".map". | |
| 32 | |
| 33 -t or --template The template to use for an initial mapfile | |
| 34 configuration. | |
| 35 | |
| 36 To have the full functionality for ArcGIS map conversion it is necessary to have | |
| 37 the ESRI fonts available. ArcGIS products install these fonts to the default | |
| 38 windows font folder "c:\\windows\\fonts". To make them available for the converter | |
| 39 there has to be a MapServer font set (see | |
| 40 http://mapserver.org/mapfile/fontset.html). The MXD2map converter comes with an | |
| 41 initial fontset containing all relevant ESRI fonts and the free font FreeSans. | |
| 42 The font set file named fonts.txt can be edited and further fonts can be added. | |
| 43 To use a font set, the file needs to be referenced in the MapServer template | |
| 44 otherwise the converter can not create character symbols and will show up errors | |
| 45 in the conversion process. | |
| 46 | |
| 47 The converter uses a separate symbol file to provide symbol sets to the | |
| 48 MapServer configuration. A pre-build symbol file can be referenced in the | |
| 49 template to have initial symbols available. If no symbol file is referenced a | |
| 50 new one is created by the converter if necessary. The resulting symbol set is | |
| 51 written to the same directory as the output mapfile named | |
| 52 [mapfile-name]-symbols.sym. | |
| 53 | |
| 54 | |
| 55 Features | |
| 56 -------- | |
| 57 | |
| 58 Currently supported features: | |
| 59 | |
| 60 * The MXD2map converter can use ArcSDE database connections and local | |
| 61 shapefile datasources to create a mapfile. | |
| 62 | |
| 63 * Convertable symbols: | |
| 64 | |
| 65 * Simple marker symbols | |
| 66 * Character marker symbols | |
| 67 * Arrow marker symbols | |
| 68 * Any combination of character marker symbols | |
| 69 * Linesymbols with pattern and cartographic attributes | |
| 70 * Polygons filled with solid color and outline | |
| 71 * Polygons filled with a hatch and outline | |
| 72 | |
| 73 * Convertable layer: | |
| 74 | |
| 75 * Feature layer | |
| 76 * Layer containing unique values | |
| 77 * Layer containing class breaks | |
| 78 * Grouplayer with one grouplevel | |
| 79 | |
| 80 * Further map attributes: | |
| 81 | |
| 82 * Projection and units | |
| 83 * Min/max scale denominations | |
| 84 * Map extents | |
| 85 * Simple labeling | |
| 86 * Filter and expressions | |
| 87 |