[MXD2map-commits] r232:4fc0635000d6
scm-commit@wald.intevation.org
scm-commit at wald.intevation.org
Fri Aug 5 08:21:49 CEST 2011
details: http://hg.intevation.org/geospatial/mxd2map/rev/4fc0635000d6
changeset: 232:4fc0635000d6
user: Stephan Holl <stephan.holl at intevation.de>
date: Mon Aug 01 10:56:15 2011 +0200
description:
Merged with upstream
diffstat:
INSTALL.txt | 111 ++++++++++++++++++++++++++++-------------
doku/source/functionality.txt | 15 +++-
doku/source/restrictions.txt | 19 ++++---
3 files changed, 97 insertions(+), 48 deletions(-)
diffs (235 lines):
diff -r 656da3f693b8 -r 4fc0635000d6 INSTALL.txt
--- a/INSTALL.txt Thu Jul 28 16:30:22 2011 +0200
+++ b/INSTALL.txt Mon Aug 01 10:56:15 2011 +0200
@@ -1,22 +1,25 @@
-.. index:: installation, requirements, apache, UMN MapServer, compile, jar
+.. index:: installation, requirements, apache, UMN MapServer, compile,
+ jar, logging, ArcSDE
------------
Requirements
------------
The current version of the converter only runs on Windows. This is because
-the ArcObjects JDK API is not running properly on Linux though.
+the ArcObjects JDK API is not running properly on Linux though. In theory
+it should also run on Linux.
To run the converter you need at least the following componentes:
* Sun Java6 SDK to build, JRE to run
* ArcGIS Desktop10.x or ArcEngine10.x with a valid licence enabled
* UMN MapServer with Java MapScript-bindings (>=6.0.1 or recent development-version)
- * Apache2 Webserver for displaying the resulting Mapfiles
+ * Optinal: Apache2 Webserver for displaying the resulting Mapfiles
* Optional: MapServer compiled with ArcSDE-plugin
* Optional: GDAL/OGR compiled with ArcSDE-support
- * Optional: GDAL/OGR compiled with FileGeodatabase-support
- * Optional: Other GDAL/OGR-related tools.
+ * Optional: GDAL/OGR compiled with FileGeodatabase-support
+ * Optional: Other GDAL/OGR-related tools
+ * Optional: Sphinx for building the docs
------------
@@ -36,38 +39,6 @@
ant jar-norevision
-Install Apache Webserver
-------------------------
-
-Install Apache webserver by exedcuting the .msi-file and follow the
-install-dialogs::
-
- httpd-2.2.19-win32-x86-openssl-0.9.8r.msi
-
-Make sure that you install apache as a service so it will be available
-directly after system bootup.
-
-
-Install UMN MapServer
----------------------
-
-The current documentation uses the Windows binary-builds from http://www.gisinternals.com/sdk/
-
-1. Unzip the ZIP-file at ``c:/ms_6.1-dev``
-
-#. Configure Apache Webserver to find the cgi-bin-folder::
-
- ScriptAlias /cgi-bin/ "C:/ms_6.1-dev/bin/"
-
- <Location "/cgi-bin">
- Options None
- Order allow,deny
- Allow from all
- </Location>
-
-#. Copy mapserv.exe from ``c:/ms_6.1-dev/bin/apps/ms`` to ``c:/ms_6.1-dev/bin/``
-
-
Create run-environment
----------------------
@@ -140,3 +111,71 @@
The above batch-script ``SDKShell.bat`` needs to be sources before working
with MXD2map.
+
+Install Apache Webserver
+------------------------
+
+If you will be able to display the resulting mapfiles directly you need to
+install a webserver like Apache2 and the UMN MapServer CGI-file
+``mapserv.exe``.
+
+Install Apache webserver by exedcuting the .msi-file and follow the
+install-dialogs::
+
+ httpd-2.2.19-win32-x86-openssl-0.9.8r.msi
+
+Make sure that you install apache as a service so it will be available
+directly after system bootup.
+
+
+Install UMN MapServer
+---------------------
+
+The current documentation uses the Windows binary-builds from http://www.gisinternals.com/sdk/
+
+1. Unzip the ZIP-file at ``c:/ms_6.1-dev``
+
+#. Configure Apache Webserver to find the cgi-bin-folder::
+
+ ScriptAlias /cgi-bin/ "C:/ms_6.1-dev/bin/"
+
+ <Location "/cgi-bin">
+ Options None
+ Order allow,deny
+ Allow from all
+ </Location>
+
+#. Copy mapserv.exe from ``c:/ms_6.1-dev/bin/apps/ms`` to ``c:/ms_6.1-dev/bin/``
+
+
+Configure Logging
+-----------------
+
+Logging is supported on different levels. MXD2map logs with Javas Log4J. A
+sample configuration could look like this::
+
+ #### Log just errors and warnings to a file.
+ log4j.rootLogger=DEBUG, MXD, Console
+
+ log4j.appender.MXD=org.apache.log4j.RollingFileAppender
+ log4j.appender.MXD.File=./logs/console-client.log
+ log4j.appender.MXD.MaxFileSize=5000KB
+ log4j.appender.MXD.MaxBackupIndex=1
+ log4j.appender.MXD.layout=org.apache.log4j.PatternLayout
+ log4j.appender.MXD.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
+
+ #log4j.rootLogger=WARN, Console
+ log4j.appender.Console=org.apache.log4j.ConsoleAppender
+ log4j.appender.Console.Threshold=INFO
+ log4j.appender.Console.layout=org.apache.log4j.PatternLayout
+ log4j.appender.Console.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
+
+
+Apache Webserver and UMN MapServer
+..................................
+
+They both support logging. MapServers outout ends up in Apaches logfiles
+if not configured differently within a providing template. The loglevel
+can be adjusted at template-level. For further information consult the UMN
+MapServer manual regarding logging at
+http://mapserver.org/optimization/debugging.html#steps-to-enable-mapserver-debugging.
diff -r 656da3f693b8 -r 4fc0635000d6 doku/source/functionality.txt
--- a/doku/source/functionality.txt Thu Jul 28 16:30:22 2011 +0200
+++ b/doku/source/functionality.txt Mon Aug 01 10:56:15 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 656da3f693b8 -r 4fc0635000d6 doku/source/restrictions.txt
--- a/doku/source/restrictions.txt Thu Jul 28 16:30:22 2011 +0200
+++ b/doku/source/restrictions.txt Mon Aug 01 10:56:15 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