The fdogdal provider is the open source raster provider for FDO (and hence MapGuide). It is implemented on top of the ​GDAL raster library. Frank Warmerdam (warmerdam at pobox.com) is the primary author of fdogdal. Questions about the provider may asked on the fdo or mapguide users lists.

Documents

• User Documentation

For MapGuide Users

Using fdogdal in Studio

To publish rasters using the open source raster provider with ​Autodesk MapGuide Studio use the following steps:

1. Start Studio and connect to your MapGuide Open Source 1.1.0 server.
2. Then do File > New > Data Connection...
3. In the Connect To Data dialog that comes up, select OSGeo FDO Provider for Raster, then press OK. An editor that says "Configure a Feature Resource using the Generic Editor" will display.
4. In the Connection Properties grid, there is a DefaultRasterFileLocation property. Click in the value column and enter the directory where your image files are. On Linux it has the form /home/thf/myimages and on Windows it has the form C:\myimages.
5. The configuration of the raster source is now complete, save the resource and start using it.

Notes:

• The layer definition preview will not show the raster. In order to preview the data, create a map definition and set the extents of the map to contain the raster data. If the extents are set correctly the raster data should show in the preview.

Frank's fdogdal Downloads

Visit the Frank's fdogdal 3.2.0 updates for MapGuide 1.1.0 download site for ecw, and mrsid support, as well as several bug fixes and features improvements:

​http://home.gdal.org/dl/mapguide/

For MGOS 1.2.0, instead of using the mg_fdogdal_110.zip file found at the above location, unzip the contents of ​http://download.osgeo.org/mapguide/releases/1.2.0-rc1/MGOS1.2.0GDALPatch.zip to C:\Program Files\MapGuideOpenSource\Server\Bin. If you have accidently unzipped mg_fdogdal_110.zip, using this zip file will undo your changes.

Debugging with Rasters

It can be instructive to run MgServer.exe at the command line in interactive mode, with the CPL_DEBUG environment variable set to ON. This will report various GDAL level debugging output. At the very least this should give an idea of the files that GDAL is trying to open.

eg.

  cd \"Program Files"\MapGuideOpenSource\server\bin
  set CPL_DEBUG=ON
  mgserver stop
  mgserver run