[GRASS-dev] [GRASS GIS] #2190: Use MySQL Spatial Functionality
GRASS GIS
trac at osgeo.org
Fri Feb 7 05:01:19 PST 2014
#2190: Use MySQL Spatial Functionality
--------------------------------------+-------------------------------------
Reporter: justinzane | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Database | Version: svn-trunk
Keywords: MySQL, spatial, geometry | Platform: All
Cpu: All |
--------------------------------------+-------------------------------------
Comment(by mlennert):
Replying to [ticket:2190 justinzane]:
> [https://dev.mysql.com/doc/refman/5.0/en/spatial-extensions.html]
>
> It appears that MySQL >= 5.0 supports spatial data natively. It would be
very nice to have GRASS leverage that since MySQL has a wider preinstalled
base than PostgreSQL.
What exaxtly do you mean by "leverage" in terms of native spatial data
support. Generally, GRASS uses its own data format and you can easily
import from MySQL to GRASS using OGR with v.in.ogr.
You can also link spatial data in a MySQL database to GRASS via v.external
(also via OGR).
If you are speaking about attribute data management, there is a mysql
driver available in GRASS.
So AFAIK, the only difference between PostgreSQL and MySQL in their
treatment by GRASS is the PostGIS direct access driver in GRASS7, which
only allows to read and write data directly from/to PostGIS (without going
through OGR), but it does not use any of the other spatial data
functionalities in PostGIS
[http://grasswiki.osgeo.org/wiki/PostGIS#Direct_access_to_PostGIS_data_.28GRASS_7_only.29
1].
So are you pleading for a similar driver for MySQL, or what exactly are
you looking for ? I do agree with Hamish, though, that within the GIS
world, PostGIS is lightyears ahead of MySQL in terms of its adoption for
spatial data handling.
Moritz
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2190#comment:3>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list