[mapserver-commits] r8201 - in trunk/docs: input/vector mapfile ogc
svn at osgeo.org
svn at osgeo.org
Sun Dec 7 17:08:53 EST 2008
Author: hobu
Date: 2008-12-07 17:08:52 -0500 (Sun, 07 Dec 2008)
New Revision: 8201
Modified:
trunk/docs/input/vector/kml.txt
trunk/docs/mapfile/projection.txt
trunk/docs/ogc/filter_encoding.txt
trunk/docs/ogc/mapcontext.txt
trunk/docs/ogc/mapscript.txt
Log:
internal referencing and indexing
Modified: trunk/docs/input/vector/kml.txt
===================================================================
--- trunk/docs/input/vector/kml.txt 2008-12-07 20:30:22 UTC (rev 8200)
+++ trunk/docs/input/vector/kml.txt 2008-12-07 22:08:52 UTC (rev 8201)
@@ -4,7 +4,8 @@
KML - Keyhole Markup Language
*****************************************************************************
-Keyhole Markup Language (KML) is an XML-based language for managing the display of 3D geospatial data.
+Keyhole Markup Language (KML) is an XML-based language for managing the
+display of 3D geospatial data.
Data Access / Connection Method
@@ -28,7 +29,8 @@
OGRINFO Examples
----------------
-First you should make sure that your GDAL/OGR build contains the "KML" driver, by using the '--formats' command:
+First you should make sure that your GDAL/OGR build contains the "KML" driver,
+by using the '--formats' command:
::
Modified: trunk/docs/mapfile/projection.txt
===================================================================
--- trunk/docs/mapfile/projection.txt 2008-12-07 20:30:22 UTC (rev 8200)
+++ trunk/docs/mapfile/projection.txt 2008-12-07 22:08:52 UTC (rev 8201)
@@ -40,7 +40,7 @@
.. note::
This refers to an EPSG lookup file that contains a '26915' code with the
- full projection parameters)
+ full projection parameters.
The next two examples both display how to possibly define unprojected
lat/longs ("geographic"):
Modified: trunk/docs/ogc/filter_encoding.txt
===================================================================
--- trunk/docs/ogc/filter_encoding.txt 2008-12-07 20:30:22 UTC (rev 8200)
+++ trunk/docs/ogc/filter_encoding.txt 2008-12-07 22:08:52 UTC (rev 8201)
@@ -146,7 +146,8 @@
your WFS server, the document returned should contain the supported filters.
Here is part of a Capabilities document as well as the Post support:
-::
+.. code-block:: guess
+ :linenos:
<?xml version='1.0' encoding="ISO-8859-1" ?>
<WFS_Capabilities
@@ -464,24 +465,34 @@
- Not supported.
-3. *Tests number 1.3.4.2, 1.3.4.4 to 1.3.4.7 (see bug 461 on MapServer Web site)*:
+3. *Tests number 1.3.4.2, 1.3.4.4 to 1.3.4.7*:
- The string comparison is not supported using >, <, >=, <=.
- The date comparison is not supported.
+
+ .. seealso::
+
+ `bug 461`_
4. *Test number 1.3.4.10*:
- This property is not supported in MapServer.
-5. *Test number 1.3.6.1 (see bug 461 on MapServer Web site)*:
-
+5. *Test number 1.3.6.1*:
+
- The returned feature xml won't validate because the validation is done
against a specific xsd (geomatry.xsd).
- - The data conversion on multipoints and multilayers are not supported within gdal.
+ - The data conversion on multipoints and multilayers are not supported within GDAL.
+
+ .. seealso::
+
+ `bug 461`_
6. *Test number 2*:
- The transaction requests are not supported.
+.. _`bug 461`: http://trac.osgeo.org/mapserver/ticket/461
+
Modified: trunk/docs/ogc/mapcontext.txt
===================================================================
--- trunk/docs/ogc/mapcontext.txt 2008-12-07 20:30:22 UTC (rev 8200)
+++ trunk/docs/ogc/mapcontext.txt 2008-12-07 22:08:52 UTC (rev 8201)
@@ -17,25 +17,27 @@
Introduction
============
-The term 'map context' comes from the Open Geospatial Constortium's (OGC)
-`Web Map Context Specification v1.0.0`_, which coincides with the OGC `Web Map Server
-Specification (WMS) v1.1.1`_. A map context is a XML document that describes the
-appearance of layers from one or more WMS servers, and can be transferred between
-clients while maintaining startup views, the state of the view (and its layers),
-and storing additional layer information.
+The term 'map context' comes from the Open Geospatial Constortium's (OGC) `Web
+Map Context Specification v1.0.0`_, which coincides with the OGC `Web Map
+Server Specification (WMS) v1.1.1`_. A map context is a XML document that
+describes the appearance of layers from one or more WMS servers, and can be
+transferred between clients while maintaining startup views, the state of the
+view (and its layers), and storing additional layer information.
-Support for OGC Web Map Context was added to MapServer in version 3.7/4.0. This
-allows client applications to load and save a map configuration in a standard XML format.
-MapServer can read context documents of versions 0.1.2, 0.1.4, 0.1.7, 1.0.0, 1.1.0 and
-can export contents in versions 0.1.4, 0.1.7, 1.0.0, 1.1.0. Web Map Context 1.1.0
-support was added to MapServer 4.10
+Support for OGC Web Map Context was added to MapServer in version 3.7/4.0.
+This allows client applications to load and save a map configuration in a
+standard XML format. MapServer can read context documents of versions 0.1.2,
+0.1.4, 0.1.7, 1.0.0, 1.1.0 and can export contents in versions 0.1.4, 0.1.7,
+1.0.0, 1.1.0. Web Map Context 1.1.0 support was added to MapServer 4.10
-This document assumes that you are already familiar with certain aspects of MapServer:
+This document assumes that you are already familiar with certain aspects of
+MapServer:
- MapServer application development and setting up :ref:`mapfiles <mapfile>`.
-- Familiarity with the WMS spec would be an asset. Please see the following section
- for links to associated sources.
+- Familiarity with the WMS spec would be an asset. Please see the following
+ section for links to associated sources.
+
Links to WMS / Map Context Related Information
----------------------------------------------
@@ -53,18 +55,19 @@
Map Context support requires PROJ4, GDAL/OGR and PHP support libraries.
-Build/install the above libraries on your system and then build MapServer with the
-*'--with-wmsclient --with-proj --with-ogr --with-gdal --with-php'* configure options.
-Also make sure that your build uses the *USE_WMS_LYR* and *USE_OGR* flags. For more
-details on MapServer compilation see the appropriate howto: :ref:`Unix <unix>` / :ref:`Windows <win32>`
+Build/install the above libraries on your system and then build MapServer with
+the *'--with-wmsclient --with-proj --with-ogr --with-gdal --with-php'*
+configure options. Also make sure that your build uses the *USE_WMS_LYR* and
+*USE_OGR* flags. For more details on MapServer compilation see the appropriate
+HowTo: :ref:`Unix <unix>` / :ref:`Windows <win32>`
Windows users can use `MS4W`_, which is ready for Map Context use.
Map Context Mapfile
-------------------
-A map context document can ONLY contain WMS layers (e.g. CONNECTIONTYPE WMS).
-Please refer to the :ref:`MapServer WMS Client HowTo <wms_client>` for more
+A map context document can ONLY contain WMS layers (e.g. CONNECTIONTYPE WMS).
+Please refer to the :ref:`MapServer WMS Client HowTo <wms_client>` for more
information on declaring WMS layers.
MapFile Metadata
@@ -154,27 +157,45 @@
- *wms_dataurl_format* : Format of the online resource where data corresponding
to the layer can be found.
-- *wms_dimension* : Current dimension used. (added in MapServer 4.10)
+- *wms_dimension* : Current dimension used.
+
+ .. versionadded:: 4.10
-- *wms_dimensionlist* : List of available dimensions. (added in MapServer 4.10)
+- *wms_dimensionlist* : List of available dimensions.
+
+ .. versionadded:: 4.10
-- *wms_dimension_%s_default* : Default dimension value. (added in MapServer 4.10) MapServer will check for wms_time and wms_timedefault metadata when this is not specified.
- %s = the name of the dimension.
+- *wms_dimension_%s_default* : Default dimension value. MapServer will check
+ for wms_time and wms_timedefault metadata when this is not specified. %s =
+ the name of the dimension.
-- *wms_dimension_%s_multiplevalues* : Multiple dimension values. (added in MapServer 4.10)
- %s = the name of the dimension.
+ .. versionadded:: 4.10
-- *wms_dimension_%s_nearestvalue* : Nearest dimension value. The default value is 0. (added in MapServer 4.10)
- %s = the name of the dimension.
+- *wms_dimension_%s_multiplevalues* : Multiple dimension values. %s = the name
+ of the dimension.
-- *wms_dimension_%s_units* : Units for the dimension values. The default value is ISO8601. (added in MapServer 4.10)
- %s = the name of the dimension.
+ .. versionadded:: 4.10
-- *wms_dimension_%s_unitsymbol* : Symbol for dimension units. The default value is t. (added in MapServer 4.10)
- %s = the name of the dimension.
+- *wms_dimension_%s_nearestvalue* : Nearest dimension value. The default value
+ is 0. %s = the name of the dimension.
-- *wms_dimension_%s_uservalue* : User dimension value. (added in MapServer 4.10) MapServer will check for wms_time and wms_timedefault metadata when this is not specified.
- %s = the name of the dimension.
+ .. versionadded:: 4.10
+
+- *wms_dimension_%s_units* : Units for the dimension values. The default value
+ is ISO8601. %s = the name of the dimension.
+
+ .. versionadded:: 4.10
+
+- *wms_dimension_%s_unitsymbol* : Symbol for dimension units. The default
+ value is t. %s = the name of the dimension.
+
+ .. verisonadded:: 4.10
+
+- *wms_dimension_%s_uservalue* : User dimension value. MapServer will check
+ for wms_time and wms_timedefault metadata when this is not specified. %s =
+ the name of the dimension.
+
+ .. versionadded:: 4.10
- *wms_format* : Current format used.
@@ -188,7 +209,7 @@
- *wms_name* : Name of the WMS layer on the server.
-- *wms_onlineresource* : (**Required**) URL to access the server.
+- *wms_onlineresource* : **Required** URL to access the server.
- *wms_server_version* : The version of the web map server specification.
@@ -209,7 +230,8 @@
- *wms_style_%s_sld* : URL to the SLD document of this style. %s = the name
of the style.
-- *wms_style_%s_sld_body* : SLD_BODY document of this style. %s = the name of the style.
+- *wms_style_%s_sld_body* : SLD_BODY document of this style. %s = the name of
+ the style.
- *wms_style_%s_title* : Title of the layer. %s = the name of the style.
@@ -289,7 +311,7 @@
---------------------------
1. The first thing to do is to save your mapfile using the saveMapContext function
- available from the :ref:`PHP/Mapscript <php>` library (see the `Map Object functions`_). An
+ available from the :ref:`PHP/Mapscript <php>` library. An
example script is shown below:
::
@@ -305,8 +327,7 @@
this you should have a mapfile compatible with the Map Context specification.
3. Now you can load your new Map Context document into an application using the
- *loadMapContext* function from the PHP/Mapscript library (see the
- `Map Object functions`_).
+ *loadMapContext* function from the PHP/Mapscript library.
Sample Map Context Document
---------------------------
@@ -361,25 +382,29 @@
Map Context Support Through CGI
-------------------------------
-MapServer CGI allows you to load a map context through the use of a CONTEXT parameter,
-and you can point this parameter to a locally stored context file or a context file
-accessible through a URL. For more information on MapServer CGI see the
-:ref:`CGI Reference <cgi>`.
+MapServer CGI allows you to load a map context through the use of a CONTEXT
+parameter, and you can point this parameter to a locally stored context file
+or a context file accessible through a URL. For more information on MapServer
+CGI see the :ref:`CGI Reference <cgi>`.
Support for Local Map Context Files
***********************************
-There is a new cgi parameter called *CONTEXT* that is used to specify a local context
-file. The user can then use MapServer to request a map using the following syntax:
+There is a new cgi parameter called *CONTEXT* that is used to specify a local
+context file. The user can then use MapServer to request a map using the
+following syntax:
::
http://localhost/mapserver.cgi?MODE=map&MAP=/path/to/mapfile.map&CONTEXT=
/path/to/contextfile.xml&LAYERS=layer_name1 layers_name2
-Note that all layers created from a context file have their status set to ON. To
-be able to display layers, the user needs to add the LAYERS argument in the URL.
+.. note::
+ All layers created from a context file have their status set to ON. To be
+ able to display layers, the user needs to add the LAYERS argument in the
+ URL.
+
Support for Context Files Accessed Through a URL
************************************************
@@ -420,14 +445,16 @@
Default Mapfile
****************
-To smoothly run a MapServer CGI application with a Map Context, the application
-administrator needs to provide a default mapfile with at least the basic required
-parameters that will be used with the Context file. This default mapfile can contain
-as little information as the imagepath and imageurl or contain a list of layers.
-Information coming from the context (e.g.: layers, width, height, ...) would either
-be appended or will replace values found in the mapfile.
+To smoothly run a MapServer CGI application with a Map Context, the
+application administrator needs to provide a default mapfile with at least the
+basic required parameters that will be used with the Context file. This
+default mapfile can contain as little information as the imagepath and
+imageurl or contain a list of layers. Information coming from the context
+(e.g.: layers, width, height, ...) would either be appended or will replace
+values found in the mapfile.
-Here is an example of a default map file containing the minimum required parameters:
+Here is an example of a default map file containing the minimum required
+parameters:
::
@@ -462,5 +489,3 @@
.. _`MapServer OGC Web Services Workshop`: http://ms-ogc-workshop.maptools.org/
.. _`Open Geospatial Consortium (OGC)`: http://www.opengeospatial.org/
.. _`MS4W`: http://www.maptools.org/ms4w/
-.. _`Map Object functions`: http://mapserver.gis.umn.edu/docs/reference/phpmapscript-class/classes/mapobj/
-.. _`CGI Reference`: http://mapserver.gis.umn.edu/docs/reference/cgiedu/docs/reference/cgi
\ No newline at end of file
Modified: trunk/docs/ogc/mapscript.txt
===================================================================
--- trunk/docs/ogc/mapscript.txt 2008-12-07 20:30:22 UTC (rev 8200)
+++ trunk/docs/ogc/mapscript.txt 2008-12-07 22:08:52 UTC (rev 8201)
@@ -18,10 +18,10 @@
Introduction
=============================================================================
-With the implementation of MapServer :ref:`rfc16` in MapServer 4.9, MapScript now has
-the ability to invoke MapServer's ability to execute OGC Web Service requests
-such as WMS, WCS, and WFS as well as capturing the results of processing the
-requests.
+With the implementation of MapServer :ref:`rfc16` in MapServer 4.9, MapScript
+now has the ability to invoke MapServer's ability to execute OGC Web Service
+requests such as WMS, WCS, and WFS as well as capturing the results of
+processing the requests.
This makes it possible to dynamically configure a map object based on
information in the original request, and to capture the output of processing
@@ -132,7 +132,7 @@
printf "%s\n", mapscript::msIO_getStdoutBufferString();
-One issue in perl is that there is currently no wrapping for binary buffers
+One issue in Perl is that there is currently no wrapping for binary buffers
so you cannot call msIO_getStdoutBufferBytes(), and so cannot manipulate
binary results.
More information about the mapserver-commits
mailing list