[mapguide-internals] Raster Layer Default Extents

Traian Stanev traian.stanev at autodesk.com
Mon Mar 5 17:15:25 EST 2007

Hi Frank. 

I was able to make it work correctly. The problem was that MapGuide
(incorrectly) uses the string returned by GetCoordinateSystem() to
determine if a spatial context is defined. The GDAL provider returns
empty string for GetCoordinateSystem() so MapGuide doesn't even try to
read the values from the spatial context. I changed your
GetCoordinateSystem() to simply return the same value as the name of the
spatial context and it started working fine.

Also, I recommend making the DefaultRasterLocation property "required"
so that it shows up in the generic connection dialog in MapGuide Studio.
This way it makes it easy for someone using Studio to set up a GDAL
connection. It's strange that properties that are not explicitly
"required" don't show up in the Studio UI, but oh well.


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Frank
Warmerdam (External)
Sent: Monday, March 05, 2007 12:42 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Raster Layer Default Extents

Jason Birch wrote:
> Hi Frank,
> For the ADSK raster provider, it looks like image reference
> may be stored in a separate XML chunk, associated with the
> FeatureSource.  Perhaps MapGuide relies on this rather than the
> returned from the provider?


In this case I was using the "no xml config" option.  That is, just
giving a DefaultRasterFileLocation property value when connecting.
So there shouldn't be any alternative configuration xml.

Best regards,
I set the clouds in motion - turn up   | Frank Warmerdam,
warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo,

mapguide-internals mailing list
mapguide-internals at lists.osgeo.org

More information about the mapguide-internals mailing list