.. index:: restrictions
.. _restriction-label:

------------
Restrictions
------------

Currently there are some restrictions in the usage of the converter:

Supported datasources:

 * ArcSDE-passwords cannot be read since they are encrypted. The converter
   exports the string ``<PASSWORD>`` which needs to be replaced later on in the
   resulting mapfile.

 * Since MapServer cannot use a FileGeodatabase datasources (yet) the MXD2map
   does not support this datasource and will not transform the MXD-file at all.

 * Raster data is not supported by the converter yet.

Symbol support:

 * Line symbols with pattern cannot be combined with marker symbols. The
   converter reads all symbols and writes the corresponding styles to the
   resulting mapfile but the marker symbols are rendered without any gap.
   The resulting mapimage may not look as intended.

   .. hint::
     Workarround: For small marker symbols it is recommended to use a line symbol in
     combination with pattern (in ArcGIS called template) to create the
     symbology.
     The reason why marker symbols cannot be used in combination with a template
     is the difficulty to interpret the read attributes like marks and gaps and
     write the appropriate symbols with the appropiate gap to the mapfile.

 * The converter sets the width to 1 for line symbols that have a width
   smaller than 1. Outlines with a width smaller than 1 are drawn in the fill
   color of the ploygon and the width is set to 1.

   .. tip::
     To avoid lines and line colors (specially outlines) to be handled by the
     converter, use integer numbers for line width only.

 * Picture symbols are not supported by the converter since ArcGIS embedds
   the image directly into the MXDfile.

 * In ArcGIS maps default symbols can be defined as fallback within classifications. 
   Since MapServer does not support such fallback symbols or styles
   within classifications the converter does not read these default symbols.

 * In ArcGIS predefined symbols like bars or pie charts can be used to display
   values. The converter does not support these symbols yet.

Layer support:

 * Grouplayer with more than  one group level are not supported by the MapServer
   and even not by the converter.

 * Expressions for label are parsed by an internal parser in ArcGIS. The
   expressions designed for this parser cannot be interpreted by the mapserver.
   Therefore label expressions may not contain any special functions or must fit
   the mapserver expression design pattern.