[mapserver-commits] r8753 - trunk/docs/tutorial
svn at osgeo.org
svn at osgeo.org
Tue Mar 10 09:17:27 EDT 2009
Author: pnaciona
Date: 2009-03-10 09:17:27 -0400 (Tue, 10 Mar 2009)
New Revision: 8753
Modified:
trunk/docs/tutorial/example1-1.txt
trunk/docs/tutorial/example1-3.txt
trunk/docs/tutorial/example1-4.txt
trunk/docs/tutorial/example1-5-map.txt
trunk/docs/tutorial/example1-5.txt
trunk/docs/tutorial/example1-7.txt
trunk/docs/tutorial/example1-8.txt
Log:
updated formatting for tutorial example files
Modified: trunk/docs/tutorial/example1-1.txt
===================================================================
--- trunk/docs/tutorial/example1-1.txt 2009-03-09 22:01:53 UTC (rev 8752)
+++ trunk/docs/tutorial/example1-1.txt 2009-03-10 13:17:27 UTC (rev 8753)
@@ -38,8 +38,10 @@
|-STYLE
+MAP Object
+**********
+
Let's look at the keywords (parameters) within the MAP object:
-**************************************************************
**MAP**
Every mapfile starts with the :ref:`MAP <map>` object--the entire
@@ -119,8 +121,10 @@
255 Red, 255 Green, and 255 Blue which results in a white background.
Go ahead and play with this values.
+LAYER Object
+************
+
Now let's look at the LAYER object parameters:
-**********************************************
**LAYER**
Marks the beginning of a :ref:`LAYER <layer>` within the MAP object.
@@ -153,8 +157,10 @@
Layers are turned on or off based on their STATUS. DEFAULT is always on.
ON or OFF works when the LAYER name is passed as part of the query string.
+CLASS Object
+************
+
Let's look at the CLASS object parameters:
-******************************************
**CLASS**
Marks the beginning of a :ref:`CLASS <class>` object within the LAYER
@@ -169,8 +175,10 @@
sure to use an appropriate descriptive name when naming classes. We
will talk about legends later in this tutorial.
+STYLE Object
+************
+
And finally, let's look at the STYLE object parameters:
-*******************************************************
**STYLE**
Marks the beginning of the :ref:`STYLE <style>` object. You can
Modified: trunk/docs/tutorial/example1-3.txt
===================================================================
--- trunk/docs/tutorial/example1-3.txt 2009-03-09 22:01:53 UTC (rev 8752)
+++ trunk/docs/tutorial/example1-3.txt 2009-03-10 13:17:27 UTC (rev 8753)
@@ -27,6 +27,9 @@
| | |
STYLE-| |-STYLE |-STYLE
+Keywords
+********
+
Our mapfile still only has two layers but the polygon layer has been broken down
into two classes. Let's have a look at the additional parameters:
Modified: trunk/docs/tutorial/example1-4.txt
===================================================================
--- trunk/docs/tutorial/example1-4.txt 2009-03-09 22:01:53 UTC (rev 8752)
+++ trunk/docs/tutorial/example1-4.txt 2009-03-10 13:17:27 UTC (rev 8753)
@@ -1,106 +1,112 @@
-.. _example1-4:
-
-===========
-Example 1.4
-===========
-Labeling the Map
-----------------
-
-We can also add labels to our map...
-
-.. image:: http://demo.mapserver.org/cgi-bin/mapserv.exe?map=/ms4w/apps/tutorial/htdocs/example1-4.map&layer=states_poly&layer=states_line&mode=map
-
-MapServer has a very flexible labeling engine. It supports native bitmap as
-well as truetype fonts. Font scaling is supported with truetype. The labeling
-angles and placements can be customized... If you take the time to learn the
-many parameters involved in creating good labels, you will be rewarded with
-informative and aesthetically pleasing maps.
-
-This is what the map file looks like: `Example1-4.map <http://biometry.gis.umn.edu/tutorial/example1-4.map>`_.
-
-The map file structure, by objects, looks like this:
-
-::
-
- MAP
- (states_poly) LAYER----------|---------LAYER (states_line)
- (land) CLASS-----|-CLASS (water) |-CLASS
- STYLE-|-LABEL |-STYLE |-STYLE</pre>
-
-Here we introduce a few more parameters along with the LABEL object:
-
-**FONTSET**
- Here we specify the full path to our truetype fonts list (or fontset)
- file. This file lists each of the available fonts. See the file
- itself and the `MapServer font set documentation
- <http://mapserver.gis.umn.edu/doc/fontset.html>`_ for more info.
- FONTSET is a parameter of the MAP object.
-
-**LABELITEM**
- This specifies which data attribute to use for labeling, in this
- case "STATE". LABELITEM is a parameter of the LAYER object.
-
-**LABEL**
- Marks the beginning of the LABEL object. The label object can be used
- under other objects (i.e. the SCALEBAR object).
-
-**COLOR**
- Within the LABEL object, COLOR specifies the color of the label text.
-
-**SHADOWCOLOR**
- This specifies the shadow color of the label text.
-
-**SHADOWSIZE**
- Specifies the shadow size. The value corresponds to the X and the Y
- shifts in pixels. So, "2 2" means two pixels wide by two pixels high.
-
-**TYPE**
- Within the LABEL object, TYPE specifies what type of font to use. We
- have the choice of TRUETYPE or BITMAP (the built-in fonts). We choose
- TRUETYPE.
-
-**FONT**
- If you specify TYPE as TRUETYPE, you need to specify what font to use.
- The value here is the "alias" in the font list file.
-
-**SIZE**
- If using truetype fonts, the value is size in pixels. If bitmap, you
- can say something like "small" or "large".
-
-**ANTIALIAS**
- This turns truetype antialiasing on or off. Remember the value isn't
- on or off but TRUE or FALSE.
-
-**POSITION**
- Where to position the label text in relation to the label points.
- The value is a combination of vertical and horizontal positions. You
- have the following choices for vertical alignment: C for center, U
- for upper, and L for lower. For horizontal alignment you have the
- following choices: C for center, L for left, and R for right. So, to
- align the label text to the center of label ID you'd use the value
- "CC" (center-center). Or if you'd like it to be on the
- lower left of the ID, you'd use LL. Another way is to let MapServer
- decide the best position for your labels. For this you would use
- the value "AUTO".
-
-**PARTIALS**
- Tells MapServer whether to generate incomplete label texts or not.
- The default here is not to generate fragments of a label text. The
- value is either TRUE or FALSE.
-
-**MINDISTANCE**
- This is the minimum distance in pixels between duplicate labels. See
- what happens if you increase or decrease this value.
-
-**BUFFER**
- The padding (in pixels) for each label. This is used to enhance
- readability. A BUFFER of 4 pixels mean that no label will be drawn
- within four pixels of each other. Again, change to see how it works.
-
- You can also create labels separate from a POLYGON layer. You do
- this with the ANNOTATION data type. Have a look at the next example's
- map file to see how you'd implement this kind of labeling. You will
- notice that the CLASS object within the "label" layer has a COLOR
- parameter value of "-1 -1 -1". The negative number tells MapServer to
- give this CLASS a transparent color (the label IDs don't show up).
- Once again, play with the values to understand how it affects the map.
+.. _example1-4:
+
+===========
+Example 1.4
+===========
+Labeling the Map
+----------------
+
+We can also add labels to our map...
+
+.. image:: http://demo.mapserver.org/cgi-bin/mapserv.exe?map=/ms4w/apps/tutorial/htdocs/example1-4.map&layer=states_poly&layer=states_line&mode=map
+
+MapServer has a very flexible labeling engine. It supports native bitmap as
+well as truetype fonts. Font scaling is supported with truetype. The labeling
+angles and placements can be customized... If you take the time to learn the
+many parameters involved in creating good labels, you will be rewarded with
+informative and aesthetically pleasing maps.
+
+This is what the map file looks like: `Example1-4.map <http://biometry.gis.umn.edu/tutorial/example1-4.map>`_.
+
+MapFile Structure
+#################
+
+The map file structure, by objects, looks like this:
+
+::
+
+ MAP
+ (states_poly) LAYER----------|---------LAYER (states_line)
+ (land) CLASS-----|-CLASS (water) |-CLASS
+ STYLE-|-LABEL |-STYLE |-STYLE</pre>
+
+The LABEL Object and Keywords
+*****************************
+
+Here we introduce a few more parameters along with the LABEL object:
+
+**FONTSET**
+ Here we specify the full path to our truetype fonts list (or fontset)
+ file. This file lists each of the available fonts. See the file
+ itself and the `MapServer font set documentation
+ <http://mapserver.gis.umn.edu/doc/fontset.html>`_ for more info.
+ FONTSET is a parameter of the MAP object.
+
+**LABELITEM**
+ This specifies which data attribute to use for labeling, in this
+ case "STATE". LABELITEM is a parameter of the LAYER object.
+
+**LABEL**
+ Marks the beginning of the LABEL object. The label object can be used
+ under other objects (i.e. the SCALEBAR object).
+
+**COLOR**
+ Within the LABEL object, COLOR specifies the color of the label text.
+
+**SHADOWCOLOR**
+ This specifies the shadow color of the label text.
+
+**SHADOWSIZE**
+ Specifies the shadow size. The value corresponds to the X and the Y
+ shifts in pixels. So, "2 2" means two pixels wide by two pixels high.
+
+**TYPE**
+ Within the LABEL object, TYPE specifies what type of font to use. We
+ have the choice of TRUETYPE or BITMAP (the built-in fonts). We choose
+ TRUETYPE.
+
+**FONT**
+ If you specify TYPE as TRUETYPE, you need to specify what font to use.
+ The value here is the "alias" in the font list file.
+
+**SIZE**
+ If using truetype fonts, the value is size in pixels. If bitmap, you
+ can say something like "small" or "large".
+
+**ANTIALIAS**
+ This turns truetype antialiasing on or off. Remember the value isn't
+ on or off but TRUE or FALSE.
+
+**POSITION**
+ Where to position the label text in relation to the label points.
+ The value is a combination of vertical and horizontal positions. You
+ have the following choices for vertical alignment: C for center, U
+ for upper, and L for lower. For horizontal alignment you have the
+ following choices: C for center, L for left, and R for right. So, to
+ align the label text to the center of label ID you'd use the value
+ "CC" (center-center). Or if you'd like it to be on the
+ lower left of the ID, you'd use LL. Another way is to let MapServer
+ decide the best position for your labels. For this you would use
+ the value "AUTO".
+
+**PARTIALS**
+ Tells MapServer whether to generate incomplete label texts or not.
+ The default here is not to generate fragments of a label text. The
+ value is either TRUE or FALSE.
+
+**MINDISTANCE**
+ This is the minimum distance in pixels between duplicate labels. See
+ what happens if you increase or decrease this value.
+
+**BUFFER**
+ The padding (in pixels) for each label. This is used to enhance
+ readability. A BUFFER of 4 pixels mean that no label will be drawn
+ within four pixels of each other. Again, change to see how it works.
+
+ You can also create labels separate from a POLYGON layer. You do
+ this with the ANNOTATION data type. Have a look at the next example's
+ map file to see how you'd implement this kind of labeling. You will
+ notice that the CLASS object within the "label" layer has a COLOR
+ parameter value of "-1 -1 -1". The negative number tells MapServer to
+ give this CLASS a transparent color (the label IDs don't show up).
+ Once again, play with the values to understand how it affects the map.
Modified: trunk/docs/tutorial/example1-5-map.txt
===================================================================
--- trunk/docs/tutorial/example1-5-map.txt 2009-03-09 22:01:53 UTC (rev 8752)
+++ trunk/docs/tutorial/example1-5-map.txt 2009-03-10 13:17:27 UTC (rev 8753)
@@ -42,7 +42,7 @@
# CLASSITEM defines the non-spatial attribute that you will be using to
# separate a layer into classes. This attribute will be in the DBF file
# of your shapefile (it will be different for each data format). In this
- # example the shapefile states_ugl has an associated database
+ # example the shapefile states_ugl has an associated database
# (states_ugl.dbf) that contains an attribute called "CLASS". You will be
# using two values in the CLASS attribute to separate the classes (also
# called themes) used in this layer--land and water. CLASSITEM is used in
@@ -160,4 +160,4 @@
END # States label layer ends here
# End of LAYER DEFINITIONS -------------------------------
- END # All map files must come to an end just as all other things must come to...
\ No newline at end of file
+ END # All map files must come to an end just as all other things must come to...
\ No newline at end of file
Modified: trunk/docs/tutorial/example1-5.txt
===================================================================
--- trunk/docs/tutorial/example1-5.txt 2009-03-09 22:01:53 UTC (rev 8752)
+++ trunk/docs/tutorial/example1-5.txt 2009-03-10 13:17:27 UTC (rev 8753)
@@ -1,140 +1,140 @@
-.. _example1-5:
-
-===========
-Example 1.5
-===========
-Adding a Raster Layer
----------------------
-
-.. image:: http://demo.mapserver.org/cgi-bin/mapserv.exe?map=/ms4w/apps/tutorial/htdocs/example1-5.map&layer=states&layer=states_line&layer=states_label&layer=modis&mode=map
-
-In addition to vector data support (point, lines, polygons, and annotations),
-MapServer can also display raster data. Through the use of GDAL library, MapServer
-can input and output multiple raster formats. Whereas in versions prior to 4.x raster
-input is limited to single layer, grayscale or indexed color images, recent MapServer
-versions support RGB and multispectral (multi-layer) images. This example shows how to
-select what layers to display when using multispectral data.
-
-.. note::
-
- There might be a noticeable performance hit when using RGB and multispectral images.
-
-Because MapServer 5.x uses GD version 2.0.x library to generate output images, it
-supports RGB (24-bit or true color) output as well. So, along with 8-bit (indexed
-color or grayscale) PNG, you can now also use PNG24 (true color) for output. This
-example uses PNG24 as IMAGETYPE.
-
-.. note::
-
- As with RGB input, there might be a noticeable performance hit when using PNG24.
-
-MapServer can actually use GDAL to generate output images as well, but that's another
-topic. If you want to know more about it, look at the :ref:`OUTPUTFORMAT <outputformat>`
-object in the mapfile reference.
-
-MapFile
--------
-
-This is what the mapfile looks like: :ref:`Example1-5.map <example1-5-map>`
-
-The mapfile structure, by objects, looks like this:
-
-::
-
- MAP
- LAYER #1-------------LAYER #2----|----LAYER #3--------LAYER #4
- (states_poly) (modis) (states_line) (states_label)
- | | |
- (land) CLASS-|-CLASS (water) |-CLASS |-CLASS
- | | | |
- STYLE-| |-STYLE |-STYLE STYLE-|-LABEL
-
-
-When you look at the mapfile, you'll see that the new LAYER object is added below
-(after) the state POLYGON layer. Why? MapServer displays layers in reverse order:
-last in, first out (LIFO). The first layer defined in the mapfile is drawn at
-the bottom of the map.
-
-So, if we have drawn the state POLYGON layer, it would be on the bottom. Since the
-raster layer gets drawn on top of it, we won't see it. That's why the first layer
-gets the STATUS value of OFF. The state LINE layer is defined below the raster
-layer so it gets drawn on top (and you can see it). This is why we separated the
-state LINE layer from the state POLYGON layer. Of course the labels get drawn
-on top of everything.
-
-MapServer can automatically turn layers on or off based on the status of other
-layers (say you want the states polygon layer turned off when the raster layer
-is turned on). This is done by using the REQUIRES parameter. Keep this in
-mind as you might want to use it once you start creating your own MapServer
-applications.
-
-Parameters
-##########
-
-Let's have a look at the new parameters introduced in the mapfile:
-
-**IMAGETYPE**
- This is not new but the value "PNG24" is. PNG24 is the 24-bit or true-color
- version of the PNG format. Instead of being limited to 256 color combinations
- for our output image, MapServer now have millions. By the way, try changing
- this value back to PNG. Notice the time it takes to generate the image using
- either formats. In choosing between true color and indexed color, take into
- account the time it takes to generate the image.
-
-**SYMBOLSET**
- Points to the path of the symbol definition file. The symbols in this file
- are referenced by the SYMBOL parameter in the :ref:`CLASS <class>` object.
- It's not really needed at this point but I thought I'd throw this here now.
- Please refer to the :ref:`Cartographic Symbol Reference <sym_construction>`
- for further information.
-
-**DATA raster/mod09a12003161_ugl_ll_8bit.tif**
-
- In the newly added LAYER object, the DATA parameter points to a GeoTIFF image.
- Like vector datasets, MapServer supports multiple raster file formats. This
- support is accomplished through use of the GDAL library. For more information
- on the different raster formats supported by MapServer and for general
- discussion on the use of rasters in MapServer, please read the
- :ref:`Raster Data Reference <raster>`.
-
-**TYPE RASTER**
- When using raster data (images) we use the value RASTER for the parameter
- TYPE, as opposed to the POLYGON, LINE, and POINT values for vector data and
- ANNOTATION for label IDs.
-
-**PROCESSING "BANDS=1,2,3"**
- This LAYER object parameter was added in MapServer 4.x. The
- :ref:<PROCESSING> keyword has many values but in this case we are using it to
- select which bands in a multispectral image to display. The values here are
- strings that will be passed to the GDAL library.
-
-**OFFSITE**
- This parameter tells MapServer what pixel values to render as background
- (or ignore). You can get the pixel values using image processing or image
- manipulation programs (i.e. Imagine, Photoshop, Gimp).
-
-RGB vs Indexed Color Image
-##########################
-
-To compare map creation speed when using RGB image as opposed to indexed color
-image, replace the following lines in the mapfile:
-
-.. code-block:: mapfile
-
- DATA "raster/mod09a12003161_ugl_ll_8bit.tif"
- STATUS DEFAULT
- TYPE RASTER
- PROCESSING "BANDS=1,2,3"
- OFFSITE 71 74 65
-
-with these:
-
-.. code-block:: mapfile
-
-
- DATA "raster/mod09a12003161_ugl_ll_idxa.tif"
- STATUS DEFAULT
- TYPE RASTER
- OFFSITE 70 74 66
-
+.. _example1-5:
+
+===========
+Example 1.5
+===========
+Adding a Raster Layer
+---------------------
+
+.. image:: http://demo.mapserver.org/cgi-bin/mapserv.exe?map=/ms4w/apps/tutorial/htdocs/example1-5.map&layer=states&layer=states_line&layer=states_label&layer=modis&mode=map
+
+In addition to vector data support (point, lines, polygons, and annotations),
+MapServer can also display raster data. Through the use of GDAL library, MapServer
+can input and output multiple raster formats. Whereas in versions prior to 4.x raster
+input is limited to single layer, grayscale or indexed color images, recent MapServer
+versions support RGB and multispectral (multi-layer) images. This example shows how to
+select what layers to display when using multispectral data.
+
+.. note::
+
+ There might be a noticeable performance hit when using RGB and multispectral images.
+
+Because MapServer 5.x uses GD version 2.0.x library to generate output images, it
+supports RGB (24-bit or true color) output as well. So, along with 8-bit (indexed
+color or grayscale) PNG, you can now also use PNG24 (true color) for output. This
+example uses PNG24 as IMAGETYPE.
+
+.. note::
+
+ As with RGB input, there might be a noticeable performance hit when using PNG24.
+
+MapServer can actually use GDAL to generate output images as well, but that's another
+topic. If you want to know more about it, look at the :ref:`OUTPUTFORMAT <outputformat>`
+object in the mapfile reference.
+
+MapFile Structure
+#################
+
+This is what the mapfile looks like: :ref:`Example1-5.map <example1-5-map>`
+
+The mapfile structure, by objects, looks like this:
+
+::
+
+ MAP
+ LAYER #1-------------LAYER #2----|----LAYER #3--------LAYER #4
+ (states_poly) (modis) (states_line) (states_label)
+ | | |
+ (land) CLASS-|-CLASS (water) |-CLASS |-CLASS
+ | | | |
+ STYLE-| |-STYLE |-STYLE STYLE-|-LABEL
+
+
+When you look at the mapfile, you'll see that the new LAYER object is added below
+(after) the state POLYGON layer. Why? MapServer displays layers in reverse order:
+last in, first out (LIFO). The first layer defined in the mapfile is drawn at
+the bottom of the map.
+
+So, if we have drawn the state POLYGON layer, it would be on the bottom. Since the
+raster layer gets drawn on top of it, we won't see it. That's why the first layer
+gets the STATUS value of OFF. The state LINE layer is defined below the raster
+layer so it gets drawn on top (and you can see it). This is why we separated the
+state LINE layer from the state POLYGON layer. Of course the labels get drawn
+on top of everything.
+
+MapServer can automatically turn layers on or off based on the status of other
+layers (say you want the states polygon layer turned off when the raster layer
+is turned on). This is done by using the REQUIRES parameter. Keep this in
+mind as you might want to use it once you start creating your own MapServer
+applications.
+
+Parameters
+##########
+
+Let's have a look at the new parameters introduced in the mapfile:
+
+**IMAGETYPE**
+ This is not new but the value "PNG24" is. PNG24 is the 24-bit or true-color
+ version of the PNG format. Instead of being limited to 256 color combinations
+ for our output image, MapServer now have millions. By the way, try changing
+ this value back to PNG. Notice the time it takes to generate the image using
+ either formats. In choosing between true color and indexed color, take into
+ account the time it takes to generate the image.
+
+**SYMBOLSET**
+ Points to the path of the symbol definition file. The symbols in this file
+ are referenced by the SYMBOL parameter in the :ref:`CLASS <class>` object.
+ It's not really needed at this point but I thought I'd throw this here now.
+ Please refer to the :ref:`Cartographic Symbol Reference <sym_construction>`
+ for further information.
+
+**DATA raster/mod09a12003161_ugl_ll_8bit.tif**
+
+ In the newly added LAYER object, the DATA parameter points to a GeoTIFF image.
+ Like vector datasets, MapServer supports multiple raster file formats. This
+ support is accomplished through use of the GDAL library. For more information
+ on the different raster formats supported by MapServer and for general
+ discussion on the use of rasters in MapServer, please read the
+ :ref:`Raster Data Reference <raster>`.
+
+**TYPE RASTER**
+ When using raster data (images) we use the value RASTER for the parameter
+ TYPE, as opposed to the POLYGON, LINE, and POINT values for vector data and
+ ANNOTATION for label IDs.
+
+**PROCESSING "BANDS=1,2,3"**
+ This LAYER object parameter was added in MapServer 4.x. The
+ :ref:<PROCESSING> keyword has many values but in this case we are using it to
+ select which bands in a multispectral image to display. The values here are
+ strings that will be passed to the GDAL library.
+
+**OFFSITE**
+ This parameter tells MapServer what pixel values to render as background
+ (or ignore). You can get the pixel values using image processing or image
+ manipulation programs (i.e. Imagine, Photoshop, Gimp).
+
+RGB vs Indexed Color Image
+##########################
+
+To compare map creation speed when using RGB image as opposed to indexed color
+image, replace the following lines in the mapfile:
+
+.. code-block:: mapfile
+
+ DATA "raster/mod09a12003161_ugl_ll_8bit.tif"
+ STATUS DEFAULT
+ TYPE RASTER
+ PROCESSING "BANDS=1,2,3"
+ OFFSITE 71 74 65
+
+with these:
+
+.. code-block:: mapfile
+
+
+ DATA "raster/mod09a12003161_ugl_ll_idxa.tif"
+ STATUS DEFAULT
+ TYPE RASTER
+ OFFSITE 70 74 66
+
Also, try changing the IMAGETYPE from PNG24 to PNG.
\ No newline at end of file
Modified: trunk/docs/tutorial/example1-7.txt
===================================================================
--- trunk/docs/tutorial/example1-7.txt 2009-03-09 22:01:53 UTC (rev 8752)
+++ trunk/docs/tutorial/example1-7.txt 2009-03-10 13:17:27 UTC (rev 8753)
@@ -8,30 +8,36 @@
.. image:: http://demo.mapserver.org/cgi-bin/mapserv.exe?map=/ms4w/apps/tutorial/htdocs/example1-7.map&layers=states+states_label+modis_jpl&mode=map
-Another exciting feature of MapServer is its ability to use layers from other
+Another exciting feature of MapServer is its ability to use layers from other
map servers. In this case, a MapServer application becomes a WMS (or WFS)
client. MapServer can also share (or serve up) the layers in the mapfile to
other map servers. This makes an application a WMS (or WFS) server. What is WMS
or WFS? These are "web-based interoperability service" specifications published
-by the Open Geospatial Consortium (OGC). WMS stands for Web Map Service and WFS
-for Web Feature Service. The difference between these two specifications, in
-simple terms, is that WMS uses web raster formats (PNG, GIF, JPEG) to share
-layers while WFS uses GML, the Geography Markup Language. A third OGC
-interoperability specification is the Web Coverage Services specification or
-WCS--MapServer supports this at the server level only. To find more information
-about WMS, WFS, and WCS go the the `OGC's web site
+by the Open Geospatial Consortium (OGC). WMS stands for Web Map Service and WFS
+for Web Feature Service. The difference between these two specifications, in
+simple terms, is that WMS uses web raster formats (PNG, GIF, JPEG) to share
+layers while WFS uses GML, the Geography Markup Language. A third OGC
+interoperability specification is the Web Coverage Services specification or
+WCS--MapServer supports this at the server level only. To find more information
+about WMS, WFS, and WCS go the the `OGC's web site
<http://www.opengeospatial.org>`_ and look for the `OGC Implementation
-Specifications <http://www.opengeospatial.org/specs/?page=specs>`_ or `OGC
-Abstract Specifications <http://www.opengeospatial.org/specs/?page=abstract>`_.
-The MapServer web site also has `documentation
-<http://mapserver.gis.umn.edu/doc.html>`_ and `WIKI pages
+Specifications <http://www.opengeospatial.org/specs/?page=specs>`_ or `OGC
+Abstract Specifications <http://www.opengeospatial.org/specs/?page=abstract>`_.
+The MapServer web site also has `documentation
+<http://mapserver.gis.umn.edu/doc.html>`_ and `WIKI pages
<http://mapserver.gis.umn.edu/cgi-bin/wiki.pl>`_ for these specifications.
This example shows you how to add a WMS layer in your mapfile.
-This is what the mapfile looks like: `Example1-7.map
+The MapFile
+###########
+
+This is what the mapfile looks like: `Example1-7.map
<http://biometry.gis.umn.edu/tutorial/example1-7.map>`_.
+LAYER Object and WMS Parameters
+*******************************
+
Let's have a look at the WMS layer:
**LAYER # MODIS WMS map from JPL**
@@ -89,9 +95,12 @@
**END**
marks the end of the METADATA object
-To know more about adding WMS layers to your applications, please visit the `WMS
+To know more about adding WMS layers to your applications, please visit the `WMS
Client HOW-TO document <http://mapserver.gis.umn.edu/doc/wms-client-howto.html>`_.
+WEB Object Parameters
+*********************
+
In addition to adding the WMS layer object, there's also a new object under MAP. This is the WEB object. Within the WEB object are two parameters:
**IMAGEPATH '/data/tmp/'**
@@ -106,13 +115,13 @@
This is how IMAGEPATH will appear relative to the web server's root
directory. If we have to type the full URL for this, it will be
"http://terrasip.gis.umn.edu/tmp/". Make sure that the
- path includes a slash (/) at the end.
-
+ path includes a slash (/) at the end.
+
Finally, within the MAP object, I added a new parameter: NAME. This
is the identifier for the MAP object. MapServer uses this as prefix
to all images it creates and dumps to the "tmp" directory.
It's not needed at this point but it also doesn't hurt to have it.
-
+
If you would like to share your data layers to other map servers,
you will need to add METADATA objects within your MAP object and
within each of the LAYER objects you would like to share. All the
@@ -120,8 +129,8 @@
cascaded and will also become available to others. To know more
about how to make your MapServer application become a WMS server,
please read the `WMS Server HOW-TO documentation
- <http://mapserver.gis.umn.edu/doc/wms-server-howto.html>`_.
- Documentations also exist for configuring MapServer application to
- support the WFS standard, both as a `server
+ <http://mapserver.gis.umn.edu/doc/wms-server-howto.html>`_.
+ Documentations also exist for configuring MapServer application to
+ support the WFS standard, both as a `server
<http://mapserver.gis.umn.edu/doc/wfs-server-howto.html>`_ and as a
`client <http://mapserver.gis.umn.edu/doc/wfs-client-howto.html>`_.
\ No newline at end of file
Modified: trunk/docs/tutorial/example1-8.txt
===================================================================
--- trunk/docs/tutorial/example1-8.txt 2009-03-09 22:01:53 UTC (rev 8752)
+++ trunk/docs/tutorial/example1-8.txt 2009-03-10 13:17:27 UTC (rev 8753)
@@ -12,8 +12,13 @@
If the link fails to display on your browser, right click on the graphic above
and save the link as whatever format you specified on your mapfile.
+The MapFile
+###########
+
Here's the mapfile: `Example1-8.map <http://biometry.gis.umn.edu/tutorial/example1-8.map>`_.
+OUTPUTFORMAT Object
+*******************
Our mapfile now contains a new object, OUTPUTFORMAT. This object is defined
within the MAP object and is used in conjunction with the IMAGETYPE keyword.
Depending on the libraries you compiled with MapServer, you can have several
More information about the mapserver-commits
mailing list