[mapserver-commits] r8695 - trunk/docs/tutorial

[svn at osgeo.org]

Author: pnaciona
Date: 2009-03-09 10:13:46 -0400 (Mon, 09 Mar 2009)
New Revision: 8695

Modified:
   trunk/docs/tutorial/example1-1.txt
Log:
update tutorial example 1.1

Modified: trunk/docs/tutorial/example1-1.txt
===================================================================
--- trunk/docs/tutorial/example1-1.txt	2009-03-09 14:00:23 UTC (rev 8694)
+++ trunk/docs/tutorial/example1-1.txt	2009-03-09 14:13:46 UTC (rev 8695)
@@ -19,7 +19,7 @@
 
 The next three parts are what make up the query string.  The query string contains the CGI parameters (variables and their values), with each parameter separated by an ampersand (&). So, looking at the query string, the first parameter "map" has a value "/ms4w/apps/tutorial/htdocs/example1-1.map"--this tells the MapServer CGI program (mapserv or mapserv.exe) what mapfile to process/parse. The next parameter "layer=states", tells mapserv.exe to "turn on" the states layer--recall that we named our layer object "states".  The last parameter, "mode=map", tells mapserv.exe what to do with the output from the mapfile. In this case it tells mapserv.exe to dump the image directly to the web browser (the client), without first creating a temporary image on the server. The MapServer "mode" CGI variable takes values other than "map". For example if you use "mode=browse", MapServer will dump the image to a temporary directory on the server. The browse mode will not work now but we'll come back to it again later.
 
-This is what the mapfile looks like: `<http://biometry.gis.umn.edu/tutorial/example1-1.map>`_.
+This is what the mapfile looks like: `Example1-1.map <http://biometry.gis.umn.edu/tutorial/example1-1.map>`_.
 
 The `mapfile <http://mapserver.gis.umn.edu/doc/mapfile-reference.html>`_ is MapServer's basic configuration mechanism. It is made up of "objects" and each object can have keywords or other objects. It has a hierarchical structure such that some objects fall under other objects... on top of this hierarchy is the MAP object, all other objects belong to it. This example shows a very straightforward heirarchy of objects.  As you go through each example, the complexity of these hierarchical trees will increase.