stephan@250: .. index:: restrictions, label, Raster, ArcSDE, SDE, workaround, picture-symols, windows, ArcEngine
stephan@202: .. _restriction-label:
rrenkert@183: 
stephan@139: ------------
stephan@139: Restrictions
stephan@139: ------------
stephan@139: 
stephan@250: Currently there are some restrictions in the usage of the converter. One
stephan@250: of the main restrictions is the fact that the converter currently only
stephan@250: runs on Windows. This is due to the fact that the needed ArcEngine did
stephan@250: never reliably work on Linux. This was tested with ArcEngine 10.0.
stephan@139: 
stephan@139: Supported datasources:
stephan@139: 
stephan@139:  * ArcSDE-passwords cannot be read since they are encrypted. The converter
stephan@188:    exports the string ``<PASSWORD>`` which needs to be replaced later on in the
stephan@188:    resulting mapfile.
stephan@139: 
stephan@188:  * Since MapServer cannot use a FileGeodatabase datasources (yet) the MXD2map
stephan@230:    does not support this datasource and will not transform the MXD-file at
stephan@230:    all. This may change in the near future.
rrenkert@182: 
stephan@230:  * Raster data is not supported by the converter yet, though ArcSDE
stephan@230:    Raster-support will be available in the near future.
rrenkert@182: 
rrenkert@182: Symbol support:
rrenkert@182: 
rrenkert@182:  * Line symbols with pattern cannot be combined with marker symbols. The
rrenkert@182:    converter reads all symbols and writes the corresponding styles to the
rrenkert@182:    resulting mapfile but the marker symbols are rendered without any gap.
stephan@188:    The resulting mapimage may not look as intended.
rrenkert@182: 
stephan@202:    .. hint::
stephan@188:      Workarround: For small marker symbols it is recommended to use a line symbol in
rrenkert@182:      combination with pattern (in ArcGIS called template) to create the
rrenkert@182:      symbology.
rrenkert@182:      The reason why marker symbols cannot be used in combination with a template
rrenkert@182:      is the difficulty to interpret the read attributes like marks and gaps and
rrenkert@182:      write the appropriate symbols with the appropiate gap to the mapfile.
rrenkert@182: 
rrenkert@182:  * The converter sets the width to 1 for line symbols that have a width
stephan@250:    smaller than 1. 
rrenkert@182: 
stephan@202:    .. tip::
stephan@202:      To avoid lines and line colors (specially outlines) to be handled by the
rrenkert@183:      converter, use integer numbers for line width only.
rrenkert@183: 
stephan@188:  * In ArcGIS maps default symbols can be defined as fallback within classifications. 
stephan@188:    Since MapServer does not support such fallback symbols or styles
stephan@188:    within classifications the converter does not read these default symbols.
rrenkert@182: 
rrenkert@182:  * In ArcGIS predefined symbols like bars or pie charts can be used to display
stephan@188:    values. The converter does not support these symbols yet.
rrenkert@182: 
rrenkert@183: Layer support:
rrenkert@183: 
rrenkert@206:  * Expressions for label are parsed by an internal parser in ArcGIS. The
stephan@230:    interpretation of this expressions is very limited though.
rrenkert@206:    Therefore label expressions may not contain any special functions or must fit
rrenkert@206:    the mapserver expression design pattern.
rrenkert@206: