| 8 | | * [#ForMapGuideUsers MapGuide Users] |
| 9 | | * [#UsingfdogdalinAutodeskMapGuideStudio Using with Autodesk Studio] |
| 10 | | * [#FranksfdogdalDownloads Downloads for ECW and MrSID support] |
| 11 | | * [#Rasterperformanceenhancements Performance-enhancing tile index support] |
| | 8 | * [#MrSIDandECWPluginSupport MrSID and ECW Plugin Support] |
| | 9 | * [#UsingfdogdalinAutodeskMapGuideStudio Using with Autodesk MapGuide Studio] |
| | 10 | * [#ConfigFileCreation Creating Tile Index Config Files] |
| | 11 | * [#DebuggingRastersinMapGuide Debugging Rasters in MapGuide] |
| 21 | | == Using fdogdal in Autodesk !MapGuide Studio == |
| | 21 | MrSID and ECW are popular wavelet compression formats used for imagery. Support for these formats is not included in the official FDO or !MapGuide releases for licensing issues, but you can add plugins to your installation to use these formats. |
| | 22 | |
| | 23 | Frank Warmerdam is making these plugins available on his site: |
| | 24 | |
| | 25 | http://home.gdal.org/dl/mapguide/ |
| | 26 | |
| | 27 | Make sure to read the appropriate license agreements, and then follow these instructions for your version of FDO/MapGuide |
| | 28 | |
| | 29 | === FDO 3.2.0 / !MapGuide 1.1.0 === |
| | 30 | |
| | 31 | Follow the instructions in the readme file (http://home.gdal.org/dl/mapguide/README.txt), downloading and unzipping the files mg_fdogdal_110.zip, mg_ecw_110.zip, and/or mg_mrsid_110.zip into your !MapGuideOpenSource/Server/Bin directory |
| | 32 | |
| | 33 | === FDO 3.2.3 / !MapGuide 1.2.0 === |
| | 34 | |
| | 35 | Only download and unzip the mg_ecw_110.zip and/or mg_mrsid_110.zip files into your !MapGuideOpenSource/Server/Bin directory |
| | 36 | |
| | 37 | |
| | 38 | = Using with Autodesk !MapGuide Studio = |
| 35 | | 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. |
| | 53 | '''Please note that this only applies to FDO 3.2.3 and !MapGuide 1.2 or greater.''' |
| | 54 | |
| | 55 | If you have a lot of raster images in a single directory, it can be prohibitively slow to read through all of these images just to display a small area of them. |
| | 56 | |
| | 57 | With the release of FDOGDAL 3.2.3, Frank has added support for tile indexes in an XML config file. |
| | 58 | |
| | 59 | If you are using !MapGuide 1.2, you can easily create a new tile-enabled data connection by running a script that Jason has provided. Usage notes are included: |
| | 60 | |
| | 61 | [http://www.jasonbirch.com/fdogdal/rasterconfig.phps View Source] | [http://www.jasonbirch.com/fdogdal/rasterconfig.readme.txt README] | [http://www.jasonbirch.com/fdogdal/rasterconfig.zip Zip Download] |
| | 62 | |
| | 63 | == Debugging Rasters in MapGuide == |
| | 64 | |
| | 65 | If your rasters are not showing correctly in !MapGuide, 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. |
| 44 | | |
| 45 | | == Frank's fdogdal Downloads == |
| 46 | | |
| 47 | | === !MapGuide 1.1.0 === |
| 48 | | |
| 49 | | 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: |
| 50 | | |
| 51 | | http://home.gdal.org/dl/mapguide/ |
| 52 | | |
| 53 | | There are instructions in these packages, but basically you just unzip into the C:\Program Files\!MapGuideOpenSource\Server\Bin directory. |
| 54 | | |
| 55 | | === !MapGuide 1.2.0 === |
| 56 | | |
| 57 | | !MapGuide 1.2.0 uses FDO 3.2.2, and requires a slightly different procedure. Do '''not''' download the mg_fdogdal_110.zip file from Frank's site. First, download and apply the ECW and MrSID packages from Frank's site as above. Second, obtain the [http://download.osgeo.org/mapguide/releases/1.2.0-rc2/MGOS1.2.0GDALPatch.zip MapGuide 1.2.0 gdalfdo patch] and apply it in the same manner. |
| 58 | | |
| 59 | | == Raster performance enhancements == |
| 60 | | |
| 61 | | Raster performance in the current released provider degrades when accessing many image files for a single layer. This is because there was no way of referencing the spatial bounds of each image without opening the image and asking it "Image, what are your bounds?". |
| 62 | | |
| 63 | | In order to address this problem, the raster provider's config file schema was extended (initially to meet the same need with the proprietary Autodesk raster provider) to store bounding boxes for the images in the feature source. Using this new schema as a guideline, Frank has added preliminary bounds support to the fdogdal provider, and this has been sucessfully tested in several environments. Further testing is encouraged. |
| 64 | | |
| 65 | | '''Note:''' These enhancements are only available for FDO 3.2.2, which means that you must be running !MapGuide 1.2 RC or greater. |
| 66 | | |
| 67 | | === Downloads === |
| 68 | | |
| 69 | | These files are required to test the bounds functionality: |
| 70 | | |
| 71 | | * The new fdogdal package (totally unofficial, for now from Jason's site) [http://www.jasonbirch.com/fdogdal/fdogdal.zip fdogdal.zip (1.3MB)] |
| 72 | | |
| 73 | | * Jason's php script for generating an image !FeatureSource and config file from images in a directory on the server [http://www.jasonbirch.com/fdogdal/configbuilder.phps Source] | [http://www.jasonbirch.com/fdogdal/configbuilder.txt TXT] [http://www.jasonbirch.com/fdogdal/configbuilder.zip ZIP] |
| 74 | | |
| 75 | | === Usage === |
| 76 | | |
| 77 | | 1. Install the new fdogdal package into the C:\Program Files\!MapGuideOpenSource\Server\Bin directory (make a backup of the gdal.dll and GRFP*.dll in the FDO directory first) |
| 78 | | |
| 79 | | 2. Place Jason's script in the C:\Program Files\!MapGuideOpenSource\!WebServerExtensions\www directory. Check the user-defined variables at the top of the script to ensure that they match your configuration |
| 80 | | |
| 81 | | 3. Run this script in your web browser (e.g. http://localhost:8008/mapguide/configbuilder.php ). Enter the path to your images and the location you want the new !FeatureSource created. If all goes well, you will be informed of the sucessful creation of the !FeatureSource |
| 82 | | |
| 83 | | Please, let us know how this works on the !MapGuide users, or FDO users mailing lists. |
| 84 | | |
| 85 | | === Status === |
| 86 | | |
| 87 | | Currently, most of these modifications have been applied to the FDO 3.2.x branch. An official package has not yet been created. Haris was experimenting with a couple changes to help with stability under concurrent access, but we have to wait until he gets back in a couple weeks to find out what those were... |
