[MXD2map-commits] r230:df533a03ad9f

scm-commit@wald.intevation.org scm-commit at wald.intevation.org
Fri Jul 29 21:46:23 CEST 2011


details:   http://hg.intevation.org/geospatial/mxd2map/rev/df533a03ad9f

changeset: 230:df533a03ad9f

user:      Stephan Holl <stephan.holl at intevation.de>

date:      Fri Jul 29 17:33:19 2011 +0200

description:
completed the features and restrictions-section


diffstat:

 doku/source/functionality.txt |  15 ++++++++++-----
 doku/source/restrictions.txt  |  19 +++++++++++--------
 2 files changed, 21 insertions(+), 13 deletions(-)

diffs (90 lines):

diff -r 64cd6a115372 -r df533a03ad9f doku/source/functionality.txt
--- a/doku/source/functionality.txt	Fri Jul 29 07:41:29 2011 +0200
+++ b/doku/source/functionality.txt	Fri Jul 29 17:33:19 2011 +0200
@@ -77,8 +77,9 @@
 
 MXD2map currently supportes the following features:
 
- * Datasources
-   * ArcSDE database connections (requires MapServer built against ArcSDE, Client-dlls needed)
+ * Datasources:
+
+   * ArcSDE vector database connections (requires MapServer built against ArcSDE, Client-dlls needed)
    * ESRI-Shapefiles
 
  * Symbols:
@@ -97,7 +98,9 @@
    * 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)
+   * Group-members are concatinated to group.layername. This ensures having discrete layernames
+   * ArcGIS-layergroups are represented as WMS Named layers, which are WMS-layers without a title (so not requestable throuhg GetMap)
+   * all definition-queries for filtering the data on Layer- and classification-level
 
  * Further map attributes:
 
@@ -108,10 +111,12 @@
    * Filter and expressions
    * ArcSDE Jointables
    * Mapfile-Templating for OGC-related stuff
+   * Simple Labeling-syntax (a subset of ArcGISs VBScript-labels)
 
  * Other features
 
-   * Umlauts are translated into its equivalents within LAYERnames,
-   CLASSnames and also mapfile-names. Though it is good standard not to
+   * Umlauts are translated into its equivalents within LAYER-names,
+   CLASS-names and also mapfile-names. Though it is good standard not to
    use them since they mostly cause problems when using them within
    OWS-related services.
+   * 
diff -r 64cd6a115372 -r df533a03ad9f doku/source/restrictions.txt
--- a/doku/source/restrictions.txt	Fri Jul 29 07:41:29 2011 +0200
+++ b/doku/source/restrictions.txt	Fri Jul 29 17:33:19 2011 +0200
@@ -1,4 +1,4 @@
-.. index:: restrictions
+.. index:: restrictions, label, Raster, SDE, workaround, picture-symols
 .. _restriction-label:
 
 ------------
@@ -14,9 +14,11 @@
    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.
+   does not support this datasource and will not transform the MXD-file at
+   all. This may change in the near future.
 
- * Raster data is not supported by the converter yet.
+ * Raster data is not supported by the converter yet, though ArcSDE
+   Raster-support will be available in the near future.
 
 Symbol support:
 
@@ -42,7 +44,8 @@
      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.
+   the image directly into the MXDfile. This might be supported in the
+   near future.
 
  * In ArcGIS maps default symbols can be defined as fallback within classifications. 
    Since MapServer does not support such fallback symbols or styles
@@ -53,11 +56,11 @@
 
 Layer support:
 
- * Grouplayer with more than  one group level are not supported by the MapServer
-   and even not by the converter.
-
+ * Group-layers are represented as WMS Named Layers (not requestable via
+   GetMap-Request). WMS-clients can recognize them as
+   'organisation-layers'.
  * Expressions for label are parsed by an internal parser in ArcGIS. The
-   expressions designed for this parser cannot be interpreted by the mapserver.
+   interpretation of this expressions is very limited though.
    Therefore label expressions may not contain any special functions or must fit
    the mapserver expression design pattern.
 


More information about the MXD2map-commits mailing list