[mapserver-commits] r8216 - in trunk/docs: input/vector output

[svn at osgeo.org]

Author: hobu
Date: 2008-12-09 02:03:52 -0500 (Tue, 09 Dec 2008)
New Revision: 8216

Modified:
   trunk/docs/input/vector/index.txt
   trunk/docs/output/svg.txt
Log:
can only have 3 levels of headings or latex can't build

Modified: trunk/docs/input/vector/index.txt
===================================================================
--- trunk/docs/input/vector/index.txt	2008-12-09 07:03:29 UTC (rev 8215)
+++ trunk/docs/input/vector/index.txt	2008-12-09 07:03:52 UTC (rev 8216)
@@ -32,46 +32,7 @@
 	From: http://coris.noaa.gov/glossary/glossary_l_z.html#v
 
 
-MapServer can access vector file formats and database connections.  It can also
-access raster or image data.  This is a summary of the vector and database 
-formats with particular focus on how to use them in a MapServer map file and 
-access them using command line tools like **ogrinfo**.
 
-MapServer and vector data access
-------------------------------------
-
-MapServer has two main methods for accessing data:
-
-*   Through built-in, format-specific, data access capabilities.
-
-.. note::
-    The most basic form of data access uses the built-in capabilities 
-    that were linked into MapServer when it was compiled.  These 
-    capabilities are limited to only a few types of vector data, 
-    such as ESRI Shapefile,	PostGIS, Oracle Spatial and ArcSDE.  The 
-    default, built-in, format for MapServer is the ESRI Shapefile format.
-
-*	Using the capabilities of third-party data access libraries.
-
-.. note::
-    One of the most powerful features of MapServer is the ability to use data 
-    formats through a pseudo plug-in environment.  The most significant 
-    third party library being used is GDAL/OGR.  This includes raster 
-    (GDAL) and vector (OGR) data.
-
-Using OGR
-------------------------------------
-
-OGR is used behind the scenes by MapServer when requested.  MapServer does not 
-require OGR in order to run.  Some users may never need the additional 
-capabilities OGR offers, but many users find them absolutely necessary.  Because 
-MapServer is capable of accessing data via OGR, there is less need to program 
-specific types of data format support directly into MapServer.  Instead, further 
-additions can be made to OGR and then be used by MapServer.  In essence, the 
-background libraries allow MapServer to bring the data into an internal, 
-memory-based format that MapServer can use.  For the most part, using 
-OGR-related formats is seamless and intuitive.
-
 .. toctree::
    :maxdepth: 1
 

Modified: trunk/docs/output/svg.txt
===================================================================
--- trunk/docs/output/svg.txt	2008-12-09 07:03:29 UTC (rev 8215)
+++ trunk/docs/output/svg.txt	2008-12-09 07:03:52 UTC (rev 8216)
@@ -322,7 +322,7 @@
           
 
 Specific FORMATOPTIONs Related to goSVG
-.......................................
+***********************************************************
 
 GOSVG
   should be set to TRUE. The default is false.