When I first wrote the original ADO.net database module for FDO Toolbox, what I wanted was the ability to integrate FDO data sources with non-FDO data sources (eg. Joining an SDF file with a MS Access database).
For the next release of FDO Toolbox, this module will no longer exist.
The reason: OSGeo.ODBC
I have come to realise that I have been essentially duplicating functionality that already exists in the ODBC FDO Provider since the beginning of time. The provider already wrappers non-FDO data sources as FDO data sources, so I was basically reinventing the wheel (poorly).
So the plan now for non-spatial data support is currently the following:
- Give the ODBC Provider some special attention in the Express Module. There will be connection builders for commonly used formats like MS Access databases, Excel Spreadsheets, CSV files, DSNs, etc.
- Implementing Class to Feature Class conversion, which will replace the old DB Table to Point Feature conversion, since the ODBC provider already exposes the DB Tables as non-feature classes.
- Supporting joins between FDO data sources, again since the ODBC provider has done all the work for us.
- Implementing configuration support. This is just another FDO feature that has yet to be exposed by FDO Toolbox.
2 comments:
Jackie, I don't know a lot about the ODBC provider, but wouldn't implementing #4 give you #2 for free?
Hmmm, point taken.
Configuration would allow you to define non-feature classes as XY/Z point feature classes thus negating the need for #2
Post a Comment