Writing the FDO/GDAL style of SQLite spatial files (see previous post for details) just got a LOT easier for those of us using Safe Software’s FME Desktop, even the affordable Base edition.
Over the past month, developers at Safe Software and the author of the FDO SQLite provider have put some time into ensuring that the SQLite provider will work properly with FME 2009. Reading worked fine out of the box, but writing required a bit of effort. FME needed datastore creation and schema writing added to their generic FDO writer, and the FDO SQLite provider needed to account for the way that FME writes to multiple schemas.
Here’s how you can take advantage of this provider in FME (and in other FDO 3.3 consumers, such as MapGuide Open Source 2.0):
- Download the unofficial binaries for the SQLite provider from my site
- Open this zipfile and copy the SQLiteProvider.dll file into your FDO directory (default c:\Program Files\FME\plugins\fdo\)
- Make a backup of the providers.xml file in that directory, and then edit the original, adding the contents of the sqlite_provider_entry.xml file in an appropriate location.
Once this installed, writing to SQLite from within FME is dead easy…
1. Add new FDO Destination Dataset:

2. Go to Settings and specify OSGeo.SQLite.3.3 as the provider name:

3: Specify the filename you want to write to:

4. Optionally, set a spatial reference system, and click on OK:

That’s it; now you can start adding tables to your SQLite file as you would any other destination dataset in FME!
As far as I know, Safe will not be distributing the SQLite provider directly with FME 2009 (it’s still in beta) primarily because the provider is not officially being released for FDO 3.3, and partially because the provider is still under heavy development. Fear not, though. I am building this provider against the 3.3 branch as often as necessary, and will post binaries as I do.
The relative ease with which this format was supported by FME can be attributed to Safe’s foresight in exposing FDO directly, rather than just using it behind-the-scenes in their SDF3 writer. They also allow FME to act as an FDO provider, which enables users of products that use FDO for their data layer (such as AutoCAD Map 3D) to access the full range of formats that FME supports.
-J
#1 by Dale Lutz on December 4, 2008 - 12:48 am
Thanks Jason — however, I’ll point out that it was your urging (with an eye on loading PostGIS via an FDO provider so that the correct metadata tables were automatically populated) that got us down the road of exposing a generic FDO capability in FME, which posed a quite serious UI challenge for us too.
Here at Autodesk University there’s been talk in the Geospatial corridors of the great performance that this new SQLite spatial brings to bear, and so I’m quite interested to see for myself how it stands up and to watch how folks out there find interesting ways of applying it. Once it is “official”, we’ll wrap it up nicely inside its own UI in a future FME to make it every easy for folks to use, but until then, the method you’ve outlined in this article will allow anyone to use it.
Dale