Feature request #305

MsSqlSpatial support

Added by rstuven-gmail-com - about 17 years ago. Updated over 12 years ago.

Assignee:godofredo -
Category:Data Provider
Pull Request or Patch supplied: Resolution:
Easy fix?:No Copied to github as #:10364


#1 Updated by Tim Sutton over 15 years ago

Changed to enhancement priority as major should be used for implemented features which are broken. I'm going to flag this for attention of Godofredo who is working on a generic sql access layer via gdal. Is MsSqlSpatial supported via gdal? Please advise.



#2 Updated by Tim Sutton over 15 years ago

I'm also setting this for milestone 2.0.0 pending feedback.

#3 Updated by frdcn - about 15 years ago

Gdal/ogr does not have a driver for mssqlspatial but mssqlspatial databases can be read using ogr odbc driver

#4 Updated by Paolo Cavallini over 13 years ago

It seems that MySQL spatial extension is not widely used, not very actively developed: http://dev.mysql.com/doc/refman/5.0/en/spatial-extensions.html
It is possible that spatial information can however be read through OGR: http://www.gdal.org/ogr/drv_mysql.html
I would suggest to close this ticket.

#5 Updated by Volker Fröhlich about 13 years ago

I also misread in the first place: It's about MS-SQL, not MySQL:


#6 Updated by Paolo Cavallini over 12 years ago

  • Status changed from Open to Closed
  • Resolution set to upstream

I think this should be solved within GDAL/OGR, I do not see a point in writing a db provider for this. Please reopen if I'm wrong.

Also available in: Atom PDF