Changes between Version 1 and Version 2 of MySQLSpatial

Timestamp:

Jul 31, 2009, 11:22:19 AM (15 years ago)

Author:

mikehostetler

Comment:

--

MySQLSpatial

@@ -14 +14 @@
  * The method of using OGR with a .ovf file didn't work for us, we were never able to find out why.
 
-=== Mapfile Syntax ===
+=== Step 1: Create your DSN ===
+The first step necessary is to craft your OGR DSN.  Documentation on how to craft this is available here: http://trac.osgeo.org/mapserver/wiki/VirtualSpatialData
 
-Simply specifying the OGR DSN in the CONNECTION statement of your LAYER definition proved successful.
+For MySQL Specifically, the DSN should be formatted as: 
+{{{
+MYSQL:##DATABASE##,host=##HOST##,user=##USERNAME##,pass=##PASSWORD##,tables=##TABLE##,##TABLE##,##TABLE##
+}}}
+
+=== Step 2: Test your DSN ===
+After creating your DSN, test it using the utility `ogrinfo`.
+
+{{{
+ogrinfo -ro -al MYSQL:##DATABASE##,host=##HOST##,user=##USERNAME##,pass=##PASSWORD##,tables=##TABLE## -sql 'SELECT geom FROM ##TABLE##'
+}}}
+
+=== Step 3: Edit your mapfile ===
+
+After testing and verifying that OGR can connect and display your data in MySQL, you can drop your DSN and Data statement right into your mapfile.  Specify the '''CONNECTIONTYPE''' as '''OGR'''.
 
 {{{
@@ -40 +55 @@
 }}}
 
-=== TABLE Schema and Data ===
+
+=== Reference: TABLE Schema and Data ===
 
 Here's the table structure that was used.