[Mapbender-commits] r6924 - trunk/mapbender/tools/wms_extent

[svn_mapbender at osgeo.org]

Author: armin11
Date: 2010-09-21 17:55:38 +0000 (Tue, 21 Sep 2010)
New Revision: 6924

Modified:
   trunk/mapbender/tools/wms_extent/readme.txt
Log:
Some better description for the extent render tool

Modified: trunk/mapbender/tools/wms_extent/readme.txt
===================================================================
--- trunk/mapbender/tools/wms_extent/readme.txt	2010-09-21 15:14:13 UTC (rev 6923)
+++ trunk/mapbender/tools/wms_extent/readme.txt	2010-09-21 17:55:38 UTC (rev 6924)
@@ -1,8 +1,8 @@
-Toolset to show a simple bounding box graphic with help of umn mapserver.
-Mapbender itselfs comes without a own server component. Therefor it is not so easy to show a simple graphic for the extents of the resources which are registrated in a mapbender database. It will be possible to do so with a mapbender or ol client and the use of javascript rendering. But it is much easier to render the bbox and the background service with the help of a mapserver installation. The bbox can be given as vsp to the mapserver and the mapserver decides to render a special symbol for a special area of the bbox. For mapserver a postgis database backend is used. The user can define the same database as used for mapbender installation.
+Tool to show a simple bounding box graphic which is rendered by mapserver.
+Mapbender itselfs comes without an own ows server component. Therefor it is not so easy to generate a simple graphic for the extents (bboxes) of the different resources (wms/layer/wfs/featuretypes/georss/kml) which are registrated in the mapbender meta-database. It will be possible to do it by using a mapbender or openlayers client and render the objects with javascript. An other possibility is to render the bbox and the background by using a wms server component. The bbox can be given as vendor specific parameters to mapserver and the server decides to render the geometry. It is easy to render different objects for different areas of the bounding boxes. For mapserver a postgis database backend is used. The user can define the same database as used for mapbender installation (if postgis is provided).
 Principle:
-vsp bbox to mapserv.cgi and generating a simple polygon by postgis functions on the fly. The polygon and/or the central point can be rendered by the mapserv itself. The url of the request will be defined in a special conf file and can be included by the module which needs the visualization of the extent.
-The principle is better than the solution with an own client because no special javascript data is used.
+Send vsp for bbox to mapserv.cgi and generating a simple polygon by postgis functions on the fly (data string). The polygon and/or the central point will be rendered by the mapserv process itself. The url of the request is defined in a special conf file and can be included by the module which needs the visualization of extents.
+The principle is better than the solution with a special client because no javascript data has to be send thru the browser and the rendering of bounding boxes is not time-consuming.
 
 List of files:
 tools/wms_extent/extent_service.conf