Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

Within our company we are deciding which DBMS we will use to store spatial data. IT wants MySQL with the Spatial extension because there is already knowledge about handling MySQL DB. We are doing quite simple calculations with the data. The only thing I am worried about is the polygon handling of MySQL.

Is it still true that MySQL only supports bounding box calculations instead of the real polygon geometry? Or is this problem gone with newer versions of MySQL?

share|improve this question

1 Answer 1

up vote 4 down vote accepted

Your assumption is pretty much correct. MySQL's spatial support is ... simplistic to say the least. It does work, but you'll find very few GIS applications support it. This isn't specific to just polygons, any spatial feature is more limited in MySQL because while it does store them in the same way (WKB), there simply aren't as many functions to manipulate or interogate it.

Full details of the MySQL Spatial Extension analysis functions can be found here: http://dev.mysql.com/doc/refman/5.0/en/spatial-analysis-functions.html

Compare that to Oracle Locator (their "free" spatial extension if you have Oracle Enterprise and the $$$ to match): http://docs.oracle.com/cd/B19306_01/appdev.102/b14255/sdo_locator.htm

And of course, PostGIS: http://postgis.net/docs/manual-2.0/reference.html

MS SQL Server has spatial too - http://msdn.microsoft.com/en-us/library/bb964708%28v=sql.105%29.aspx

That's before you start playing with things like topography's, geography's and rasters, none of which I believe MySQL supports. You can clearly see which of those four products is the least feature-complete for spatial data (Hint: MySQL). Its very subjective which is the winner; thats an eternal religious war that belongs in other threads. ;-)


You may only be doing very simple things with the data at this point, however going forward non-MySQL will give you more options if you decide to expand your spatial data processing/storage.

share|improve this answer
    
Working with Spatial Data (Database Engine) - msdn.microsoft.com/en-us/library/bb933876%28v=sql.105%29.aspx –  geographika Nov 9 '12 at 14:35
    
@geographika - I found that much, but there's no nice list of functions like I've referenced with the other three. Ah no, found it at last, needed a second look. Thanks. –  GIS-Jonathan Nov 9 '12 at 14:44
    
Yes - hard to find.I always have to go through google. Function list for GEOMETRY types - msdn.microsoft.com/en-us/library/bb933973.aspx - the nice thing is it meets the OGC standards –  geographika Nov 9 '12 at 20:11

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.