[mapguide-internals] RE: Motion: RFC 30 - FDO Configuration
greg.boone at autodesk.com
Thu Sep 6 10:48:53 EDT 2007
Bounds override/specification for the MapGuide Enterprise and OpenSource
Raster Providers is not currently accomplished through the specification
of insertionPoint, resolution, etc, in the configuration document. As of
the FDO 3.2.2 release, a new <bounds> element was added to the
configuration file for the raster providers that allowed this
information to be specified independent of the aforementioned
Geo-reference information. Typically, an application would choose to
either specify the Geo-reference information or the bounds information
in a configuration file, not both.
The reason that the <bounds> element was added was that even with the
geo-reference information included in the configuration file it was not
enough information to fully determine the bounds of the raster image.
The raster provider was still forced to access the raster image to
extract the image height and width to determine the exact image bounds.
See the attached specification for complete details.
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Leaf Li
Sent: Wednesday, September 05, 2007 11:55 PM
To: mapguide-internals at lists.osgeo.org
Subject: [mapguide-internals] RE: Motion: RFC 30 - FDO Configuration
Bound override for Raster provider is done by insertpoint, resolution,
rotation override. If you take a look at schema override of Raster
provider, you will find there is no bounds override in its physical
schema mapping. Actually bound can be computed from insertpoint,
resolution, rotation override. So you can implement bound override from
insertpoint, resolution, rotation override.
As for specifying the layer to be used for each MgRasterWMSItem, it is
done by from MgRasterItem::m_name. For MgRasterFileItem, it means raster
file name. For MgRasterWmsItem, it means layer name.
I agree with you. One sample make more sense. I will add it later.
From: "Jason Birch" <Jason.Birch at nanaimo.ca>
Subject: RE: [mapguide-internals] Motion: RFC 30 - FDO Configuration
To: "MapGuide Internals Mail List"
<mapguide-internals at lists.osgeo.org>
<8E468917B01800408B91984428BE03DD072A5889 at starfish.nanaimo.ca>
Content-Type: text/plain; charset="us-ascii"
Hi Leaf Li,
Maybe I'm missing something, but I don't see support for the Bounds
override in MgRasterFileItem.
I don't see where you would specify the layer to be used for each
MgRasterWMSItem ... is the name of the MgRasterItem used for that? One
of the largest benefit of config files with the WMS provider is being
able to ask the server for multiple layers in a single request. An
example would help my understanding.
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals