To clarify I have a column in SQL 2008 of type geography that I would like to
use in map server. I have been able to do this using the OGR ODBC driver.
However, when trying to use the Native SQL 2008 driver that has been added to
MS4W 2.3.1 I get the error message "sys.geometry is incompatible with
sys.geography" when executing the query captured by profiling the database
request.
It appears as though the SQL 2008 driver either assumes that it will always
(and only) be used against geometry columns or there is a configuration setting
I that I can use to tell it that the internal datatype is geography and as such
builds the WHERE clause using the geomertry type for the bounding box filter.
SQL Excerpt:
the_geom.STIntersects(Geometry::STGeomFromText('POLYGON(...)') = 1
where in this case the_geom is a Geography column that cannot be used in an
STIntersects call with a Geometry object.
I am hoping someone can tell me about the configuration option to change this
behavior or confirm that it does not exist so we can discuss the possibility of
adding such an option.
Let me know if you need additional details.
There are two ways to define an object spatially in 2008 one as type geometry
and one as geography.
--
View this message in context:
http://n2.nabble.com/Using-the-SQL-Server-2008-Plugin-with-a-Geography-column-tp2565867p2575468.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
