id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,external_id 740,GETSPATIALCONTEXTS and GDAL always returns default extents,crispinatime,,"Hi, I have been trying to debug Maestro wondering why when a raster config resource file is built it always contains bogus extents (-10000000 to 10000000). I finally traced through to 'GetSpatialContextInfo(...)' which has created a temporary session resource to query via the MapGuide API - as far as I can see on my layer set-ups it is GETSPATIALCONTEXTS that is at fault. I have tested the file with GDALinfo.exe to confirm the extents are returned OK by the GDAL14.dll. To recreate (for example) add a raster file to a GDAL composite feature source in Maestro and put a braek point in HttpServerConnection.cs at line 922 to step into the call and see the extents generated. Or simply edit the FeatureSource in the second URL below: C {{{ http://localhost/mapguide/mapagent/mapagent.fcgi?OPERATION=GETSPATIALCONTEXTS &VERSION=1.0.0 &SESSION=5360ba88-0000-1000-8000-001422f493b1_en_7F0000010AFC0AFB0AFA &FORMAT=text%2fxml &RESOURCEID=Session%3a5360ba88-0000-1000-8000-001422f493b1_en_7F0000010AFC0AFB0AFA%2f%2fccbeeed0-d467-41c9-a439-8d7fc84593bc.FeatureSource &ACTIVEONLY=1 &LOCALE=en }}} Can simplify for any GDAL resource you have with the following {{{ http://localhost/mapguide/mapagent/mapagent.fcgi?OPERATION=GETSPATIALCONTEXTS &VERSION=1.0.0 &FORMAT=text%2fxml &RESOURCEID=Library://Test/Data/NS66.FeatureSource &ACTIVEONLY=1 &LOCALE=en }}} Always returns extents like below (non-GDAL feature sources return good extents) {{{ ... -10000000 -10000000 10000000 10000000 ... }}} ",defect,closed,medium,2.2,Feature Service,2.2.0,critical,fixed,,,