[mapserver-commits] r8228 - trunk/docs/input/vector

[svn at osgeo.org]

Author: hobu
Date: 2008-12-09 20:41:09 -0500 (Tue, 09 Dec 2008)
New Revision: 8228

Modified:
   trunk/docs/input/vector/index.txt
   trunk/docs/input/vector/mysql.txt
Log:
finish excising mygis

Modified: trunk/docs/input/vector/index.txt
===================================================================
--- trunk/docs/input/vector/index.txt	2008-12-10 01:37:07 UTC (rev 8227)
+++ trunk/docs/input/vector/index.txt	2008-12-10 01:41:09 UTC (rev 8228)
@@ -68,7 +68,7 @@
    inline
    kml
    oracle_spatial
-   mygis
+   mysql
    ntf
    sdts
    tiger

Modified: trunk/docs/input/vector/mysql.txt
===================================================================
--- trunk/docs/input/vector/mysql.txt	2008-12-10 01:37:07 UTC (rev 8227)
+++ trunk/docs/input/vector/mysql.txt	2008-12-10 01:41:09 UTC (rev 8228)
@@ -1,13 +1,30 @@
-.. sectnum::
+.. _mysql:
 
+***************************************************
+MySQL
+***************************************************
+
+:Revision: $Revision$
+:Date: $Date$
+:Author: David Fawcett
+:Contact: david.fawcett at moea.state.mn.us
+
+.. contents::
+    :depth: 2
+    :backlinks: top
+
+
 Introduction
 ============
 
-This method takes advantage of OGR's MySQL driver and avoids the need to set up an ODBC connection.  
+This method takes advantage of OGR's MySQL driver and avoids the need to set
+up an ODBC connection.
 
-This is the primitive MySQL support for point data, not the recently added  `MySQL spatial support found in GDAL/OGR 1.3.2`_ .  
+This is the primitive MySQL support for point data, not the recently added
+`MySQL spatial support found in GDAL/OGR 1.3.2`_ .
  
-Support for this functionality is found in GDAL/OGR 1.2.6 and older on Windows and GDAL/OGR 1.3.2 on Linux.
+Support for this functionality is found in GDAL/OGR 1.2.6 and older on Windows
+and GDAL/OGR 1.3.2 on Linux.
 
 **Needed**
 
@@ -37,7 +54,8 @@
 - 'testdata' is the table containing the coordinate data
 - host and port are for MySQL server 
 
-Use the GeometryField element to tell OGR which fields store the x and y coordinate data.  Mine are simply named x and y.
+Use the GeometryField element to tell OGR which fields store the x and y
+coordinate data. Mine are simply named x and y.
 
 
 Test Connection with ogrinfo
@@ -88,19 +106,18 @@
        END
    END  
 
-DATA in the LAYER definition should be the same as the name attribute of the OGRVRTLayer element in the ovf file. 
+DATA in the LAYER definition should be the same as the name attribute of the
+OGRVRTLayer element in the ovf file.
 
-*For this to draw, you need to have a SYMBOLSET defined in your mapfile and have a symbol called 'circle' in your symbols.sym file.*
+*For this to draw, you need to have a SYMBOLSET defined in your mapfile and
+have a symbol called 'circle' in your symbols.sym file.*
 
 More Information
 =================
 
- `MapServer OGR HowTo`_ 
+* :ref:`ogr` 
+* :ref:`vector`
 
- `MapServer Vector Data Reference - Virtual Spatial Data`_ 
-
 .. #### rST Link Section ####
 
 .. _`MySQL spatial support found in GDAL/OGR 1.3.2`: http://www.gdal.org/ogr/drv_mysql.html 
-.. _`MapServer OGR HowTo`: http://mapserver.gis.umn.edu/docs/howto/ogr_howto
-.. _`MapServer Vector Data Reference - Virtual Spatial Data`: http://mapserver.gis.umn.edu/docs/reference/vector_data/VirtualSpatialData
\ No newline at end of file