#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 |
--------------------------------------+-------------------------------------
Changes (by hamish):
* version: unspecified => svn-trunk
Comment:
Hi,
fwiw in spatial circles PostGIS heavily dominates the market for spatially
enabled DBs, even when proprietary systems are considered.
That is not to say there's anything wrong with MySQL's spatial support
(I've no experience with it), just that the popularity argument isn't
going to convince many GIS programmers.
also note that GRASS is a topologically enabled GIS, and spatially-enabled
DBs are generally much simpler beasts.
see also the sqlite offering: spatialite.
http://live.osgeo.org/en/overview/postgis_overview.html
http://live.osgeo.org/en/overview/spatialite_overview.html
Meanwhile, GRASS's native vector format remains heavily favored support-
wise.
regards,
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2190#comment:1>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
