[mapserver-commits] r8069 - in trunk/docs: . references
references/mapfile
svn at osgeo.org
svn at osgeo.org
Sun Nov 23 19:35:16 EST 2008
Author: hobu
Date: 2008-11-23 19:35:16 -0500 (Sun, 23 Nov 2008)
New Revision: 8069
Added:
trunk/docs/references/mapfile/index.txt
Removed:
trunk/docs/references/mapfile/introduction.txt
Modified:
trunk/docs/index.txt
trunk/docs/references/index.txt
Log:
org
Modified: trunk/docs/index.txt
===================================================================
--- trunk/docs/index.txt 2008-11-24 00:24:41 UTC (rev 8068)
+++ trunk/docs/index.txt 2008-11-24 00:35:16 UTC (rev 8069)
@@ -10,7 +10,7 @@
.. toctree::
:maxdepth: 2
- references
+ references/index
Indices and tables
==================
Modified: trunk/docs/references/index.txt
===================================================================
--- trunk/docs/references/index.txt 2008-11-24 00:24:41 UTC (rev 8068)
+++ trunk/docs/references/index.txt 2008-11-24 00:35:16 UTC (rev 8069)
@@ -1,11 +1,10 @@
-.. _reference:
+.. _references:
*****************************************************************************
MapServer Reference
*****************************************************************************
-:Release: |version|
-:Date: |today|
+Some text describing
see also :ref:`mapscript`.
@@ -14,6 +13,6 @@
.. toctree::
:maxdepth: 2
- mapfile
- mapscript
+ mapfile/index
+ mapscript/index
Copied: trunk/docs/references/mapfile/index.txt (from rev 8068, trunk/docs/references/mapfile/introduction.txt)
===================================================================
--- trunk/docs/references/mapfile/index.txt (rev 0)
+++ trunk/docs/references/mapfile/index.txt 2008-11-24 00:35:16 UTC (rev 8069)
@@ -0,0 +1,71 @@
+.. _mapfile:
+
+*****************************************************************************
+ Mapfile Reference
+*****************************************************************************
+
+:Release: |version|
+:Date: |today|
+
+
+see also MapScript :ref:`mapscript`.
+
+
+.. toctree::
+ :maxdepth: 2
+
+ class
+ feature
+ expressions
+ fontset
+ grid
+ Include
+
+
+
+
+The Mapfile is the heart of MapServer. It defines the relationships between
+objects, points MapServer to where data are located and defines how things are
+to be drawn.
+
+There are some important concepts that you must understand before you can
+reliably use mapfiles to configure MapServer. First is the concept of a
+`layer <../../../../docs/glossary/layer>`__. A layer is the combination of
+data plus styling. Data, in the form of attributes plus geometry, are given
+styling using CLASS and STYLE directives.
+
+-----------------------------------------------------------------------------
+ Notes
+-----------------------------------------------------------------------------
+* The Mapfile is NOT case-sensitive.
+* Strings containing non-alphanumeric characters or a MapServer keyword MUST
+ be quoted. It is recommended to put ALL strings in double-quotes.
+* For MapServer versions < 5, there was a default maximum of 200 layers per
+ mapfile (there is no layer limit with MapServer >= 5). This can be changed by
+ editing the map.h file to change the value of MS_MAXLAYERS to the desired
+ number and recompiling. Here are other important default limits when using a
+ MapServer version < 5:
+
+ * MAXCLASSES 250 (set in map.h)
+ * MAXSTYLES 5 (set in map.h)
+ * MAXSYMBOLS 64 (set in mapsymbol.h)
+
+ MapServer versions >= 5 have no limits for classes, styles, symbols, or layers.
+* File paths may be given as absolute paths, or as paths relative to the
+ location of the mapfile. In addition, data files may be specified relative
+ to the SHAPEPATH.
+* The mapfile has a hierarchical structure, with the Map object being the
+ "root". All other objects fall under this one.
+* Comments are designated with a #.
+* Attributes are named using the following syntax: [ATTRIBUTENAME] ... Note
+ that the name of the attribute included between the square brackets
+ *IS CASE SENSITIVE*. Generally ESRI generated shapefiles have their
+ attributes (.dbf column names) all in upper-case for instance, and for
+ PostGIS, *ALWAYS* use lower-case.
+* MapServer Regular Expressions are used through the operating system's
+ C Library. For information on how to use and write Regular Expressions on
+ your system, you should read the documentation provided with your C Library.
+ On Linux, this is GLibC, and you can read "man 7 regex" ... This man page is
+ also available on most UNIX's. Since these RegEx's are POSIX compliant, they
+ should be the same on Windows as well, so windows users can try searching
+ the web for "man 7 regex" since man pages are available all over the web.
\ No newline at end of file
Deleted: trunk/docs/references/mapfile/introduction.txt
===================================================================
--- trunk/docs/references/mapfile/introduction.txt 2008-11-24 00:24:41 UTC (rev 8068)
+++ trunk/docs/references/mapfile/introduction.txt 2008-11-24 00:35:16 UTC (rev 8069)
@@ -1,71 +0,0 @@
-.. _mapfile:
-
-*****************************************************************************
- Mapfile Reference
-*****************************************************************************
-
-:Release: |version|
-:Date: |today|
-
-
-see also MapScript :ref:`mapscript`.
-
-
-.. toctree::
- :maxdepth: 2
-
- class
- feature
- expressions
- fontset
- grid
- Include
-
-
-
-
-The Mapfile is the heart of MapServer. It defines the relationships between
-objects, points MapServer to where data are located and defines how things are
-to be drawn.
-
-There are some important concepts that you must understand before you can
-reliably use mapfiles to configure MapServer. First is the concept of a
-`layer <../../../../docs/glossary/layer>`__. A layer is the combination of
-data plus styling. Data, in the form of attributes plus geometry, are given
-styling using CLASS and STYLE directives.
-
------------------------------------------------------------------------------
- Notes
------------------------------------------------------------------------------
-* The Mapfile is NOT case-sensitive.
-* Strings containing non-alphanumeric characters or a MapServer keyword MUST
- be quoted. It is recommended to put ALL strings in double-quotes.
-* For MapServer versions < 5, there was a default maximum of 200 layers per
- mapfile (there is no layer limit with MapServer >= 5). This can be changed by
- editing the map.h file to change the value of MS_MAXLAYERS to the desired
- number and recompiling. Here are other important default limits when using a
- MapServer version < 5:
-
- * MAXCLASSES 250 (set in map.h)
- * MAXSTYLES 5 (set in map.h)
- * MAXSYMBOLS 64 (set in mapsymbol.h)
-
- MapServer versions >= 5 have no limits for classes, styles, symbols, or layers.
-* File paths may be given as absolute paths, or as paths relative to the
- location of the mapfile. In addition, data files may be specified relative
- to the SHAPEPATH.
-* The mapfile has a hierarchical structure, with the Map object being the
- "root". All other objects fall under this one.
-* Comments are designated with a #.
-* Attributes are named using the following syntax: [ATTRIBUTENAME] ... Note
- that the name of the attribute included between the square brackets
- *IS CASE SENSITIVE*. Generally ESRI generated shapefiles have their
- attributes (.dbf column names) all in upper-case for instance, and for
- PostGIS, *ALWAYS* use lower-case.
-* MapServer Regular Expressions are used through the operating system's
- C Library. For information on how to use and write Regular Expressions on
- your system, you should read the documentation provided with your C Library.
- On Linux, this is GLibC, and you can read "man 7 regex" ... This man page is
- also available on most UNIX's. Since these RegEx's are POSIX compliant, they
- should be the same on Windows as well, so windows users can try searching
- the web for "man 7 regex" since man pages are available all over the web.
\ No newline at end of file
More information about the mapserver-commits
mailing list