Announcing: MapGuide Maestro 3.0 Final

12 months, 145 tickets and 309 revisions later, I am happy to announce the final release of MapGuide Maestro 3.0 is now available.

This release includes the following changes from RC1:

• Added missing editor support for creating and editing point styles that reference symbols from a symbol library
• Added a more graceful way to handle unsupported element in a Load Procedure or Layer Definition when you open them in their respective specialized editors.
• Added support for aliases when building GDAL configuration documents.
• Many fixes from RC1.

For a comprehensive list of changes from the very beginning, see the changelog.

Download

The out-of-the-box MapGuide/FDO experience (or: Why the installer doesn't install all FDO providers by default)

When you install MapGuide Open Source, you have the choice of the following FDO providers to install:

• ArcSDE
• GDAL
• Oracle (King.Oracle)
  
• MySQL
• ODBC
• OGR
• PostGIS (old one)
• PostgreSQL (new one)
• SDF
• SHP
• SQLite
• MS SQL Server Spatial (>= 2008)
  
• WFS
• WMS

For those not astutely aware, the following provider options do not get installed by default:

• ArcSDE
• Oracle (King.Oracle)
  
• MySQL
• PostGIS (old one)
  
• PostgreSQL (new one)

The reason for this is simple. These FDO providers require additional components that are not included with the MapGuide installer due to any of the following:

• Licensing restrictions preventing component redistribution (ArcSDE)
• Substantially increased installer footprint (Oracle)
• The components that are bundled (if we did bundle them) may be older or newer than what is provided by your existing DBMS installation (MySQL, PostgreSQL)
• Any combination of the above points.

So there is an implicit assumption that if you do enable any of the above FDO providers during installation, you will need to do some extra post-installation configuration to have a functioning FDO provider. This cannot be avoided.

So what exactly do you need to do for each provider?

For ArcSDE:

• Here's an old (but still relevant) blog post detailing how to set up the ArcSDE FDO provider for AutoCAD Map. It is equally applicable to MapGuide
• Here's a blog post straight from the horse's mouth detailing how to troubleshoot common problems with this provider. Once again, despite the AutoCAD Map focus it is equally applicable to MapGuide as both products use FDO.
  

For Oracle:

• Here's a readme from the author of this provider (sl-king), detailing the configuration you need to do with the Oracle Instant Client
  

For MySQL:

• You need to ensure that libmysql.dll from your MySQL installation is either in the same directory as the FDO provider dll, or the path to libmysql.dll is in the PATH environment variable (which is what Windows will use to search for dlls that need to be loaded). If you are installing MapGuide on the same machine where MySQL is installed, you shouldn't need to do anything.
  

For PostgreSQL/PostGIS:

• You need to ensure that libpq.dll (and its dependencies) from your PostgreSQL installation is either in the same directory as the FDO provider dll, or the path to libpq.dll is in the PATH environment variable (which is what Windows will use to search for dlls that need to be loaded). If you are installing MapGuide on the same machine where PostgreSQL is installed, you shouldn't need to do anything.

Still stuck? Well understand that the root problem for any of the above is that the FDO provider failed to find one or more dlls that it needs in order to properly function. You can use the Dependency Walker tool to determine if your FDO provider has all its dependencies satisfied and can be loaded without issues. Here's a screenshot of Dependency Walker on the King Oracle provider dll on a fresh MapGuide installation.


Notice the question mark on OCI.dll? OCI.dll is part of the Oracle Instant Client which the King.Oracle provider requires to properly function. A question mark indicates that this dll could not be found.

So the solution is to ensure that OCI.dll (and its dependencies) are located in a directory that Windows will search dlls for. Reloading the provider dll in Dependency Walker should no longer show a question mark beside OCI.dll meaning that the provider dll has all its dependencies satisfied, meaning this provider should now be fully functional.

One more thing about this: If you did have to carry out any of these extra configuration steps, remember to restart your MapGuide Server if it is already running.

So in summary:

• Some FDO providers are not installed by default because they require additional components. These components are not bundled into the installer for reasons explained in this post.
  
• This post should hopefully point you in the right direction to configure and troubleshoot these providers should you choose to install them.
  

Announcing: MapGuide Maestro 3.0 RC1

Here is 1st release candidate of Maestro 3.0

This release adds

• Support for validating XML content against local XSD files in the XML editor
• Coloring for active and inactive tabs
• F2 keybinding to rename resources
• A new option to determine whether validation is performed on save (default is: true)
• More missing features from Maestro 2.x
  

And of course: many fixes for defects found in the previous beta and earlier releases.

Showstopper bugs withstanding, I will be releasing the final build of Maestro 3.0 sometime next week.

Download

Announcing: MapGuide Maestro 3.0 beta 3

Here is the 3rd (and most likely last) beta of Maestro 3.0

This release includes mostly fixes from the previous beta and earlier releases.

Most notable is a new command which allows you to purge cached information of a feature source (useful when authoring against a data source whose structure is in constant flux). Using this command ensures that a listing of feature classes for a feature source (or properties for a feature class) will be the most current.

Download