Have you removed the 'Seas' nvarchar field from the table to see if that
changes the situation ? By the way, if you change the underlying table, I
think it might be best to delete the layer and then re-create the layer
before re-testing.
On Tue, Oct 25, 2011 at 2:16 PM, springrider <[email protected]>wrote:
> Thanks David
>
> This table in SQL Server is the result of the import of a shapefile using
> Shape2Sql tool. The spatial index is available and the columns type seems
> to
> be correct to me.
>
> So i have no solution and looks like the SQL server extension in GS does
> not
> work for me and i won't be able to use GeoServer :(...
>
> Thanks
>
> Sylvain
>
> --
> View this message in context:
> http://osgeo-org.1803224.n2.nabble.com/SQL-Server-Layers-not-displayed-tp6915925p6927422.html
> Sent from the GeoServer - User mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
