For data management, an RDBMS is of course preferred. Other options to ArcSDE/PostGIS would be something like SQL Server 2008 (cheaper than ArcSDE if you don't need the bells and whistles) or something like the Oracle Express Edition (free, but with a rather painful curve as you scale up). I'd encourage you not to give up on getting PostGIS to work. Often you'll see that something like the wrong version of the ssleay library is located elsewhere in the filesystem, but I've always been able to get it working by putting the required dlls in the FDO installation directory.
My preference in this regard though is to optimize for performance, and if you do not need up-to-the-minute currency or web-based editing you can see considerable performance gains by going to SDF or (if you're feeling adventurous) SQLite as the data storage format. Jason -----Original Message----- From: GISDOTNET Subject: [mapguide-users] Spatial Data Formats Best Practice I have worked with ESRI web technology for the past 9 years and am getting up to speed with MapGuide Open Source 2.0.1 and the FDO providers. While there are numerous FDO providers, I would like to know what the preferred or best practice data format is for MapGuide OS 2.0.1? My overall preference is to go with a RDBMS spatial solution like ArcSDE or PostGIS; however, I am completely flexible. I have gone through dll hell trying to get the PostGIS FDO provider configured without success and ArcSDE comes at a steep price. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
