#305 closed enhancement (upstream)
MsSqlSpatial support
Reported by: | Owned by: | godofredo | |
---|---|---|---|
Priority: | minor: annoyance | Milestone: | Version 2.0.0 |
Component: | Data Provider | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | yes |
Description
Change History (8)
comment:1 by , 18 years ago
Milestone: | → Version 1.0 Release |
---|---|
Version: | → HEAD |
comment:2 by , 16 years ago
Awaiting user input: | set |
---|---|
Must Fix for Release: | → No |
Owner: | changed from | to
Priority: | major: does not work as expected → minor: annoyance or enhancement |
follow-up: 4 comment:3 by , 16 years ago
Milestone: | Version 1.0.0 → Version 2.0.0 |
---|
I'm also setting this for milestone 2.0.0 pending feedback.
comment:4 by , 16 years ago
Gdal/ogr does not have a driver for mssqlspatial but mssqlspatial databases can be read using ogr odbc driver
comment:5 by , 14 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.
comment:7 by , 13 years ago
Resolution: | → upstream |
---|---|
Status: | new → closed |
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.
Note:
See TracTickets
for help on using tickets.
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