Wednesday, 21 January 2009

FDO Toolbox v0.7.0

After two months of re-writes and re-designs (and a whole lot of new development). I have finally pumped out a new release of FDO Toolbox that until now was nothing more than words and screenshots!

A (big) summary of the changes include:
  • Everything has been rewritten from the ground up. The foundation is now based on SharpDevelop Core, providing a framework for easy extensibility.
  • Re-Designed/Improved Data Preview control. Null values are now displayed as
  • Re-Designed/Improved Schema Editor. This can now also function in standalone mode, meaning you can edit a serialized xml feature schema independent of any open FDO connections.
  • The Generic connect/create data store controls now have helper macros (eg. "Insert Current Directory") to make filling in the connection parameters much quicker.
  • Re-Designed Express Module
  • You can create connections with configuration file support. This is used to configure non-feature classes as feature classes (eg. Defining a non-feature class as a point-feature class by specifying a X and Y column). The configuration files still have to be created/edited manually.
  • The new ETL framework (based on Rhino ETL) is fully implemented. This is much more flexible than how things were done previously. Bulk Copy and Joins are now using this framework. You will probably (definitely) have to re-create your saved Bulk Copy and Join tasks as the xml schemas for these files have changed.
  • Database Join operations now have batch support (if the target connection supports it)
  • FDO Toolbox now uses FDO 3.4.0 (beta 1). FDO 3.4 is not binary compatible with FDO 3.3, so if you are using providers that do not come with the standard FDO distribution, they must be built for 3.4, otherwise they will not work with this release of FDO Toolbox. If this is the case, perhaps the author(s) of the provider(s) in question could be persuaded to start migrating their providers ;-) Also FDO 3.4 requires you have the Visual C++ 2008 runtime library installed.
  • Express module now supports connecting to common ODBC formats (MS Access, Excel, SQL Server, Text files)
  • Express module now supports connecting to common OGR formats (currently: MapInfo, CSV and ESRI Personal Geodatabase)
  • Much more!
Also starting with this release, FDO Toolbox is now packaged with NSIS technology allowing for a better installation user experience. Also, no more lite releases. From now on, every release will have FDO bundled with it.

So without further ado, come and get it!

P.S. The (near) exponential growth of FDO Toolbox between versions means that I may well have missed some small things that were in previous releases. If this is the case, do not hesitate to file a bug report. Actually, do not hesitate to file an bug report on anything! I can't be the only one filing bug reports all the time! :-)

8 comments:

jasonbirch.com said...

Rats; appears to crash on Vista64. Time to break out the VM... Was there a notice for the FDO beta that I missed? I've seen a couple people mention it, and the files are there...

Jackie Ng said...

It runs fine on my Windows 7 Beta VM, so I suspect it's the 64 part, not the Vista part.

Unfortunately I don't have a 64-bit environment to test. Still stuck in 32-bit land.

Jody Garnett said...

I just tried on a Windows XP machine without much luck.

Error message:

The application failed to initiaize propertly (0xc0000135). Click OK to terminate the application.

Jackie Ng said...

Hi Jody,

Have you installed the required components?

http://code.google.com/p/fdotoolbox/wiki/Requirements

Ideally the NSIS installer should be checking for these components beforehand.

Jody Garnett said...

Nope I had not installed anything; just followed your blog post instruction to "come and get it" :-)

Luc said...

Very nice work!

Question 1:
I have tried OGR with PersonalGeoDatabase (Ms-access md file). Connecting, schema definition works OK but trying to view the data throughs an error: system.AccessViolationException:Attempted to read write corrupted memory.

do you have any idea how to reslve this?

Question 2: using FDO toolbox and Shema reading defintion did you ever considered to have FDO toolbox generating XML based Metadata info file following Iso standard?

tx

Luc Van Linden

Jackie Ng said...

Re: System.AccessViolationException

The OGR provider is a very fickle thing. Is this something that occurs on a consistent basis? Would I be able to get a copy of the geo-db to see if i can reproduce the error?

Re: Metadata

I do not understand what kind of metadata you are talking about. Perhaps you could file an enhancement request and elaborate?

Jackie Ng said...

Re: Vista64 crashing

This may help