Opened 18 years ago

Closed 13 years ago

Last modified 13 years ago

#305 closed enhancement (upstream)

MsSqlSpatial support

Reported by: rstuven@… 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 anonymous, 18 years ago

Milestone: Version 1.0 Release
Version: HEAD

comment:2 by timlinux, 16 years ago

Awaiting user input: set
Must Fix for Release: No
Owner: changed from gsherman to godofredo
Priority: major: does not work as expectedminor: annoyance or enhancement

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

comment:3 by timlinux, 16 years ago

Milestone: Version 1.0.0Version 2.0.0

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

in reply to:  3 comment:4 by frdcn, 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 pcav, 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:6 by volter, 14 years ago

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

http://www.gdal.org/ogr/drv_mssqlspatial.html

comment:7 by pcav, 13 years ago

Resolution: upstream
Status: newclosed

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.