[mapserver-commits] r12613 - branches/branch-6-0/docs/en/mapfile trunk/docs/en/mapfile

[svn at osgeo.org]

Author: havatv
Date: 2011-10-03 08:59:22 -0700 (Mon, 03 Oct 2011)
New Revision: 12613

Modified:
   branches/branch-6-0/docs/en/mapfile/projection.txt
   trunk/docs/en/mapfile/projection.txt
Log:
Fixed some spelling mistakes and formatting issues for the projection document.

Modified: branches/branch-6-0/docs/en/mapfile/projection.txt
===================================================================
--- branches/branch-6-0/docs/en/mapfile/projection.txt	2011-10-03 06:55:53 UTC (rev 12612)
+++ branches/branch-6-0/docs/en/mapfile/projection.txt	2011-10-03 15:59:22 UTC (rev 12613)
@@ -13,7 +13,7 @@
 .. index::
    single: Map projections
 
-There are thousands for geographical reference systems.  In order to
+There are thousands of geographical reference systems.  In order to
 combine datasets with different geographical reference systems into a
 map, the datasets will have to be transformed (projected) to the
 chosen geographical reference system of the map.  If you want to know
@@ -21,13 +21,13 @@
 could take some Geomatics courses (Geographical Information Systems,
 Cartography, Geodesy, ...).
 
-To set up projections you must define one projection objects for the
+To set up projections you must define one projection object for the
 output image (in the :ref:`MAP` object) and one projection object for
-each layer (in the :ref:`LAYER` objects) to be projected. MapServer
-relies on the :term:`Proj.4` library for projections. Projection
+each layer (in the :ref:`LAYER` objects) to be projected.  MapServer
+relies on the :term:`Proj.4` library for projections.  Projection
 objects therefore consist of a series of PROJ.4 keywords, which are
 either specified within the object directly or referred to in an
-:term:`EPSG` file. An EPSG file is a lookup file containing projection
+:term:`EPSG` file.  An EPSG file is a lookup file containing projection
 parameters, and is part of the PROJ.4 library.
 
 The following two examples both define the same projection (UTM zone 15,
@@ -63,8 +63,8 @@
 .. note::
 
     This refers to an EPSG lookup file that contains a '26915' code with the
-    full projection parameters. "epsg" in this instance is case-sensitive
-    because it is referring to a file name. If your file system is
+    full projection parameters.  "epsg" in this instance is case-sensitive
+    because it is referring to a file name.  If your file system is
     case-sensitive, this must be lower case, or MapServer (Proj.4 actually)
     will complain about not being able to find this file.
 
@@ -74,7 +74,7 @@
     this coordinate system.
 
 The next two examples both display how to possibly define unprojected 
-lat/longs ("geographic"):
+lat/long ("geographic"):
 
 **Example 3: Inline Projection Parameters**
 
@@ -98,18 +98,18 @@
 ---------------
 
 - If all of your data in the mapfile is in the same projection, you DO NOT
-  have to specify any projection objects. MapServer will assume that all of
+  have to specify any projection objects.  MapServer will assume that all of
   the data is in the same projection.
 
 - Think of the :ref:`MAP`-level projection object as your output projection.
-  The EXTENT and UNITS values at the MAP-level must be in the output
-  projection units. Also, if you have layers in other projections (other than
-  the MAP-level projection) then you must define :ref:`PROJECTION` objects for
+  The `EXTENT` and `UNITS` values at the `MAP`-level must be in the output
+  projection units.  Also, if you have layers in other projections (other than
+  the `MAP`-level projection) then you must define `PROJECTION` objects for
   those layers, to tell MapServer what projections they are in.
 
-- If you specify a MAP-level projection, and then only one other LAYER
+- If you specify a `MAP`-level projection, and then only one other `LAYER`
   projection object, MapServer will assume that all of the other layers are in
-  the specified MAP-level projection.
+  the specified `MAP`-level projection.
 
 - Always refer to the EPSG file in lowercase, because it is a lowercase
   filename and on Linux/Unix systems this parameter is case sensitive.

Modified: trunk/docs/en/mapfile/projection.txt
===================================================================
--- trunk/docs/en/mapfile/projection.txt	2011-10-03 06:55:53 UTC (rev 12612)
+++ trunk/docs/en/mapfile/projection.txt	2011-10-03 15:59:22 UTC (rev 12613)
@@ -13,7 +13,7 @@
 .. index::
    single: Map projections
 
-There are thousands for geographical reference systems.  In order to
+There are thousands of geographical reference systems.  In order to
 combine datasets with different geographical reference systems into a
 map, the datasets will have to be transformed (projected) to the
 chosen geographical reference system of the map.  If you want to know
@@ -21,13 +21,13 @@
 could take some Geomatics courses (Geographical Information Systems,
 Cartography, Geodesy, ...).
 
-To set up projections you must define one projection objects for the
+To set up projections you must define one projection object for the
 output image (in the :ref:`MAP` object) and one projection object for
-each layer (in the :ref:`LAYER` objects) to be projected. MapServer
-relies on the :term:`Proj.4` library for projections. Projection
+each layer (in the :ref:`LAYER` objects) to be projected.  MapServer
+relies on the :term:`Proj.4` library for projections.  Projection
 objects therefore consist of a series of PROJ.4 keywords, which are
 either specified within the object directly or referred to in an
-:term:`EPSG` file. An EPSG file is a lookup file containing projection
+:term:`EPSG` file.  An EPSG file is a lookup file containing projection
 parameters, and is part of the PROJ.4 library.
 
 The following two examples both define the same projection (UTM zone 15,
@@ -63,8 +63,8 @@
 .. note::
 
     This refers to an EPSG lookup file that contains a '26915' code with the
-    full projection parameters. "epsg" in this instance is case-sensitive
-    because it is referring to a file name. If your file system is
+    full projection parameters.  "epsg" in this instance is case-sensitive
+    because it is referring to a file name.  If your file system is
     case-sensitive, this must be lower case, or MapServer (Proj.4 actually)
     will complain about not being able to find this file.
 
@@ -74,7 +74,7 @@
     this coordinate system.
 
 The next two examples both display how to possibly define unprojected 
-lat/longs ("geographic"):
+lat/long ("geographic"):
 
 **Example 3: Inline Projection Parameters**
 
@@ -98,18 +98,18 @@
 ---------------
 
 - If all of your data in the mapfile is in the same projection, you DO NOT
-  have to specify any projection objects. MapServer will assume that all of
+  have to specify any projection objects.  MapServer will assume that all of
   the data is in the same projection.
 
 - Think of the :ref:`MAP`-level projection object as your output projection.
-  The EXTENT and UNITS values at the MAP-level must be in the output
-  projection units. Also, if you have layers in other projections (other than
-  the MAP-level projection) then you must define :ref:`PROJECTION` objects for
+  The `EXTENT` and `UNITS` values at the `MAP`-level must be in the output
+  projection units.  Also, if you have layers in other projections (other than
+  the `MAP`-level projection) then you must define `PROJECTION` objects for
   those layers, to tell MapServer what projections they are in.
 
-- If you specify a MAP-level projection, and then only one other LAYER
+- If you specify a `MAP`-level projection, and then only one other `LAYER`
   projection object, MapServer will assume that all of the other layers are in
-  the specified MAP-level projection.
+  the specified `MAP`-level projection.
 
 - Always refer to the EPSG file in lowercase, because it is a lowercase
   filename and on Linux/Unix systems this parameter is case sensitive.