[mapserver-commits] r12597 - branches/branch-6-0/docs/en/ogc
trunk/docs/en/ogc
svn at osgeo.org
svn at osgeo.org
Wed Sep 28 18:36:48 EDT 2011
Author: havatv
Date: 2011-09-28 15:36:48 -0700 (Wed, 28 Sep 2011)
New Revision: 12597
Modified:
branches/branch-6-0/docs/en/ogc/wms_server.txt
trunk/docs/en/ogc/wms_server.txt
Log:
Improvement of the wms_server document - templates, gml output (#3208).
Modified: branches/branch-6-0/docs/en/ogc/wms_server.txt
===================================================================
--- branches/branch-6-0/docs/en/ogc/wms_server.txt 2011-09-28 21:27:18 UTC (rev 12596)
+++ branches/branch-6-0/docs/en/ogc/wms_server.txt 2011-09-28 22:36:48 UTC (rev 12597)
@@ -68,9 +68,11 @@
- text/plain output with attribute info.
- - text/html output using MapServer query templates specified in the CLASS
- template parameter. The MIME type returned by the Class templates defaults
- to text/html and can be controlled using the metadata "wms_feature_info_mime_type".
+ - text/html output using MapServer query templates (see
+ :ref:`template`) specified in the :ref:`CLASS` TEMPLATE parameter
+ (the filename has to have an .html extension). The MIME type
+ returned by the Class templates defaults to text/html and can be
+ controlled using the metadata "wms_feature_info_mime_type".
- application/vnd.ogc.gml, GML.1 or GML for GML features.
@@ -169,7 +171,7 @@
- Layers set to STATUS DEFAULT will always be sent to the client.
- Layers set to STATUS ON or STATUS OFF can be requested by the client.
-- Layer TEMPLATE (required for GetFeatureInfo requests)
+- Layer TEMPLATE (required for GetFeatureInfo requests - see :ref:`template`)
- Layer DUMP TRUE (only required for GetFeatureInfo GML requests)
Let's go through each of these parameters in more detail:
@@ -309,18 +311,22 @@
- **Configuring for GetFeatureInfo Requests:**
- You must set the layer TEMPLATE parameter for the layer to be queryable by
- GetFeatureInfo requests. For requests of type "text/html" you should also set
- the layer HEADER and FOOTER parameters.
+ You must set the layer TEMPLATE parameter for the layer to be
+ queryable by GetFeatureInfo requests (see :ref:`template`). For
+ requests of type "text/html" you should also set the layer HEADER
+ and FOOTER parameters.
- For GetFeatureInfo requests of GML you must set the layer to DUMP TRUE in the
- mapfile. As of MapServer 4.6 you must also set the *gml_\** metadata for the
- layer attributes to be served (see the Layer Object metadata in the Reference
- Section later in this document).
+ For GetFeatureInfo requests of GML you must set the layer to DUMP
+ TRUE in the mapfile. As of MapServer 4.6 you must set the *gml_\**
+ metadata for the layer attributes to be served (see the Layer Object
+ metadata in the Reference Section later in this document). To
+ include geometry, gml_geometries and gml_[name]_type has to be
+ specified.
- Here are working examples of GetFeatureInfo requests: `text/plain`_ / `text/html`_
- / `gml`_ (for gml, your browser might ask you to save the file, if so save it
- locally as a .gml file and view it in a text editor)
+ Here are working examples of GetFeatureInfo requests: `text/plain`_
+ / `text/html`_ / `gml`_ (for gml, your browser might ask you to save
+ the file, if so save it locally as a .gml file and view it in a text
+ editor)
Test Your WMS Server
--------------------
@@ -967,12 +973,13 @@
- Used to specify an additional MIME type that can be used when responding
to the GetFeature request.
- For example if you want to use the layer's HTML template as a base for its
- response, you need to add "WMS_FEATURE_INFO_MIME_TYPE" "text/html".
- Setting this will have the effect of advertizing text/html as one of the
- MIME types supported for a GetFeature request. You also need to make sure
- that the layer points to a valid html template. The client can then call
- the server with INFO_FORMAT=text/html.
+ For example if you want to use the layer's HTML template as a base
+ for its response, you need to add "WMS_FEATURE_INFO_MIME_TYPE"
+ "text/html". Setting this will have the effect of advertizing
+ text/html as one of the MIME types supported for a GetFeature
+ request. You also need to make sure that the layer points to a
+ valid html template (see :ref:`template`). The client can then
+ call the server with INFO_FORMAT=text/html.
- If not specified, MapServer by default has text/plain and GML implemented.
- Note that for GML to be returned the layer in the wms-server mapfile must
Modified: trunk/docs/en/ogc/wms_server.txt
===================================================================
--- trunk/docs/en/ogc/wms_server.txt 2011-09-28 21:27:18 UTC (rev 12596)
+++ trunk/docs/en/ogc/wms_server.txt 2011-09-28 22:36:48 UTC (rev 12597)
@@ -68,9 +68,11 @@
- text/plain output with attribute info.
- - text/html output using MapServer query templates specified in the CLASS
- template parameter. The MIME type returned by the Class templates defaults
- to text/html and can be controlled using the metadata "wms_feature_info_mime_type".
+ - text/html output using MapServer query templates (see
+ :ref:`template`) specified in the :ref:`CLASS` TEMPLATE parameter
+ (the filename has to have an .html extension). The MIME type
+ returned by the Class templates defaults to text/html and can be
+ controlled using the metadata "wms_feature_info_mime_type".
- application/vnd.ogc.gml, GML.1 or GML for GML features.
@@ -169,7 +171,7 @@
- Layers set to STATUS DEFAULT will always be sent to the client.
- Layers set to STATUS ON or STATUS OFF can be requested by the client.
-- Layer TEMPLATE (required for GetFeatureInfo requests)
+- Layer TEMPLATE (required for GetFeatureInfo requests - see :ref:`template`)
- Layer DUMP TRUE (only required for GetFeatureInfo GML requests)
Let's go through each of these parameters in more detail:
@@ -309,18 +311,22 @@
- **Configuring for GetFeatureInfo Requests:**
- You must set the layer TEMPLATE parameter for the layer to be queryable by
- GetFeatureInfo requests. For requests of type "text/html" you should also set
- the layer HEADER and FOOTER parameters.
+ You must set the layer TEMPLATE parameter for the layer to be
+ queryable by GetFeatureInfo requests (see :ref:`template`). For
+ requests of type "text/html" you should also set the layer HEADER
+ and FOOTER parameters.
- For GetFeatureInfo requests of GML you must set the layer to DUMP TRUE in the
- mapfile. As of MapServer 4.6 you must also set the *gml_\** metadata for the
- layer attributes to be served (see the Layer Object metadata in the Reference
- Section later in this document).
+ For GetFeatureInfo requests of GML you must set the layer to DUMP
+ TRUE in the mapfile. As of MapServer 4.6 you must set the *gml_\**
+ metadata for the layer attributes to be served (see the Layer Object
+ metadata in the Reference Section later in this document). To
+ include geometry, gml_geometries and gml_[name]_type has to be
+ specified.
- Here are working examples of GetFeatureInfo requests: `text/plain`_ / `text/html`_
- / `gml`_ (for gml, your browser might ask you to save the file, if so save it
- locally as a .gml file and view it in a text editor)
+ Here are working examples of GetFeatureInfo requests: `text/plain`_
+ / `text/html`_ / `gml`_ (for gml, your browser might ask you to save
+ the file, if so save it locally as a .gml file and view it in a text
+ editor)
Test Your WMS Server
--------------------
@@ -967,12 +973,13 @@
- Used to specify an additional MIME type that can be used when responding
to the GetFeature request.
- For example if you want to use the layer's HTML template as a base for its
- response, you need to add "WMS_FEATURE_INFO_MIME_TYPE" "text/html".
- Setting this will have the effect of advertizing text/html as one of the
- MIME types supported for a GetFeature request. You also need to make sure
- that the layer points to a valid html template. The client can then call
- the server with INFO_FORMAT=text/html.
+ For example if you want to use the layer's HTML template as a base
+ for its response, you need to add "WMS_FEATURE_INFO_MIME_TYPE"
+ "text/html". Setting this will have the effect of advertizing
+ text/html as one of the MIME types supported for a GetFeature
+ request. You also need to make sure that the layer points to a
+ valid html template (see :ref:`template`). The client can then
+ call the server with INFO_FORMAT=text/html.
- If not specified, MapServer by default has text/plain and GML implemented.
- Note that for GML to be returned the layer in the wms-server mapfile must
More information about the mapserver-commits
mailing list