I have been using postgresql as a data store and although I am very happy with it, I need to use sql server if at all possible.
I have run into a couple of problems that I am hoping there are solutions for 1. Geography vs Geometry types. Afaik geography is preferred in sql server so I initially setup a table with the type being geography, but when I create a layer from it in geoserver the resulting type shows as byte[] and geoserver doesn't know what to do with it, what SRID etc. I don't have a problem using geometry, but I find this odd, and perhaps it's related to #2 2. Sql views show a similar problem. I can make a layer out of a table with a geometry type and geoserver displays it. But if I make a view that is simply 'select * from mytable' the data type returned is byte[] which isn't working. Any thoughts on this appreciated. charles (Geoserver 2.1RC2) ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
