[fdo-internals] Raster Catalogs (aka Tileindexes)

Greg Boone greg.boone at autodesk.com
Thu Jan 25 12:47:11 EST 2007

There are a couple of options for generating the bounds information in
the configuration file:

1) The FDO team can provide a small application or tool to create the
configuration file based on a set of input directories. Studio or
Studio developers could then use this tool to create the XML
configuration file.
2) Studio could use the FDO DescribeSchemaMapping command to generate
the schema mappings for a default raster connection made to a single
directory of images. However, as stated, this mechanism is limited in
that it only generates mappings for a single directory.


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Frank
Warmerdam (External)
Sent: Thursday, January 25, 2007 12:55 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] Raster Catalogs (aka Tileindexes)

Jason Birch wrote:
> ------------
> I would like to help the webstudio guys add raster support including
> building the config doc.  It should be pretty easy.
> ------------
> My concern with this would be those of us who are using MapGuide
> with MapGuide Open Source.  If you are going to do this, could you
> please consider making it modular enough that I could easily adapt it
> a standalone page that generates the config file, creates a new
> unmanaged raster data source, and uploads the config file into the
> resource content?


I was assuming that the Studio developers would be doing something for
generating this config file in studio.  Actually, I have no idea how
normally create these config files.

Having said earlier that creating the config file should be easy, I must
confess that on sober second thought I'm not exactly sure how I'm going
approach it.  The GDAL PHP bindings and I'm not sure we want Web Studio
having a dependency on GDAL PHP bindings anyways.

In theory I suppose Web Studio can use FDO itself to get the bounds for
individual files and then build the config file based on that.  I
that is what Studio does?

So, I find myself backing off a bit and thinking perhaps I would offer
an output switch for my existing gdaltindex program that would provide
XML config files instead of shapefiles.

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,

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

More information about the fdo-internals mailing list