[mapguide-users] more 2.1 problems (GDAL this time)

[Jason Birch]

config.xml is optional.  You can either point to a single file, or use Maestro to generate a config file.

I've had mixed results using this with aliased folders; I think that last time I tried it failed (maybe it was writing the alias to the config file, rather than the explicit path?)  I've been using explicit paths, and just making sure that drive letters match between development and production.  I haven't tried accessing rasters over the network.

Jason

From: Dave Wilson
Sent: Monday, June 15, 2009 10:53 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] more 2.1 problems (GDAL this time)

That suggests to me the gdal provider isn't creating a config.xml. I haven't used the gdal provider so I don't know if it should create a config.xml or not.

Can you or someone check a raster resource on the prior release and  see if it contains a config.xml? It if doesn't then something else is broken and config.xml files are not needed by the provider.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20090615/0b3ad7a8/attachment.html