MapGuide 2.1 GDAL Raster Provider

This page provides installation and configuration tips for the MapGuide 2.1 GDAL Raster Provider. Most of the information has been compiled from individuals in the user community. This document is a work in progress and incomplete. Please post any feedback on this document to the mapguide-users list.

Licensing

NOTICE: ECW Technology must be licensed from ERDAS if it used in a server application like MapGuide. Please see the following link for information on the licensing. ​http://iws.erdas.com/gis/can-i-use-ecw-technology-in-my-third-party-server.aspx

Installation

Jason Birch posted an article to the news group on where to find the vendor libraries for ECW and SID.

The install location for the libraries is not obvious. Jonathan McIntyre has provided the following directory layout for the various libraries:

C:\Program Files\OSGeo\MapGuide\Server\Fdo
   Gdal16.dll - Version 1.6.0.4

C:\Program Files\OSGeo\MapGuide\Server\bin
   Lti_dsdk_cdll.dll - Version 6.0.7.1407
   Lti_dsdk_dll.dll - Version 6.0.7.1407
   NCScnet.dll
   NCSEcw.dll
   NCSEcwC.dll
   NCSUtil.dll

C:\Program Files\OSGeo\MapGuide\Server\bin\gdalplugins
   Gdal_ecw_jp2ecw.dll (01/12/2009)
   Gdal_MrSID.dll (11/28/2008)

In addition, please ensure that the GDAL Provider is listed in provider.xml

You may also receive errors (apparent in debugging mode) regarding missing msvcp71.dll and msvcr71.dll files. You can download these from many internet sites and copy them to the C:\Program Files\OSGeo\MapGuide\Server\bin folder.

Debugging

Jonathan has also supplied some debugging steps for the GDAL Provider:

1. Starting MG in debug mode
   1. Open cmd window
   2. Cd to C:\Program Files\OSGeo\MapGuide\Server\bin
   3. Type ‘set cpl_debug=on’ (no quotes needed)
   4. Type ‘mgserver run’ (no quotes needed)
   5. You should see:

      (1392) Server starting...
      (1392) Mentor Coordinate System Library
      (1392) Server started.
      

2. Setting up image in MG site
   1. Use Maestro to create Feature Source for image
      1. Create New GDAL Feature Source
      2. Add file(s) to list-you should see something like the following show up in the console:

         GDAL: Auto register C:\Program Files\OSGeo\MapGuide\Server\bin\gdalplugins\gdal_ECW.dll using GDALRegister_ECW.
         GDAL: Auto register C:\Program Files\OSGeo\MapGuide\Server\bin\gdalplugins\gdal_ECW_JP2ECW.dll using GDALRegister_ECW_JP2ECW.
         GDAL: Auto register C:\Program Files\OSGeo\MapGuide\Server\bin\gdalplugins\gdal_MrSID.dll using GDALRegister_MrSID.
         GDAL: Auto register C:\Program Files\OSGeo\MapGuide\Server\bin\gdalplugins\gdal_ECW.dll using GDALRegister_ECW.
         GDAL: Auto register C:\Program Files\OSGeo\MapGuide\Server\bin\gdalplugins\gdal_ECW_JP2ECW.dll using GDALRegister_ECW_JP2ECW.
         GDAL: Auto register C:\Program Files\OSGeo\MapGuide\Server\bin\gdalplugins\gdal_MrSID.dll using GDALRegister_MrSID.
         MrSID: Opened zoom level 1 with size 2500x2500.
         MrSID: Opened zoom level 2 with size 1250x1250.
         MrSID: Opened zoom level 3 with size 625x625.
         MrSID: Opened zoom level 4 with size 313x313.
         MrSID: Opened zoom level 5 with size 157x157.
         MrSID: Opened zoom level 6 with size 79x79.
         MrSID: Opened zoom level 7 with size 40x40.
         MrSID: Opened zoom level 0 with size 5000x5000.
         MrSID: Opened image: width 5000, height 5000, bands 3
         GDAL: GDALOpen(D:\projects\Client\Data\SDF/DO_S03_9608_40.sid, this=0FB15438)  succeeds as MrSID.
         GDAL: GDALClose(, this=0FB15D18)
         GDAL: GDALClose(, this=0FB16088)
         GDAL: GDALClose(, this=0FB16410)
         GDAL: GDALClose(, this=0FB16798)
         GDAL: GDALClose(, this=0FB16B20)
         GDAL: GDALClose(, this=0FB16EA8)
         GDAL: GDALClose(, this=0FB17230)
         GDAL: GDALClose(D:\projects\Client\Data\SDF/DO_S03_9608_40.sid, this=0FB15438
         

Configuration Parameters

Jason Birch has had more success running a stable MapGuide with connection pooling disabled. In serverconfig.ini, this can be accomplished by disabling connection pooling entirely

[FeatureServiceProperties]
DataConnectionPoolEnabled = 0

If you require connection pooling for performance of other providers, you may instead wish to attempt to just exclude the GDAL Provider from the connection pool provider list. Note that in Jason's experience this improved reliability, but not to the same level as disabling connection pooling entirely; his guess was that the GDAL provider exercises some bug more reliably than the other providers, but the instability may be entirely unrelated.

[FeatureServiceProperties]
DataConnectionPoolExcludedProviders = OSGeo.Gdal