MapGuide 2.2 GDAL Raster Provider
This page provides installation and configuration tips for the MapGuide 2.2 GDAL Raster Provider. This document is a work in progress. Please post any feedback on this document to the mapguide-users list.
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
If you want to avoid problems with invalid spatial extents when setting up new layers, you may want to use the GDAL provider that Jackie compiled from and attached to #740:
- http://trac.osgeo.org/mapguide/attachment/ticket/740/GDALProvider_493.zip (32-bit)
- http://trac.osgeo.org/mapguide/attachment/ticket/740/GRFPProvider_FDO35_MGOS22_x64.zip (64-bit)
Tamas Szekeres is maintaining binary distributions of the GDAL library with the plugins for the MapServer project. His distributions work with MapGuide. The distributions are available here http://vbkto.dyndns.org/sdk/. For MapGuide 2.2, the following builds are required:
- 32 bit Windows: http://vbkto.dyndns.org/sdk/PackageList.aspx?file=release-1500-gdal-1-6-mapserver-5-6.zip
- 64 bit Windows: http://vbkto.dyndns.org/sdk/PackageList.aspx?file=release-1500-x64-gdal-1-6-mapserver-5-6.zip
From the bin and bin/gdal/plugins directories contained in the zip file, copy the following files to the MapGuide Server:
Server\bin\libecwj2.dll Server\bin\lti_dsdk_dll.dll Server\bin\gdalplugins\gdal_ECW_JP2ECW.dll Server\bin\gdalplugins\gdal_MrSID.dll Server\Fdo\gdal16.dll Server\Fdo\geos_c.dll Server\Fdo\iconv.dll Server\Fdo\libcurl.dll Server\Fdo\libexpat.dll Server\Fdo\libpq.dll Server\Fdo\libtiff.dll Server\Fdo\proj.dll Server\Fdo\spatialite.dll Server\Fdo\xerces-c_2_8.dll Server\Fdo\zlib1.dll
Format Support, Performance, and Stability
Trevor Wekel has verified the following raster file formats are usable in MapGuide 2.2:
- JPEG 2000
With the default serverconfig.ini configuration, an 8 user load test against a 25 file catalog for each format generated no errors over an 8 hour run. Scalability was limited to approximately 2 cpus and a memory leak of roughly 200 MB was observed over the 8 hour period.
Make sure that mapguide is reading the correct co-ordinate system is being read from the source files, override it if necessary.
Jonathan McIntyre has supplied some debugging steps for GDAL in MapGuide 2.1 which should work for MapGuide 2.2:
- Starting MG in debug mode
- Open cmd window
- Cd to C:\Program Files\OSGeo\MapGuide\Server\bin
- Type ‘set cpl_debug=on’ (no quotes needed)
- Type ‘mgserver run’ (no quotes needed)
- You should see:
(1392) Server starting... (1392) Mentor Coordinate System Library (1392) Server started.
- Setting up image in MG site
- Use Maestro to create Feature Source for image
- Create New GDAL Feature Source
- 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
- Use Maestro to create Feature Source for image
The default serverconfig.ini settings set by the installer should be sufficient. No additional serverconfig.ini modifications are required.
The following companies have supported the GDAL work:
- Pacific Alliance Technologies
- Explore Australia
- Ennoble Consultancy
- Spatial Integrators