Feature #305
MsSqlSpatial support
| Status: | Closed | Start Date: | ||
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assigned to: | % Done: | 0% |
||
| Category: | Data Provider | |||
| Target version: | Version 2.0.0 | |||
| Platform: | All | Resolution: | ||
| Platform version: | Patch supplied: | |||
| Status info: | 1 |
Description
History
Updated by Tim Sutton almost 5 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.
Thanks
Tim
Updated by Tim Sutton almost 5 years ago
I'm also setting this for milestone 2.0.0 pending feedback.
Updated by frdcn - over 4 years ago
Gdal/ogr does not have a driver for mssqlspatial but mssqlspatial databases can be read using ogr odbc driver
Updated by Paolo Cavallini about 3 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.
Updated by Volker Fröhlich over 2 years ago
I also misread in the first place: It's about MS-SQL, not MySQL:
Updated by Paolo Cavallini about 2 years ago
- Status changed from New 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.