[mapguide-internals] Raster Layer Default Extents

Tom Fukushima tom.fukushima at autodesk.com
Mon Mar 5 14:09:10 EST 2007

Hi Frank,

Studio uses the spatial contexts of the feature source to set the layer
preview extents and the extents of the map definition.

To see what your provider is returning for spatial contexts, use the
MapGuide site HTML/mapagent pages
1) click on Feature in the top left pane
2) click on GetSpatialContexts in the bottom left pane
3) Enter the resource ID of the feature source you are testing
4) Press submit, and enter administrator credentials

The returned XML should look something like the following:
<?xml version="1.0" encoding="UTF-8"?>
  <SpatialContext IsActive="true">
    <Description>Arbitrary X-Y Coordinates (Meters)</Description>
"Meter", 1],AXIS["X",EAST],AXIS["Y",NORTH]]</CoordinateSystemWkt>

The important parts for Studio are the CoordinateSystemWkt and the


-----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 10:22 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Raster Layer Default Extents


For several weeks now I have been working towards resolving the problem
where mapguide does not recognise default extents for GDAL based raster
layers.  I have modified the raster provider in trunk (and via local
uncommitted changes in 3.2.x branch) to set the extents returned by the
SpatialContextReader properly.  However, this does not seem to be having
the desired effect in mapguide.

I have essentially confirmed that mapguide is reading back my correct
spatial extents from the spatial context reader, but when creating a new
layer they don't seem to have any effect.  Can anyone comment on why
that might be?

My process was:
  1) Install MapGuide OS 1.1.0 for windows.
  2) Build FDO from source (same tree I used for earlier fdogdal
  3) Checkout out 3.2.x provider into 3.2.0 fdo tree, patch it, build
     install it.
  4) I run mgserver interactively (so I can see extra fprintf's I
     in my 32x fdo provider confirming I'm using it and it is returning
     I expect).
  5) In studio I create a new layer using an existing gdal based data
     I can see via debug output that the spatial context reader is
     the expected values.
  6) But the layer extents are not defaulted such that I see the layer.
  7) If I create a map from that layer, the default map extents are 0,0
to 0,0.

Any thoughts?

The only two files in the fdogdal/Src/Provider directory are available

if someone would like to try overlaying them on the fdo32x gdal provider
and testing it themselves.  In particular I'd like some confirmation
about what is happening on the mapguide side, since I'm too chicken to
start debugging there. Perhaps I really just need to build mapguide from
source and go whole hog on debugging...

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