FDO Report 2007

FDO (Feature Data Objects)

• Period covered by report: Jan-Dec 2007
• Contact name: Greg Boone

Key Accomplishments

2007 was a gret year for the FDO project. Considerable momentum has grown around the development community.

The following 4 releases of FDO were made available in 2007:

• FDO Open Source 3.2.1 Released - March 2007
• FDO Open Source 3.2.2 Released - July 2007
• FDO Open Source 3.2.3 Released - August 2007
• FDO Open Source 3.3.0 Beta 1 Released - December 2007
  • Addition of the FDO Expression Engine
  • Addition of the PostGIS Provider
  • Continued development and release of the KingOracle Provider
  • Alpha Release of the SQL Server Spatial Provider
  • The complete roadmap and features of FDO 3.3.0 can be found here: http://trac.osgeo.org/fdo/milestone/3.3.0.

FDO adoption into Third Party applications continued in 2007:

• 1Spatial Radius Studio v1.4: 3.2.0
• Safe Software FME® 2007: 3.2.1
• Autodesk Map 3D 2008: 3.2.1
• Autodesk MapGuide Enterprise 2008: 3.2.2
• MapGuide Open Source 1.2.0: 3.2.3

External Vendor Adoption of FDO:

• FME® FDO Provider for AutoCAD® Map 3D 2008

Areas for Improvement

• Implement a formalized release process.
• While community contribution to the project is growing, most of those contributions are still on the periphery of the project. The core development on the API is still primarily fueled by developers at Autodesk. The project needs developers from the community actively working on some of the core components.
• Getting started with FDO and the process of building new providers are still more difficult than they need to be. Enhanced documentation, tutorials and certification tools would go a long way to improving this experience.
• A public build system for FDO would provide the community information on the state of trunk and access to daily builds of trunk.
• Linux based builds of FDO remain more difficult than they should be. Additional work is required to the build system of FDO to make it fully FGS viable.
• The PostGIS, King Oracle and SQL Server Spatial providers would really benefit from increased community development and support.