Mercurial > mxd2map
comparison doku/source/restrictions.txt @ 250:d10fd4de02aa
Documented a bunch of new features
* Support of picture-marker symbol (issue343)
* Support for ArcGIS named groups (issue381)
* GLOBAL and Layer extents and SRS (issue 379)
| author | Stephan Holl <stephan.holl@intevation.de> |
|---|---|
| date | Fri, 12 Aug 2011 09:15:34 +0200 |
| parents | df533a03ad9f |
| children | 4dc2b9aa3c57 |
comparison
equal
deleted
inserted
replaced
| 249:4c59d8c36418 | 250:d10fd4de02aa |
|---|---|
| 1 .. index:: restrictions, label, Raster, SDE, workaround, picture-symols | 1 .. index:: restrictions, label, Raster, ArcSDE, SDE, workaround, picture-symols, windows, ArcEngine |
| 2 .. _restriction-label: | 2 .. _restriction-label: |
| 3 | 3 |
| 4 ------------ | 4 ------------ |
| 5 Restrictions | 5 Restrictions |
| 6 ------------ | 6 ------------ |
| 7 | 7 |
| 8 Currently there are some restrictions in the usage of the converter: | 8 Currently there are some restrictions in the usage of the converter. One |
| 9 of the main restrictions is the fact that the converter currently only | |
| 10 runs on Windows. This is due to the fact that the needed ArcEngine did | |
| 11 never reliably work on Linux. This was tested with ArcEngine 10.0. | |
| 9 | 12 |
| 10 Supported datasources: | 13 Supported datasources: |
| 11 | 14 |
| 12 * ArcSDE-passwords cannot be read since they are encrypted. The converter | 15 * ArcSDE-passwords cannot be read since they are encrypted. The converter |
| 13 exports the string ``<PASSWORD>`` which needs to be replaced later on in the | 16 exports the string ``<PASSWORD>`` which needs to be replaced later on in the |
| 34 The reason why marker symbols cannot be used in combination with a template | 37 The reason why marker symbols cannot be used in combination with a template |
| 35 is the difficulty to interpret the read attributes like marks and gaps and | 38 is the difficulty to interpret the read attributes like marks and gaps and |
| 36 write the appropriate symbols with the appropiate gap to the mapfile. | 39 write the appropriate symbols with the appropiate gap to the mapfile. |
| 37 | 40 |
| 38 * The converter sets the width to 1 for line symbols that have a width | 41 * The converter sets the width to 1 for line symbols that have a width |
| 39 smaller than 1. Outlines with a width smaller than 1 are drawn in the fill | 42 smaller than 1. |
| 40 color of the ploygon and the width is set to 1. | |
| 41 | 43 |
| 42 .. tip:: | 44 .. tip:: |
| 43 To avoid lines and line colors (specially outlines) to be handled by the | 45 To avoid lines and line colors (specially outlines) to be handled by the |
| 44 converter, use integer numbers for line width only. | 46 converter, use integer numbers for line width only. |
| 45 | |
| 46 * Picture symbols are not supported by the converter since ArcGIS embedds | |
| 47 the image directly into the MXDfile. This might be supported in the | |
| 48 near future. | |
| 49 | 47 |
| 50 * In ArcGIS maps default symbols can be defined as fallback within classifications. | 48 * In ArcGIS maps default symbols can be defined as fallback within classifications. |
| 51 Since MapServer does not support such fallback symbols or styles | 49 Since MapServer does not support such fallback symbols or styles |
| 52 within classifications the converter does not read these default symbols. | 50 within classifications the converter does not read these default symbols. |
| 53 | 51 |
| 54 * In ArcGIS predefined symbols like bars or pie charts can be used to display | 52 * In ArcGIS predefined symbols like bars or pie charts can be used to display |
| 55 values. The converter does not support these symbols yet. | 53 values. The converter does not support these symbols yet. |
| 56 | 54 |
| 57 Layer support: | 55 Layer support: |
| 58 | 56 |
| 59 * Group-layers are represented as WMS Named Layers (not requestable via | |
| 60 GetMap-Request). WMS-clients can recognize them as | |
| 61 'organisation-layers'. | |
| 62 * Expressions for label are parsed by an internal parser in ArcGIS. The | 57 * Expressions for label are parsed by an internal parser in ArcGIS. The |
| 63 interpretation of this expressions is very limited though. | 58 interpretation of this expressions is very limited though. |
| 64 Therefore label expressions may not contain any special functions or must fit | 59 Therefore label expressions may not contain any special functions or must fit |
| 65 the mapserver expression design pattern. | 60 the mapserver expression design pattern. |
| 66 | 61 |