[mapserver-commits] r12556 - trunk/docs/en/cgi
svn at osgeo.org
svn at osgeo.org
Mon Sep 19 13:11:32 EDT 2011
Author: hobu
Date: 2011-09-19 10:11:32 -0700 (Mon, 19 Sep 2011)
New Revision: 12556
Modified:
trunk/docs/en/cgi/runsub.txt
Log:
a few cleanups for syntax highlighting
Modified: trunk/docs/en/cgi/runsub.txt
===================================================================
--- trunk/docs/en/cgi/runsub.txt 2011-09-19 17:11:04 UTC (rev 12555)
+++ trunk/docs/en/cgi/runsub.txt 2011-09-19 17:11:32 UTC (rev 12556)
@@ -19,21 +19,20 @@
-----------------------------------------------------------------------------
Run-time substitution for the MapServer CGI has been around since version 4.0
-and it's use has continued to expand. In short, it allows you to alter
-portions of a mapfile based on data passed via a CGI request. This
-functionality is only available via the standard CGI application. Within
-MapScript this is easy to do since the developer has complete control over how
-input is handled.
+and it's use has continued to expand. In short, it allows you to alter portions
+of a mapfile based on data passed via a CGI request. This functionality is only
+available via the standard CGI application. Within MapScript this is easy to do
+since the developer has complete control over how input is handled.
Basic Example
-----------------------------------------------------------------------------
-Let's say you'd like the user to dynamically set a
-portion of an expression so they could highlight a certain land cover class,
-and you have a form element (called ctype) that allows them to choose between:
-forest, water, wetland and developed. You could then set up a layer like so:
+Let's say you'd like the user to dynamically set a portion of an expression so
+they could highlight a certain land cover class, and you have a form element
+(called ctype) that allows them to choose between: forest, water, wetland and
+developed. You could then set up a layer like so:
-::
+.. code-block:: mapfile
LAYER
NAME 'covertypes'
@@ -48,20 +47,20 @@
END
END
-When a request is processed the value for ctype is substituted for the
-string %ctype% and the mapfile is processed as normal. If no ctype is passed
-in the EXPRESSION will never be true so it doesn't really hurt anything except
-for a slight performance hit. Often you would set a default class to draw
-features that don't match, but that is not required.
+When a request is processed the value for ctype is substituted for the string
+%ctype% and the mapfile is processed as normal. If no ctype is passed in the
+EXPRESSION will never be true so it doesn't really hurt anything except for a
+slight performance hit. Often you would set a default class to draw features
+that don't match, but that is not required.
Parameters Supported
-----------------------------------------------------------------------------
-Not every mapfile parameter supports run-time substitution and care has
-been taken to try and support those that make the most sense. Remember, you
-also can do run-time configuration using the map_object_property type syntax
-detailed elsewhere (todo- add link). Below is a list of properties that do
-allow run-time substitution (todo- add MapServer version):
+Not every mapfile parameter supports run-time substitution and care has been
+taken to try and support those that make the most sense. Remember, you also can
+do run-time configuration using the map_object_property type syntax detailed
+elsewhere (todo- add link). Below is a list of properties that do allow
+run-time substitution (todo- add MapServer version):
* LAYER: DATA (must validate against DATAPATTERN)
* LAYER: TILEINDEX
@@ -149,10 +148,10 @@
VALIDATION
# %firstname% substitutions can only have letters and hyphens
- firstname '^[a-zA-Z\-]+$'
+ 'firstname' '^[a-zA-Z\-]+$'
# %parcelid% must be numeric and between 5 and 8 characters
- parcelid '^[0-9]{5,8)$'
+ 'parcelid' '^[0-9]{5,8)$'
# %taxid% must be two capital letters and six digits
taxid '^[A-Z]{2}[0-9]{6}$'
More information about the mapserver-commits
mailing list