[mapserver-commits] r12519 - branches/branch-6-0/docs/en/ogc trunk/docs/en/ogc

svn at osgeo.org svn at osgeo.org
Tue Sep 6 13:09:58 EDT 2011


Author: havatv
Date: 2011-09-06 10:09:58 -0700 (Tue, 06 Sep 2011)
New Revision: 12519

Modified:
   branches/branch-6-0/docs/en/ogc/wms_server.txt
   trunk/docs/en/ogc/wms_server.txt
Log:
wms capabilities, mandatory boundingbox, update of the wms_server documentation (#3067).

Modified: branches/branch-6-0/docs/en/ogc/wms_server.txt
===================================================================
--- branches/branch-6-0/docs/en/ogc/wms_server.txt	2011-09-06 13:50:10 UTC (rev 12518)
+++ branches/branch-6-0/docs/en/ogc/wms_server.txt	2011-09-06 17:09:58 UTC (rev 12519)
@@ -204,11 +204,12 @@
           
   (Note that "epsg" has to be in lowercase when used in the PROJ4 'init' directive.)
 
-  If the :ref:`MAP` :ref:`PROJECTION` block is provided in the format "init=epsg:xxxx" then MapServer 
-  will also use this information to generate a <BoundingBox> tag for the top-level 
-  layer in the WMS capabilities document. Note that the BoundingBox is an optional 
-  element of WMS capabilities, but it is good practice to allow MapServer to include 
-  it when possible.
+  If the :ref:`MAP` :ref:`PROJECTION` block is provided in the format
+  "init=epsg:xxxx" then MapServer will also use this information to
+  generate a <BoundingBox> tag for the top-level layer in the WMS
+  capabilities document.  BoundingBox is a mandatory element of WMS
+  capabilities for WMS 1.3.0 (for WMS 1.1.0 it is optional, but it is
+  good practice to allow MapServer to include it when possible).
 
   The above is sufficient for MapServer to recognize the EPSG code and include it in 
   SRS tags in the capabilities output (wms_srs metadata is not required in this case). 
@@ -260,11 +261,12 @@
   Layer PROJECTION and wms_srs metadata are defined exactly the same way as the 
   map's PROJECTION and wms_srs metadata.
 
-  For vector layers, if a PROJECTION block is provided in the format "init=epsg:xxxx" 
-  then MapServer will also use this information to generate a <BoundingBox> tag for 
-  this layer in the WMS capabilities document. Note that the BoundingBox is an 
-  optional element of WMS capabilities, but it is good practice to allow MapServer 
-  to include it when possible.
+  For vector layers, if a PROJECTION block is provided in the format
+  "init=epsg:xxxx" then MapServer will also use this information to
+  generate a <BoundingBox> tag for this layer in the WMS capabilities
+  document. BoundingBox is a mandatory element of WMS capabilities for
+  WMS 1.3.0 (for WMS 1.1.0 it is optional, but it is good practice to
+  allow MapServer to include it when possible).
 
 - **"wms_onlineresource" metadata:**
 

Modified: trunk/docs/en/ogc/wms_server.txt
===================================================================
--- trunk/docs/en/ogc/wms_server.txt	2011-09-06 13:50:10 UTC (rev 12518)
+++ trunk/docs/en/ogc/wms_server.txt	2011-09-06 17:09:58 UTC (rev 12519)
@@ -204,11 +204,12 @@
           
   (Note that "epsg" has to be in lowercase when used in the PROJ4 'init' directive.)
 
-  If the :ref:`MAP` :ref:`PROJECTION` block is provided in the format "init=epsg:xxxx" then MapServer 
-  will also use this information to generate a <BoundingBox> tag for the top-level 
-  layer in the WMS capabilities document. Note that the BoundingBox is an optional 
-  element of WMS capabilities, but it is good practice to allow MapServer to include 
-  it when possible.
+  If the :ref:`MAP` :ref:`PROJECTION` block is provided in the format
+  "init=epsg:xxxx" then MapServer will also use this information to
+  generate a <BoundingBox> tag for the top-level layer in the WMS
+  capabilities document.  BoundingBox is a mandatory element of WMS
+  capabilities for WMS 1.3.0 (for WMS 1.1.0 it is optional, but it is
+  good practice to allow MapServer to include it when possible).
 
   The above is sufficient for MapServer to recognize the EPSG code and include it in 
   SRS tags in the capabilities output (wms_srs metadata is not required in this case). 
@@ -260,11 +261,12 @@
   Layer PROJECTION and wms_srs metadata are defined exactly the same way as the 
   map's PROJECTION and wms_srs metadata.
 
-  For vector layers, if a PROJECTION block is provided in the format "init=epsg:xxxx" 
-  then MapServer will also use this information to generate a <BoundingBox> tag for 
-  this layer in the WMS capabilities document. Note that the BoundingBox is an 
-  optional element of WMS capabilities, but it is good practice to allow MapServer 
-  to include it when possible.
+  For vector layers, if a PROJECTION block is provided in the format
+  "init=epsg:xxxx" then MapServer will also use this information to
+  generate a <BoundingBox> tag for this layer in the WMS capabilities
+  document. BoundingBox is a mandatory element of WMS capabilities for
+  WMS 1.3.0 (for WMS 1.1.0 it is optional, but it is good practice to
+  allow MapServer to include it when possible).
 
 - **"wms_onlineresource" metadata:**
 



More information about the mapserver-commits mailing list