The data imported into SQL Server Spatial is in whatever native SRS the data was captured in unless you converted it during import.
So when you connect your datasource you should be getting the native SRS for the data. At the time you define your map you can pick the alternate SRS for all datasources to be converted into. You only do an override if the source doesn't know what the value is. The override is simply to set the SRS to a value that matches what the data was captured in. Dave -----Original Message----- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Jamo Sent: Wednesday, February 29, 2012 8:59 PM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] Re: multiple coordinate systems SQL spatial? using MSSQL Spatial (SQL Server 10.0.2531) I've not looked at the SRS since I first started using SQL as a datastore, so the thought hasn't really crossed my mind. I think the server only supports geography type spatial reference systems ? to overcome this i can remember setting up the below. I've setup an ExtendedCoordSys.txt in \Server\Fdo\com directory with my coordinate system Not sure if this is required. for the new geogrphy I've specified 4326 as the srid but it doesn't seem to transform to the maps coordinate system epsg 28356 /side note that was a lightning fast response!/ -- View this message in context: http://osgeo-org.1560.n6.nabble.com/multiple-coordinate-systems-SQL-spatial-tp4533662p4533691.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
